Effective August 27, 2026

Privacy

The myAni family is independently operated by its individual publisher. This page covers myAni, myAce, myPax, myCenterOS, and the shared account and support services behind them.

What we receive

We receive the account identity supplied when you sign in, subscription and billing status from Stripe, support requests, and the intake answers, facts, preferences, rules, goals, Systems, plans, approvals, task handoffs, work results, checks, and corrections you choose to save. We compile those inputs into a private customer Build and keep limited connector, security, support, and audit records needed to run and protect the service.

Website, intake, and referral records

We keep limited first-party records of the page, campaign link, referring page, and referral code that brought a visitor to us. After sign-in, we may connect those records to the account, save unfinished intake answers so the person can return, and record the next setup step. A marketing choice is stored separately from account and service messages. These records do not contain prompt text, card details, passwords, API keys, or customer files.

How it is used

We use this information to provide the product requested, enforce the plan, build and track Systems, authorize supported AI hosts, show the next setup step, answer support requests, prevent abuse, and keep important account changes reviewable. We use limited first-party counts to find where setup or service fails. We do not sell personal information, use it for advertising, or use saved customer content to train a general-purpose AI model.

Existing AI history transfer

If you choose to transfer information from an existing AI, the selected export is reduced in your browser before myAni receives it. The useful conversation text is sent to an AI service for one limited extraction with model response storage disabled. The raw export and conversation text are not added to your myAni account. myAni shows proposed facts, preferences, rules, projects, corrections, and goals for review; only the items you approve are added to your intake draft. Do not transfer passwords, keys, payment information, government identifiers, medical records, or information you do not have the right to use.

AI hosts and connected services

When you use myAni inside ChatGPT, Codex, or another supported host, that host receives the myAni information needed to answer your request. The host processes that information under its own terms, privacy choices, and retention rules. A separate connected service receives information only when you connect it and authorize the relevant action.

Account connection

When you connect myAni through OAuth, the authorized host may receive your account email and a statement that the email was verified. This is used to link the correct account and support workspace domain restrictions. It does not give the host your password, payment details, or other sign-in secrets.

Who processes the data

The individual operator of myAni and service providers used for hosting, account sign-in, AI intake and myAce request interpretation, billing, security, and customer support process only the information needed for those jobs. Connected AI hosts and source services receive task-specific information when you authorize and use them. We do not sell personal information or provide it to advertising networks.

How myAce reads a request

When you use myAce, the rough request and any task-specific context you send to that tool are passed to an AI service for one limited interpretation. myAce does not request your inbox, files, past chats, or device. The interpretation request is configured not to be stored by the model API. If that service is unavailable or the monthly smart-read allowance has been used, myAce uses its rules-only fallback. We record the request mode, depth, processing method, timing, and account identifier for usage limits and reliability—not the words in the request.

Billing

Stripe processes payment details. myAni receives customer, subscription, plan, and payment-status records but does not receive or store your full card number.

Retention and control

Private memories and intake drafts remain while the account is active unless you remove them sooner or ask us to do so. Connector access tokens expire after one hour and refresh tokens after 30 days unless revoked sooner. After a verified account-deletion request, we delete or de-identify customer Build content, intake drafts, memories, task ledgers, work results, and referral records tied to the account within 90 days, subject to backups and legal holds. Billing, tax, fraud-prevention, security, dispute, and audit records may be kept for up to seven years. Support records may be kept for up to two years. You can revoke all myAni connector access and change marketing consent from your account.

Information myAni does not accept

myAni is not designed to collect or process payment-card data, protected health information, government identifiers, passwords, API keys, MFA codes, or other authentication secrets. The intake and connector reject likely restricted data. Do not place it in a prompt, memory, task, plan, result, or support request.

Security

We use access controls, scoped authorization, token revocation, input limits, and audit records designed to limit access and make important changes reviewable. No internet service can promise perfect security.

Your request

Use the support page or email privacy@myani.co to ask for help with access, correction, export, or deletion. Report security concerns to security@myani.co. We may need to verify that the account belongs to you before completing a request.

Changes

We may update this policy as myAni changes. The effective date at the top will show when the current version took effect.