Privacy Policy

This Privacy Policy applies to Mirai websites, apps, interactive experiences, creator workspaces, and other services that link to it. "Mirai," "we," "us," and "our" refer to Mirai Technologies Inc., a Delaware corporation.

Creators and organizations may publish experiences through Mirai and independently handle information they receive. This policy covers Mirai's handling of information. It does not cover a creator's or organization's independent handling.

The information we collect depends on how you use Mirai and may include:

• Account and contact information, such as name, email, phone number, login information, role, organization, profile, and settings.
• Content and communications, such as prompts, chats, AI responses, voice interactions and transcripts, inquiries, messages, feedback, property or listing information, uploads, recordings, photos, video, audio, and scans.
• Activity, device, attribution, and location information, such as pages and listings viewed, feature interactions, engagement, referral and campaign details, browser and device information, IP address, approximate location derived from IP, visitor or session identifiers, addresses, places and routes you provide, and device location if a feature requests it and you allow it.
• Preferences and inferences, such as saved content, places, routes, routines, interests, accessibility requests, personalization choices, and information inferred from activity.

We receive information from you; automatically from your use, browser, or device; from creators, organizations, and other users; and from service providers and public sources.

We may associate activity collected before sign-in or an inquiry with an account or contact using identifiers such as cookies. If a feature uses camera, microphone, screen, or device-location access, your browser or device may request permission.

We may use information to:

• provide, personalize, operate, maintain, secure, and support Mirai;
• fulfill requests and create recommendations, routes, transcripts, media, and other output;
• manage accounts, settings, support, service messages, and permitted marketing communications;
• process inquiries and provide relevant experience context to creators or organizations;
• associate activity with an account, contact, experience, or inquiry;
• analyze content and usage to evaluate, develop, and improve Mirai and prevent fraud or misuse; and
• comply with law and protect Mirai, our users, and others.

We may share information with:

• providers supporting hosting, authentication, storage, maps, communications, analytics, transcription, AI, media generation, and other operations;
• creators or organizations connected with an experience you use, an inquiry you submit, or a team you join;
• people you invite or anyone who can view content you choose to publish or share;
• authorities or other parties when reasonably necessary for legal or safety reasons; and
• advisers or counterparties involved in a financing, merger, acquisition, or business transfer.

Depending on the context, information available to a connected creator or organization may include submitted information and related activity, engagement, referral or campaign details, device information, approximate location, visitor identifiers, and, where available, identity or contact information, inquiries, and messages.

Mirai includes Google Maps features and content. Google's collection and use of information through those features is governed by the Google Privacy Policy, which is incorporated into this Privacy Policy by reference.

Some features send prompts, conversation context, place or property information, uploaded media, or audio to AI and media providers. We may log, review, and analyze prompts, responses, transcripts, and related usage information for the purposes described in this policy.

Providers handle information under their applicable terms and our arrangements with them. Depending on the provider, service, account tier, settings, and feature, a provider may retain or review inputs and outputs for safety, abuse prevention, reliability, debugging, product improvement, or AI-system improvement.

If you use a voice feature, microphone audio and relevant context may be streamed to an AI provider and transcribed. Transcripts are handled like other content and may be saved in browser history. As of the effective date, some voice features use Google Gemini Live; providers and features may change. Your browser or device may request microphone permission.

Please avoid including highly sensitive information that is not needed for your request.

We and services integrated with Mirai may use cookies, browser storage, and similar technologies for authentication, security, preferences, saved content, visitor and session identification, chat and feature continuity, analytics, and attribution. You can manage browser storage and permissions, although some features may stop working.

Where enabled and permitted, Mirai measures feature discovery and use, content interactions, loading problems, observed exits, and successful saves or contact. Records include fixed event and feature names, content and interaction references, timing, duration, and progress. A random browser reference in first-party browser storage recognizes later sessions within the same site scope. It expires after 90 days without use. A new browsing session begins after 30 minutes without activity. Different devices and browsers are not joined. Session histories, their summaries, and associated outcome references are removed by scheduled cleanup 90 days after the session’s last observation, subject to the backup and legal exceptions below. Collection remains limited by region and respects applicable browser privacy signals and existing opt-outs. Settings and this privacy page let you turn measurement off without signing in; doing so removes the stored measurement reference, discards unsent events and requests revocation of outstanding server collection capabilities. Server revocation requires network delivery.

Retention reports do not include names, account IDs, message or form contents, or full page URLs. The server may check existing authentication to distinguish staff traffic and verify that a save or contact succeeded, but it does not store an account ID on new measurement sessions. Random browser references and interaction histories are pseudonymous and are restricted to authorized administrators. Embedded experiences use separate publisher and site scopes; when browser storage or the site scope is unavailable, return measurement is unknown. Where collection is permitted, embed loaders report delivery stages, visibility, publisher origin, and publisher-supplied placement and page labels. These labels must not contain personal information. Optional production publisher retention analytics and cross-site journey/outcome linking are currently disabled pending review of publisher agreements, visitor notices and the applicable permission requirements. Enabling these features would require an updated disclosure and any permission required by law. Individual content references are omitted for unclassified, sensitive or personalized content; generic feature activity may still be measured where permitted. The newer retention system’s delivery records are removed after 90 days without observation; publisher activity timestamps and administrator-recorded business lifecycle changes are retained as publisher relationship records. Earlier aggregate-only visits cannot be reconstructed into return histories. Existing choices to turn measurement off remain effective. The legacy embed engagement collector is retired. Existing legacy embed session records have a separate 365-day cleanup default; operational publisher request diagnostics have a 30-day cleanup default. Those settings do not establish that all historical data has already been deleted. Previously collected data remains subject to our retention practices and your applicable privacy rights. Publisher agreement evidence is a separate restricted business record containing the organization, representative name and role, covered websites, authenticated account reference, acceptance time and exact terms. Agreement acceptance does not enable optional visitor measurement or replace any required visitor permission. Analytics controls do not disable processing needed to provide requested features, maintain security, or meet legal obligations.

Retention varies depending on the type of information, why it was collected, the status of an account or relationship, security and fraud-prevention needs, and legal obligations. We retain information for as long as reasonably needed for the purposes described in this policy or as otherwise permitted or required by law.

Deletion requests are subject to identity verification and applicable exceptions. Information may remain in backups or records we are permitted or required to keep for security, fraud prevention, disputes, enforcement, or legal compliance. We may retain information in aggregated or deidentified form where permitted by law.

We use safeguards designed to protect personal information, but no online service can guarantee absolute security. Mirai and its providers may process information outside the country where you live, including in the United States.

Depending on where you live and subject to applicable exceptions, you may have rights to access, correct, delete, copy, or receive personal information; withdraw consent; opt out of or limit certain processing; or appeal or complain about a privacy decision.

Where available, you can change settings, clear browser storage, manage device permissions, or use an email's unsubscribe link. To make a privacy request, email founders@heymirai.ai. We may need information to verify your identity or authority and locate relevant records.

Mirai is intended for users 18 and older and is not directed to children. If you are under 18, do not use Mirai. Contact us if you believe a child provided personal information.

We may update this policy as Mirai or our practices change. We will post the updated policy and effective date and provide additional notice or obtain consent when required by law.

Questions, concerns, and privacy requests can be sent to founders@heymirai.ai. Please do not email passwords, government identifiers, or other highly sensitive information.