Privacy Notice

1. Who operates this service

This notice uses MyPersonas / AliaSpaces as the operator label for the website, persona network, private management studio, and related automation features.

The service uses Supabase for authentication, database records, server-side Edge Functions, encrypted secret storage through Supabase Vault, and media storage.

2. Information handled by the service

Sign-in and private account information

• Your sign-in email, Supabase user identifier, account display name, authentication state, and security factors managed by Supabase Auth.
• Optional details you choose to save, such as name, pronouns, date of birth, gender, country, city or region, phone number, time zone, personality notes, and astrology birth details.
• Preferences such as content filters, hidden topics, and automation safety settings.

Persona and social content

• Persona names, handles, bios, themes, visibility settings, links, posts, comments, reactions, albums, media, follows, blocks, and other page content. For new media, this can include your AI-use declaration, source and final file hashes, MIME type, byte size, watermark version/state, rendition, and the persona and public asset URL to which it is bound.
• Private notes, drafts, schedules, content plans, persona instructions, affiliate disclosure text, approval records, automation history, owner-assistant conversations, and any private main-to-backup persona roster assignment you choose.
• Public fan-chat messages, whether the visitor selected a saved transcript or private session, the persona involved, a one-way hash of the visitor’s random browser token, safety flags, live-owner state, and escalation state. The persona owner can see saved chats and private-session chats while they remain open. Fan chat is currently disabled for adult/NSFW personas.

Saved external-account inventory

The private account ledger can contain a provider name, username, login email, profile URL, persona assignment, notes, and connection status. It is designed for identifiers and planning—not credentials. Do not enter provider passwords, app passwords, recovery codes, API keys, or browser cookies.

Connected provider data

• Gmail: authorized mailbox identity, granted scopes, message and thread identifiers, labels, selected headers, sender, subject, date, a bounded Gmail preview snippet, unsubscribe metadata, classification findings, scan status, action previews, approved label/archive/Trash changes, and undo/audit records. The current scanner does not read full message bodies or download attachments.
• X: the authorized account identifier and username, granted scopes, connection state, and token lifecycle data. The current connector supports identity/read authorization and does not have posting permission.
• Meta: after the owner authorizes the configured Business app, the Meta member identifier and name, manageable Page identifiers, Page names and tasks, Page-linked professional Instagram identifiers and profile fields, granted discovery scopes, connection state, and token lifecycle data. The current connector pairs assets for identity/read use and does not publish.
• Future connectors: this notice must be updated when Outlook or another provider begins sending data to MyPersonas, or before a current identity/read connector adds a new data or publishing scope.

Diagnostics you choose to submit

The in-app Report a problem control sends your note, the current page route, up to 200 characters of browser user-agent information, and a short list of recent in-app error or status messages. When you are signed in, the report can include your user identifier; signed-out reports have no account identifier.

3. How information is used

• Authenticate you, protect private owner records, and provide account-security controls.
• Create, display, search, and manage persona pages according to the visibility you choose.
• Store account inventory and bind authorized provider identities to the intended ledger record.
• Generate drafts, schedule work, enforce pauses, limits and quiet hours, and keep approval and action histories.
• Run mailbox reports and carry out only the exact mailbox actions you approve.
• Send selected prompts and context to the AI provider you configure or select.
• Investigate problem reports, protect the service, and enforce safety boundaries.

4. What is public and what is private

Your profile, owner-to-persona relationship, and private Backup roster assignments are private database records protected by owner-based access rules. Marking a persona as Backup does not publish or reveal a relationship; the separate Linked personas control is the explicit opt-in public cross-link. Public and unlisted persona pages can expose the content, links, interactions, and profile details you put on those pages. Private persona visibility restricts the page, but it is not a promise of absolute anonymity.

Other people, search engines, external links, or caches can retain copies of public material. Avoid including identifying information if separation between personas matters to you.

5. OAuth, tokens, and external accounts

Official provider authorization redirects you to the provider’s own sign-in and consent page. MyPersonas receives authorization results and tokens, not the password you enter on the provider page.

• Gmail refresh tokens, X access/refresh token bundles, and configured Meta user/Page tokens are encrypted in Supabase Vault and are unavailable to ordinary browser code.
• OAuth state, PKCE verifiers, and same-browser bindings are temporary, service-only records used to complete a connection safely.
• Connection metadata—such as provider identity, scopes, status, and expiry—appears in owner-readable records without exposing the token.
• Removing a ledger record or using content erasure attempts to revoke supported provider grants and remove the encrypted local token. It does not delete your provider account or provider-hosted content.

For providers without an official connector—including OnlyFans and Signal—MyPersonas can hold private planning records, links, drafts, and the posted/sent status you mark for staged items. It will not collect provider passwords, session cookies, or reverse-engineered login sessions.

6. AI processing

When you choose an AI backend, the relevant prompt, persona instructions, conversation content, or draft context is sent through a server-side proxy to that provider. Supported hosted endpoints can include OpenAI-compatible services, Anthropic, Azure OpenAI, Google Gemini endpoints, OpenRouter, xAI, Groq, Mistral, DeepSeek, Together, Fireworks, and explicitly approved custom hosts. Which provider receives data depends on the model connection you select.

Optional AI mailbox classification is off until you select a model for that mailbox and accept the mailbox-specific disclosure. It sends only bounded sender/subject/preview-snippet inputs for ambiguous messages—not full bodies or attachments. A custom mailbox AI host needs separate confirmation.

When the site generates an image, it records a short-lived server event and passes the provider output directly to secure media intake. That event can include the owner and persona identifiers, selected backend, provider and model, hashes of the prompt and output, output MIME type, creation time, expiry, and derivative-use count. The prompt text is not stored in this generation event. The browser receives only the visibly watermarked, registered public derivative; event consumption and provenance registration are one database transaction.

Every media upload asks whether generative AI was used. “AI-assisted,” “AI-generated,” and “Not sure” static images receive the MyPersonas AI mark; “No AI” retains the exact uploaded bytes. Pre-existing external media can remain visibly labeled “AI use not known,” while new unregistered external media prevents publication. The service does not claim that an owner declaration or automated detector can prove how external content was made. AI-used GIF, APNG, animated WebP, and video upload remains unavailable until the service can mark every frame.

AI providers process submitted data under their own terms and privacy notices. Avoid sending secrets or information you are not permitted to disclose.

7. Service providers and third-party requests

Data can be transmitted to:

• Supabase for sign-in, database, storage, encrypted Vault secrets, and Edge Functions.
• The provider you connect, such as Google/Gmail, X, or Meta, to authorize, verify, discover eligible assets, read, modify, refresh, or revoke within the scopes shown on its consent screen.
• The AI provider you select for a requested model operation.
• Open-Meteo geocoding when you press “Find place”; the entered place name is sent to obtain coordinates and a time zone.
• Content, embed, CDN, and extension hosts when your browser loads their media, scripts, embeds, or release information. Those hosts receive ordinary web-request information under their own policies.

The current application does not include a behavioral-ad tracking or personal-data sale workflow.

8. Browser storage and cookies

The current web client uses browser local storage and session storage for the Supabase sign-in session, content filters, selected local endpoint, owner-chat backup, OAuth same-tab binding, age-gate choice, and a random fan-chat visitor token. Session items normally end with the browser tab; local items remain until cleared by the feature, content erasure where applicable, or your browser’s site-data controls.

MyPersonas does not import or store session cookies from external social, creator, or mailbox accounts. Supabase Auth, provider sign-in pages, and embedded third-party content can use their own cookies or browser storage under their notices.

9. Security safeguards

The current design uses HTTPS provider flows, Supabase row-level access rules, owner-bound server functions, encrypted Vault storage for connector tokens and model keys, limited service-role access, exact-action approvals, safety pauses, and audit records. Sensitive OAuth tables are not readable by ordinary browser roles.

No system can guarantee perfect security. Protect your AliaSpaces sign-in, enable two-factor authentication when available, review connected applications at each provider, and report unexpected activity without including credentials.

10. Retention and deletion

Owner content and operational records generally remain until you remove them, clear the relevant history, remove the connected account, or use the content-erasure control. A saved fan-chat transcript remains in the private owner inbox until deletion. A fan who turns off conversation saving uses a private session: message content is temporarily stored so the AI and an optionally live owner can respond, deleted when the chat closes successfully, and automatically expires after 30 minutes without activity. Content-free safety, quota, and delivery audit receipts may remain without the message text. Short-lived authorization, scan, lease, and action-preview records expire according to their task. Gmail scan checkpoints are bounded to seven days, action previews to 24 hours, and the current Gmail undo window to no more than 28 days.

Deleting all content removes owned personas, private Backup roster assignments, pages, posts, albums, media, account inventory and connections, drafts, schedules, linked models and encrypted credentials, automation/chat history, display name, preferences, and owner problem reports. Deleting either persona in one Backup pair removes the private assignment but does not delete the other persona. The in-app content-erasure control intentionally retains your Supabase sign-in record.

For complete steps, provider revocation links, and sign-in deletion instructions, see the Data Deletion Guide.

11. Your choices and controls

• Choose public, unlisted, or private persona visibility and privately assign or remove one Backup persona without creating a public cross-link.
• Download an owner-readable JSON export from Account & settings → Security.
• Clear an owner-assistant conversation from its chat controls.
• Before using public fan chat, choose a saved transcript or turn saving off for a private session. The human persona owner can see either mode while the chat is open, and human replies are labeled Owner.
• Pause all automation, pause one persona, require approval, limit daily activity, and set quiet hours in Matrix.
• Disconnect a supported provider and revoke the grant at the provider.
• Delete content while keeping sign-in, or request removal of the remaining sign-in record.

12. Children and adult content

MyPersonas is not directed to children under 13, and children under 13 should not create accounts or use public fan chat. Do not submit a child’s personal information through the service.

Adult/NSFW persona features are for adults age 18 or older. The current 18+ page prompt is a visitor self-attestation, not identity-based age assurance. Public AI fan chat remains disabled for NSFW personas. Users are responsible for complying with provider rules and applicable age, consent, and content laws.

13. Affiliate and sponsored content

MyPersonas can store approved links, offers, and disclosure language and can display sponsored or affiliate destinations. The persona owner is responsible for accurate, prominent disclosures and for following the destination platform’s advertising, endorsement, and affiliate rules. A link stored in MyPersonas is not an endorsement or verification of the offer.