Privacy Policy

1. Who is responsible

The service is operated by Arshak Tsarukyan, sole proprietor, Republic of Armenia (“we”, “us”). For your account, signup and billing details, we are the controller of your personal data.

The text you send through the API often belongs to your own customers. For that text, we act on your behalf and only on your instructions, as your processor; you remain responsible for it towards them. We can sign a data processing agreement with you; write to [email protected].

2. What we collect

When you use the API

• The text you send, so a correction can be checked against the original.
• The results we return: the instant result, and the polished version if you asked for one.
• Request details: the tone, the time, and which API key sent it, so only your key can list and correct its requests.
• Corrections you send, kept with the request they fix.
• Usage: how many requests your key has used this period and when it was last used, so we can apply your plan’s limits.

When you sign up or pay

• Your email address, if you signed up for a trial online. We send your key to it, and keep a normalised form of it to allow one trial per inbox.
• Your plan and Paddle subscription ID, if you pay online. Paddle collects your name, billing address and payment details as Merchant of Record; we never see your card.
• Your messages, if you write to us.

Your API key itself is never stored, only a one-way hash of it.

When you visit the website

• Homepage demo: text you type there is converted on our servers and returned. It is not stored, and no AI provider receives it.
• Technical data: like any website, our servers and network provider see your IP address and browser details. We use IP addresses briefly to rate-limit the demo and signup form, and our servers keep short technical logs of requests (time, address, page and status) for security and troubleshooting. These logs do not contain the text you send.

3. Why we use it

• To provide the service you asked for (performance of a contract): converting text, sending your key, enforcing plan limits, and checking corrections against the request they fix.
• To keep the service secure and working (legitimate interests): rate limits, abuse prevention, troubleshooting.
• To improve results for everyone (legitimate interests): after review, a correction can add a single word to the shared dictionary, never your message.
• To meet legal duties (legal obligation), such as answering lawful requests. Paddle keeps the tax and payment records for paid orders.

We do not sell your data, use it for advertising, or use your text or corrections to train AI models.

4. How long we keep it

• Requests, results and corrections: deleted automatically 30 days after the request.
• Account details (email, plan, usage count, subscription ID): while your key is active. When you ask us to close your account, we delete them, apart from what we must keep by law.
• Dictionary words added from reviewed corrections: kept, because they are single words with no link to you or your message.
• Technical logs: kept only for a short time, then overwritten.

5. No-log mode

Business and Custom customers can ask us to switch their key to no-log. Each request is converted and returned as usual, but neither the text nor the results are written to our database. We keep only the key details, plan, usage count and the time the key was last used. Corrections are not available in this mode. Add use_llm: false, and no AI provider receives your text either: it is held in memory only while the request runs.

6. Who else receives it

We share data only with the providers we need to run the service:

• OpenAI or Anthropic receive your text and the instant result when you ask for the polished version, and write it through their API. Under their API terms they do not train on it, and they may keep it for a short time for abuse monitoring.
• Cloudflare, our network provider, carries all traffic to our servers over HTTPS.
• Our hosting provider runs the servers and database that hold the data described above.
• Paddle takes payments as our reseller and Merchant of Record, under Paddle’s privacy policy.
• Our email provider delivers your trial key and our replies.
• Google Fonts serves the fonts on this website, so your browser connects to Google, which sees your IP address.

We may also disclose data when the law requires it, or to protect the service and its users against fraud or abuse.

7. International transfers

Some of these providers process data outside your country, including in the United States and the European Union. Where data protection law requires it, these transfers rely on safeguards such as the providers’ standard contractual clauses.

8. Cookies and browser storage

We use no analytics, advertising or tracking cookies. If you paste your API key into the playground on the homepage, your browser keeps it in session storage so you don’t have to paste it again; it is gone when you close the tab. When you buy a plan, Paddle’s checkout runs on our page and may set the cookies it needs to process the payment and prevent fraud.

9. Security

All traffic is encrypted with HTTPS. API keys are stored only as one-way hashes, access to the database is restricted, and data is deleted on the schedule above. No system is perfectly secure; if a breach affects your data, we will tell you without undue delay.

10. Your rights

Depending on where you live, including under the EU and UK GDPR and Armenia’s Law on Protection of Personal Data, you can ask us to:

• tell you what personal data we hold about you and give you a copy;
• correct it, or delete it;
• restrict or object to how we use it, including use based on our legitimate interests;
• send it to you, or to another provider, in a machine-readable format.

Write to [email protected] from the email address on your account. We reply within 30 days. If your request is about text your own customers sent through your integration, we will help you answer it. You can also complain to the data protection authority where you live; in Armenia, that is the Personal Data Protection Agency.

11. Children

The service is built for businesses and developers. It is not directed at children under 16, and we do not knowingly collect their personal data.

12. Changes

We will update this policy when what we collect or who receives it changes. The date at the top always shows the current version. For a significant change, we will email customers before it takes effect.

13. Contact

Privacy questions, data requests, or a data processing agreement: [email protected]. The plain-language summary of how we handle your text is in Trust & privacy on our homepage.