Privacy Policy
Last updated: October 5, 2026.
At a glance
Local workspaces keep chats, settings, attachments and encrypted connection credentials on your device. Dinasty operates private, invitation-only cloud workspaces; their server also processes and stores workspace content and credentials. Requests and tool results can go to your chosen AI provider. Our beta rollout will use PostHog for product-usage measurement and Sentry for automatic technical error reports in builds that include those integrations, with the notice and controls described below. Website beta signup sends your email and signup record to Loops; occasional beta updates are optional. We do not sell personal information or use it for advertising.
Who we are
Dinasty Online Inc. (Florida, USA) provides AuraVibes and auravibes.me. We are the controller for website signup information, product measurement and error reports sent to our services, and information processed by cloud services we operate. We use cloud hosting and other service providers to process information for the purposes described in this policy. Contact us about privacy at privacy@auravibes.me. For app help, write to support@auravibes.me.
You may also connect to a server operated independently of Dinasty Online Inc. That operator is responsible for its own account, workspace and hosting practices; its privacy notice applies to that processing. Check the server address and operator before connecting. Cloud features depend on the app build and server configuration and may not be available in every beta build.
What the app stores
In a local workspace, AuraVibes keeps chats, workspaces and settings in a database on your device and attachments in local storage. Depending on your build's features, local data can also include saved drafts, app-owned attachment copies, summaries or rollback checkpoints, imported archives, usage/cost records, and background work records and results. Browser builds use browser storage for supported local files and drafts; device and browser storage have different limits and deletion behavior. AI provider API keys and connection tokens are encrypted on the device with a key kept in your operating system's secure storage where supported. Using a local workspace does not automatically upload its chats or credentials to a cloud workspace; technical measurement and error reports are separate, as explained below.
If you create or use a cloud account, the selected server processes your email, account identifiers and authentication information. Cloud workspaces store and sync their configuration, membership and permissions, conversations, tool calls and results, and uploaded attachments, including history or background work records supported by that build. Dinasty-operated workspaces are private and invitation-only. Authorized members can access shared content according to their roles; private membership does not prevent the server from processing that content. Other data you create or import into a workspace follows the same storage and access boundaries.
Cloud connection credentials, including API keys and OAuth access or refresh tokens, can be stored encrypted on the server. The server can decrypt them to authenticate and run configured requests. This is encryption at rest, not end-to-end encryption that prevents the server from accessing the data. The server also processes operational records, such as account or workspace identifiers, request times and errors, to run and protect the service. Privileged administrative changes may have audit records identifying the actor, action, affected resource and time; access is restricted to authorized personnel for administration and security.
Removing local app data or uninstalling the app removes local copies subject to your device backups and operating system behavior. It does not delete a remote account, cloud workspace or information already sent to another service. Removing or disconnecting a cloud account in the app also differs from deleting the account on its server.
What leaves your device
- Your AI provider: Your prompts, conversation context, tool results and attachments included in a request go to the provider you connect, such as OpenAI, Anthropic or OpenRouter. This can include information retrieved from a connected app. Your API key or OAuth token authenticates the request. In a cloud workspace, the server can make these requests on your behalf. Where available and enabled, background continuations or optional prompt-cache refreshes can send additional requests using retained context. The provider's processing, retention and charges are governed by its own policies.
- Connected apps and tool servers: An action sends the information and credentials needed for that action to the connected service, such as Notion, or to a remote tool server you connect. New tools ask for permission by default. You can allow an action once, for a conversation or set different permissions; previously allowed actions may run without a separate prompt. Information returned by a tool can become part of the context sent to your AI provider. Check the policies of the services and servers you connect.
- Other requests and device access: The app may load model logos from models.dev, retrieve release information where that feature is available, or contact addresses you configure or request through tools. Those destinations may receive an IP address and ordinary request data. Camera, microphone and file selection follow your device's permission and picker controls. Material you attach can be included in requests to the AI provider or cloud workspace you choose. If your build offers OS notifications and you enable them, they use generic text by default; any remote delivery service processes the device token and routing metadata needed for delivery. Notification delivery must not include prompts, responses, tool arguments or credentials.
- Store feedback: Apple TestFlight and Google Play may collect installation, testing and feedback data under their own policies.
App analytics and automatic error reports
The planned beta rollout includes these integrations; availability depends on the build. We will provide the required notice and controls before a build starts sending these reports.
- PostHog: We will use PostHog to measure selected activation, reliability and feature-usage events and improve AuraVibes. Approved technical metadata can include the event type and time, app version, operating system/device family, language, and an installation or session identifier where needed. Requests also expose ordinary network metadata, such as an IP address, to the receiving service. These records are not necessarily anonymous.
- Sentry: Builds with Sentry will automatically send technical crash and error reports to diagnose failures. Reports can include an error category, stack trace, event/request identifiers, app and operating system versions, timestamps and relevant technical state. These reports do not require you to submit a separate bug report for each error.
We will limit these integrations to approved technical fields and filter before transmission. Prompts, conversation text, attachment content, credentials, tool arguments/results and sensitive URL values are excluded. Initial beta measurement does not include screen/session recordings, broad automatic interaction capture or collection of text entered in forms or the composer. We do not use these integrations for advertising profiles.
Product analytics may be enabled by default only where the actual configuration and applicable law permit collection without prior consent. Where consent is required, collection waits for your consent. Builds with product analytics will provide a simple, free control to turn it off or withdraw consent. Any storage or device access that requires consent, including for error reporting, also waits for that consent. A local workspace, cookieless collection or a pseudonymous identifier does not by itself make technical reporting anonymous or exempt from consent rules. Optional update emails have a separate opt-in.
Website signup and security
When you submit the beta form, we collect your email address, device choice, language, website signup source, optional-update preference, terms version and signup time. We send these to Loops to deliver the beta links, keep the signup record and manage your email preferences. Loops also processes delivery and unsubscribe information. We send occasional beta updates only if you select the optional updates checkbox. You can unsubscribe using the link in those emails or email privacy@auravibes.me. Requesting beta links does not require subscribing to updates.
Your signup records whether you requested optional updates. Delivery also respects existing mailing-list opt-outs. An invitation email can still be sent when you have declined optional updates. An invite email might not arrive if our email service is unavailable; the website also shows the install steps.
Cloudflare hosts the website and processes request data, such as IP addresses, browser details and security logs. Cloudflare Turnstile checks whether a signup is automated and processes device and network signals for that purpose; the signup verification request may include your IP address. Website application logs record error codes and response statuses, not signup email addresses or form payloads. We do not use advertising trackers, product analytics or analytics cookies on this website. Security checks may use storage or other mechanisms described in Cloudflare's Turnstile privacy information.
Why we process information
Where EU or UK data protection law applies, our legal bases are:
- Providing the service you request: Account administration, cloud storage and requests, and delivery of requested beta links are necessary to provide the relevant service under our terms.
- Legitimate interests: Essential website operation, security, abuse prevention, technical error diagnosis and keeping records of signup choices help us operate and protect the service. We may also rely on legitimate interests for proportionate product-improvement statistics where permitted without prior consent. We consider your rights when relying on these interests.
- Consent: Optional beta updates rely on your opt-in. Product measurement, error reporting or associated storage/device access also relies on consent where required by applicable law. You can withdraw consent at any time; withdrawal does not affect processing that was lawful before withdrawal. Accepting the Terms or requesting beta links does not replace a required analytics consent choice.
- Legal obligations: We process information when needed to comply with applicable law, including responding to privacy requests.
Local device permissions let you control access to device features; they do not replace the legal bases described above. We use sensitive information in content or credentials to provide the functionality you request, protect the service and comply with law.
How long we keep data
These are the planned beta retention targets. Periods labelled as targets still need verification against cleanup behavior and the services' actual settings; they are not confirmation that every copy already expires on that schedule. We will confirm the applicable periods before enabling the relevant collection. Contact privacy@auravibes.me about retention that applies to your information.
- Local data: Remains on your device until you remove it, subject to device backups and operating system behavior. Draft controls clear unsent text or app-owned copies on send, discard or deletion where supported; content already saved in a conversation has its own deletion controls. Deleting a checkpoint does not delete its source messages. Exported archives and copies outside the app are outside its deletion controls.
- Cloud data and backups: Content remains on the selected server while the account or workspace needs it. Account and workspace deletion are separate; shared content can remain for other members after you delete your account. Our rolling cloud backup retention target is 30 days. Completed deletions must be reapplied before restored data is served. An independent operator sets its own retention rules.
- Product analytics and our operational logs: Our raw-event and operational-log retention target is 30 days, subject to verified vendor controls. This does not extend shorter platform limits or legal requirements. If a consent exemption requires earlier aggregation and removal of individual records, those records must be removed as soon as they are no longer needed for aggregation. Aggregate statistics that cannot identify people may be retained for product improvement.
- Sentry error reports: Retention follows the active plan when reports are ingested. Sentry's standard periods are 30 days on Developer and 90 days on Team/Business; the plan used for the beta must be confirmed before collection. See Sentry's retention documentation.
- Support requests: Our retention target is six months after resolution, except for minimum records still needed for a documented security or legal purpose. Avoid sending credentials or full conversations in a support request.
- Beta signup and update contacts: For contacts without an ongoing updates subscription, our target is the beta duration plus 90 days. For opted-in updates, our target is to retain the contact until unsubscribe and then remove data no longer needed, preserving only minimum records necessary to honor opt-outs, demonstrate consent or meet legal obligations. Unsubscribing stops updates; you can also request deletion at privacy@auravibes.me.
- Website technical logs: Cloudflare Workers invocation logs expire within its documented retention window, currently up to seven days. Other security records depend on the relevant hosting service and settings. We retain information needed to investigate incidents or meet legal obligations only for that purpose. Ask privacy@auravibes.me about retention that applies to your information.
Necessary security, administrative audit, consent/opt-out and legal records may have a different retention period based on their specific purpose and applicable obligations. Access is restricted, and they are removed when that need ends. These telemetry targets do not introduce automatic pruning of conversation content, drafts or checkpoints.
AI providers, connected apps, independent server operators, stores and device backup providers set their own retention rules for information sent to them.
Your choices and rights
You can change app permissions, disconnect services, remove local app/browser data, control product analytics in builds that include it and unsubscribe from updates. Analytics and error reporting have different purposes; an analytics opt-out does not itself unsubscribe you from emails or change essential service/security processing. If cloud accounts are available, use Delete account to request server account deletion; Remove account only removes the local connection. You must first delete or transfer ownership of workspaces you own. Deleting an account does not erase shared workspace content, user-exported archives, independently held copies or actions already carried out in connected services.
Email privacy@auravibes.me for access, correction or deletion of signup information or other personal information Dinasty Online Inc. holds. For an independent server or connected provider, contact that operator. Do not email passwords, API keys or tokens. We may verify identity or an authorized agent's authority before acting and will respond within applicable legal deadlines, with notice of permitted extensions.
EU and UK: Depending on the legal basis and circumstances, you may request access, rectification, erasure, restriction, portability or object to processing, including direct marketing. You can withdraw consent and complain to your local data protection supervisory authority. We ordinarily respond to these requests within one month, subject to lawful extensions.
California: Where the CCPA applies, you may request the categories and specific pieces of personal information collected, their sources, purposes and recipients; request deletion or correction; opt out of sale or sharing; and limit qualifying uses of sensitive personal information. You may use an authorized agent and will not receive discriminatory treatment for exercising a privacy right. We ordinarily respond to requests to know, delete or correct within 45 days, subject to lawful extensions. Categories described above include identifiers such as email, account IDs and IP addresses, internet or network activity such as browser and security records, and content you provide. We disclose them to the providers, operators and services described above for the stated purposes. We do not sell personal information or share it for cross-context behavioral advertising, and do not use sensitive personal information to infer characteristics about you.
Children
AuraVibes is not intended for children under 13 or a higher minimum age required where they live. The beta form asks you to confirm you are at least 13 and accept the terms; we do not request your date of birth. Please contact us if you believe we collected a child's personal information so we can investigate and remove it as required.
International transfers
Dinasty Online Inc. is based in the United States. Loops, Cloudflare, PostHog, Sentry and cloud hosting providers may process information in the United States and other countries where they or their subprocessors operate. Cloud and telemetry processing locations depend on the actual service configuration and selected regions. Protections and rights can differ from those where you live.
The providers publish Loops' Data Processing Agreement and Cloudflare's Data Processing Addendum describing safeguards for covered transfers, including EU Standard Contractual Clauses and UK adaptations where applicable. Contact privacy@auravibes.me to ask about the transfer mechanism that applies to your information or to obtain relevant safeguard details or copies. For an independent server, ask its operator.
For cloud hosting, analytics and error-reporting services, we must confirm the applicable processing agreements, regions and legally required transfer safeguards before activation. A provider's public policy or agreement template alone does not establish which safeguards cover our account or your information.
Changes
We may update this policy as the product or its data practices change. We will update the date above and provide notice when required by law, including before using personal information for a new purpose that requires notice or consent. Contact privacy@auravibes.me with questions.