Privacy Policy, Data Protection and Security

This explains what DoGPT collects when you use dogpt.ir, why we have it, and what you can ask us to do with it. We collect the minimum the service needs to work, which is less than you might expect, because your API requests never touch our servers.

The short version

We hold your email address, a record of what you paid, and a running total of what you spent. We do not hold your prompts, the model's replies, your card number, or a password. We do not run advertising or analytics trackers, and we do not sell anything about you.

What we collect

Account. When you sign in with GitHub or Google we ask that provider for your email address and your stable user ID there, and we store both along with which provider you used and when the account was created. We ask GitHub for read access to your profile and email, and Google for your email through OpenID Connect. We do not request access to your repositories, your files, or your contacts.

Session. Your sign in state lives in a cookie we sign cryptographically. There is no session table, so the cookie itself is the session.

Payments. Stripe collects and processes your card details on its own systems. We receive the amount, the currency, the time, and a Stripe reference, and we write those into your wallet ledger as a credit.

API key. We store the first few characters of your key so the dashboard can show you which one is active, plus its status and timestamps, and an internal reference to the key record held by our routing provider. The full key is shown to you once and is never written to our database.

Usage. We store one number per account per day: total spend in US dollars. That comes from the routing provider's meter. It carries no prompt text, no model breakdown, and no per request detail.

Operational records. We log account events such as key creation and key rotation, with a timestamp and the account they belong to, so we can investigate abuse and answer support questions.

What we do not collect

Your prompts and the model's output never reach us. Your code calls the API endpoint directly, and that traffic goes to our routing provider and on to the model provider without passing through this site. We could not produce a transcript of your usage if we wanted to.

We also never hold a password for you, never see your card number, and run no analytics, advertising, or session replay scripts anywhere on the site.

Why we are allowed to hold it

Your email address, your key metadata, and your wallet ledger are needed to perform the contract you entered when you signed up. Our operational records and the daily spend totals rest on our legitimate interest in running the service securely and in being able to answer a billing question. Payment records are kept because tax and accounting law requires it. We do not rely on consent, and we send no marketing.

Email we send you

Account messages, never marketing:

• a welcome message when the account is created
• a receipt when a top up is credited
• a warning when you reach your chosen spend alert threshold (50–95%)
• a notice when the credit runs out and requests stop
• if you turn on auto top-up, a note when a charge does not go through
• if you set a daily spend cap, a note when it stops requests for the day
• if support adjusts your balance and asks us to tell you, a note saying what changed and what the balance is now

The spend warnings re arm themselves after your next top up, so you get at most one of each per balance rather than a stream of them. If a single reconciliation empties a full balance, only the second message is sent.

Cookies

Two, both strictly necessary. The session cookie keeps you signed in for seven days and is HttpOnly, SameSite=Lax, and Secure over HTTPS. A short lived cookie holds the OAuth state value while you are being redirected to GitHub or Google, and it is deleted as soon as you come back. No third party sets a cookie on this site, so there is nothing here to consent to or opt out of.

Who else processes your data

• Cloudflare hosts the site and stores the database, the wallet ledger, and the model catalogue cache
• Stripe processes payments and holds the card details
• our AI routing provider issues and meters API keys, and receives the content of your API requests directly from you
• the model providers you call, such as OpenAI, Anthropic, and Google, receive your request content through that routing provider
• an email provider delivers the messages listed above
• GitHub or Google, whichever you sign in with, confirms your identity to us

We will also disclose data where a law, a court, or a regulator requires it, and we would tell you unless we are legally barred from doing so. If the business is ever sold or merged, account data moves with it, and we will email you before that happens.

Where your data is

Cloudflare, Stripe, and the model providers operate globally, so your data may be processed outside the country you live in, including in the United States. Where European or UK data protection law applies to a transfer, it is covered by the standard contractual clauses those suppliers publish.

How long we keep it

Your account, its wallet ledger, the daily spend totals, and our operational records stay for as long as the account exists. We do not currently expire them on a timer, so deletion is what removes them. Ask us and they go. Payment records are kept for as long as tax and accounting rules require, which is commonly seven years, and that obligation survives deletion of the rest of your account.

Your rights

You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, ask for it in a portable format, or object to processing we base on legitimate interest. If you live in California you can also ask what we collected, ask us to delete or correct it, and know that we do not sell or share personal information and run no financial incentive programmes.

Email privacy@dogpt.ir from the address on your account. There is no self service delete button yet, so deletion is a manual request. We answer within 30 days and delete within 30 days of confirming, except for the payment records we are required to keep. Exercising any of these rights costs nothing and we will not treat you differently for it.

If we get it wrong, you can complain to the data protection regulator where you live.

Security

Everything moves over HTTPS. Session cookies are signed with HMAC and cannot be edited without detection. The API key we issue you is never written to our database at all, so there is no store of live credentials here to breach. Access to the production database is limited to the people who operate the service. No system is perfect, and if a breach affects you we will tell you and the relevant regulator within the deadlines the law sets.

Children

The service is for adults. We do not knowingly collect anything from a child under 18. If you believe a child has an account, email privacy@dogpt.ir and we will remove it.

Changes

When this policy changes, the date at the top changes with it. For a change that materially affects how we handle your data we will email the address on your account before it takes effect.

Contact

privacy@dogpt.ir for anything about data, support@dogpt.ir for everything else.