Privacy policy.

Last updated 15 August 2026

What we collect

If you only read the site

Nothing that identifies you. This site sets no cookies, runs no analytics, and loads no fonts, scripts or images from any other company — every request your browser makes while rendering these pages goes to this server and nowhere else.

The server keeps ordinary request logs, which include IP addresses, for a short period, to diagnose faults and to detect abuse.

If you tell us what you want to run

Your email address, and anything else you type into that form — optionally a name, a note, and which portfolio you were looking at. We also store a one-way hash of your IP address, not the address itself: enough to notice one machine submitting the form forty times, not enough to reconstruct who visited.

If you have an account

• your email address;
• a hash of your password — never the password;
• which portfolios you follow, the allocation you set, and the sub-account label you chose;
• hashes of your session and feed tokens, plus a short non-secret hint so you can tell which token your instance is holding;
• your Telegram chat id, if you link Telegram;
• timestamps: when you signed up, last signed in, and when your instance last read its feed.

If you connect an instance in cloud mode

Your instance can report its state to this hub so you can see it from a browser — what it is holding, what it has ordered, and whether it is connected. That is your choice: an instance in local mode reads its signals and reports nothing back. When it is on, this hub holds a cached copy of what your instance told it, and no more.

What we deliberately do not collect

• Brokerage credentials. Not stored, not transmitted, not requested. Nowhere on this service is there a field for them.
• Your password. Only a hash of it, which cannot be reversed into the original.
• Usable tokens. Feed, session and ingest tokens are stored as peppered hashes. A copy of the database contains no working credential, and a lost token is replaced by rotating it rather than by looking it up.
• Analytics, advertising or tracking identifiers. There are none.
• Payment card details. Card numbers are entered on Stripe's own checkout pages and never reach this service. We store only what Stripe tells us afterwards: which plan, whether it is active, and the identifiers needed to cancel or refund it.

Why we hold it

To operate the service you asked for: to sign you in, to deliver the portfolios you follow to your instance, to notify you about your own orders where you asked to be notified, to keep the service secure and available, and to reply to you.

We do not sell personal data, and we do not use it to build a profile of you for anybody else's purposes.

How it is stored

In a PostgreSQL database on a server we operate, reachable only through this site over HTTPS. Secrets are stored hashed as described above. Backups are encrypted.

Who else sees it

Stripe, our payment processor, when you buy something: it receives your email address and the card details you type on its own pages, and it tells us which plan you took and whether it is active. We never see the card.

Telegram, in two ways, and the second is worth stating plainly. If you link your own chat, it necessarily sees the messages sent to you. Separately, we are notified there when an account is created or a plan is bought — those notifications name the email address involved, so Telegram processes it. They go only to the operator's own chats, never to any customer's.

The infrastructure providers who host the server. Where we use a language model to read a published research document, that document is a public or subscribed source; your personal data is not sent to it.

We disclose personal data to a third party only where the law requires it.

How long we keep it

• Account data: while your account exists, and for a short period afterwards so that a deletion can be reversed if it was a mistake.
• Early-access requests: until we have replied and you have decided, and then no longer than is useful. Ask and we will delete yours immediately.
• Session records: a revoked session is marked revoked rather than deleted, because the record of a login is part of the security history of an account. An operator can open a time-limited support session on an account; it is not shown on your Sign-ins list, and it is still a session row.
• Server logs: a short period, then discarded.

Your rights

Depending on where you live, you may have the right to ask for a copy of the personal data we hold about you, to have it corrected, to have it deleted, to object to or restrict how it is used, and to complain to your data protection authority.

Ask, and we will do it. There is not very much to send you.

Contact

Write to privacy@autoportfolios.ai.