Privacy Policy — Redrafty

This policy explains what happens to the text you send to Redrafty (@RedraftyBot), who else can see it, how long we keep it, and how to delete it. We wrote it to be read on a phone, not by a lawyer.

If something here is unclear, send /support in the bot or use the contact form at redrafty.com/contact, and we will explain it in plain words.

1. The short version

All five tools send your text to an AI provider we work with. That means Detect, Rewrite, Summarize, Explain and Feedback; any tool we add that reads your text with a language model will work the same way. Your paragraphs leave our systems and are processed by a specialist AI provider in the United States (section 4). There is no way around this — it is how these features work.
We keep text for a short time, and we do not keep it forever. Your original text sits in memory for up to 24 hours so the buttons under the result keep working. Processed paragraphs are cached for 7 days, then up to 30 days, then deleted automatically.
We do not train anything on your texts or your results — ever. Not even with your permission: there is no switch for it (section 6).
You can delete your data any time. The Privacy screen in the Mini App has a 🗑 Delete my data button: confirm once and your support requests, username, time zone, activity hours and text fingerprints go immediately. What stays: your balance and payment records — that is your money — processing records without text until they expire, and cached paragraphs that carry no link to you and expire on their own. Encrypted backups catch up within 8 days. Details in section 7.
Telegram can see every message you send to the bot. That is a property of the platform, not a choice we made. See section 8.

2. What we handle

Your text. Whatever you paste or upload for any of the five tools — Detect, Rewrite, Summarize, Explain, Feedback. This is the sensitive part, so most of this policy is about it.

Your Telegram account details. Telegram gives the bot your numeric user_id, your username if you have one, and your interface language. We do not receive your phone number, your contacts, or your other chats.

Your settings. Which tool is active, the style, strength, person and "don't touch" choices, the Rewrite mode, the Summarize length, the Feedback audience, format and depth, your interface language, and whether the low-balance reminder is on. We do not store a choice of answer language: every tool replies in the language of your text, which the bot works out for itself.

Your credits and payments. Credit balance, purchases, bonuses, referral rewards, and spending. For each Telegram Stars purchase we store the amount, the date, and the Telegram payment ID.

We never see your card, bank account, or any payment credential. Telegram handles payment; we only receive confirmation that Stars were paid.

Job records. For every processing request we store a hash of the input, the tool and model used, the language the text was written in, token counts, cost, and status. The hash is not the text and cannot be turned back into the text. The language is stored because it sets the price — different writing systems cost different amounts to process — and because it is what tells us which results to trust when we check our own accuracy.

Requests that never became a job. If a file is rejected, a text is too short to check, or something breaks before we start, we store what happened — the reason, the size, the file type — and no text.

Support tickets. When you write to support, we keep your message (up to 500 characters), what you were doing at the time, and our reply.

Messages from the contact form on our website. If you write to us at redrafty.com/contact, we keep the topic you chose, your message and the contact you gave us (a Telegram username or an email address) — only so we can reply. We do not store your IP address.

Errors you saw. If the app failed to open, a button did nothing, or the bot went quiet, we store that it happened, on which surface, and an error code — so the same fault can be found and fixed. No text, and nothing you typed.

Detection records. For every Detect run we store a hash of the text, the scores, the result we showed you, and the version of the detector that produced it.

We do not write your original text into our database — in any case. It lives in memory for up to 24 hours and is then deleted (section 3); processed paragraphs are cached with no link to you (section 5); nothing is kept to train or tune a model (section 6).

We never write your text into our logs. Not in production, not in debug mode, not on a developer's machine. This is enforced in code, not just by policy.

3. What happens to your text, step by step

When you send text

Your message goes from your phone to Telegram's servers, then to our server.
We store the text in memory (Redis) under a random ID so the buttons under the result work. It is compressed and expires after 24 hours. Your raw text is never written to our main database.
We split it into paragraphs and calculate a price.

If you press Detect

The text is sent to our main AI provider (section 4), which checks it and returns the scores — on the same terms as the other tools: not retained by default, never used for training.
We save the scores plus a hash. Not the text.

If you run Rewrite (costs credits)

These two work paragraph by paragraph.

We check our cache first. If the exact same paragraph was already processed with the same settings, we reuse the stored result, and no new request leaves our server for that paragraph.
Paragraphs that are not cached are sent to our AI provider for processing (section 4).
The result comes back, we assemble it, send it to you, and store the processed paragraph in the cache.

If you run Summarize, Explain or Feedback (costs credits)

These three read the whole document at once: an answer about a document cannot be assembled out of answers about single paragraphs.

Your text is sent to our AI provider as one request (section 4).
The result comes back and we send it to you.

After 24 hours

Your original text is deleted from our memory automatically. The next-step buttons under old results — the 🔍 check offered after a Rewrite — stop working. That is why, not a bug.

4. Who else gets your text

We do not sell your data. We do not publish it. We do not share it with advertisers or data brokers.

Your text reaches exactly two companies: our AI provider and Telegram (which delivers every message). Here is what each one gets.

Separately, your payment travels through Telegram and, depending on your device, through Apple or Google — they process the Stars transaction and see that a payment happened. They never see your text.

Our AI provider — for all five tools

Who it is: one specialist AI company that provides the language models behind all five tools, and behind reading photos and scans. Where: the United States.

We don't publish its name, the same way most services don't publish their infrastructure suppliers. What they get, where it goes and what their policies say about keeping it is set out right here — that is the part that affects your text.

What it gets: the paragraphs you asked us to process, plus our instructions. Nothing that identifies you — no user_id, no username, no email. It cannot tell whose text it is.

What we have secured, and what the provider's published policy states:

For the models we use, prompts and outputs are not retained by default.
Retained data is never used to train models without express permission, and we have not given such permission.
Where prompt caching is used, prompts and outputs are not stored; internal cache representations stay in memory for the cache lifetime and are deleted after it expires.
We do not use any of the model variants their policy treats as exceptions to the above. If that ever changes, we will update this page first.

Photos and scans. When you send a photo of text or a scanned PDF, the page images go to the same provider so it can transcribe the text — on the same terms: not retained by default, never used for training. We don't keep the images; we record only how many pages were recognised and what it cost, without the text, for up to 90 days.

Links to Google Docs. If you send a link to a document that is shared as “Anyone with the link”, our server downloads it from Google to read the text — exactly as if you had sent the file — and keeps nothing. We never open any other links.

Detect goes to the main provider, on the same terms.

Telegram — the platform and the payment processor

What they get: every message you send to the bot and every message the bot sends you, because they deliver them. Plus your payment, because Telegram Stars is the only payment method Telegram allows for digital services.

Telegram's privacy policy: <https://telegram.org/privacy>
Telegram's terms of service: <https://telegram.org/tos>

Where our data lives — hosting and backups

Our server is rented from Hetzner, in Helsinki (EU). The database sits on an encrypted disk.

Backups. Every night we make an encrypted copy of our database and keep it with Backblaze, a storage provider in the EU. We encrypt it on our server before it leaves, and the key stays with us, so Backblaze holds files it cannot read. Your original text is never in them — it never reaches our database.

Apart from the infrastructure that runs our own service, those are the only two companies that ever receive your text.

5. How long we keep things

Your original text — up to 24 hours. Held in memory only, deleted automatically. Never stored in our database.

Processed paragraphs (the cache) — 7 days, then up to 30 days. Cached results move from fast memory to our database and are deleted automatically when they expire.

One honest detail about the cache: cache entries are stored by the content of the paragraph, not by who sent it. There is no link from a cache entry back to you, and no way to look up "what did this person send". The flip side is that if the same paragraph is requested again — by you or by anyone — the 30-day clock restarts. A paragraph nobody asks for again is deleted on schedule.

Job records — 30 days. These contain a hash, token counts, size, cost and the version of the rate table used. No text.

To be plain about what that means in practice, because a summary can be a half-truth: we keep a record of which tool you used, which settings, how many words, when, and what it cost. We need these to keep your balance correct, to answer support requests, and to restore credits when something breaks. Your text is not in them — only a hash of it, which cannot be turned back into the text.

Job records also hold the number of the chat message we replied with — an integer like 48213. This is what the ↗ button in your history uses: it does not contain your text, it points at a message that lives in your Telegram chat, not with us. That is why the button still works long after the 24 hours are up — the result is in your chat, and we only remember where. The button stops working after 30 days, when the job record is deleted; the message itself stays in your chat until you delete it.

Detection records — up to 90 days. Scores, markers, a hash and the detector version — never text. They are linked to your account until we anonymise them; the 🗑 Delete my data button removes that link immediately, and the record itself lives out its 90 days with nothing in it that points at you.

Support tickets, contact-form messages and the errors you saw — 30 days. Long enough to answer you and find a pattern, short enough that nothing lingers.

Your account, settings and credit balance — as long as your account exists.

Other people's personal data — please don't send it. Some things you might want processed contain information about someone else: a teacher's written comments, a photo of an assignment sheet with names on it, an email thread. We are not able to ask those people for their consent, and we would rather not hold their data at all. Remove names and identifying details before sending, or don't send those documents.

Payment and credit records — kept as financial records. These are amounts, dates and payment IDs. They contain no text from you at all. We keep them because we have to be able to reconcile money that moved.

Backups — up to 8 days. An encrypted copy of the database is made every night and kept for up to 8 days (section 4). When you delete your data, it leaves our live database at once and the backups as the older copies expire — within 8 days. We open a backup only to restore the service after a failure.

6. No training on your texts or your results

We do not train or tune any model on anything you send or receive — your texts, files, photos and scans, the results we return, your Detect scores, your support requests, or how you use the app. Not our own models, and not anyone else's.

Not even with your permission. There is no switch for it, so there is nothing to turn on by accident and nothing to withdraw later. Your text is used for one thing only — completing the request you made — and is then deleted on the schedule in section 5.

How our AI check is tuned instead. We test and calibrate 🔍 Detect on public texts written by people before AI writing tools existed and on texts we generate ourselves for that purpose — never on what our users send.

Our AI provider does not train on your text either (section 4): it never uses retained data to train its models without express permission, and we have not given that permission.

One clarification about the 24 hours. That clock is about our servers. Your chat with the bot lives on Telegram's servers for as long as you keep it — every text you sent and every result you got back stays in that chat, synced across your devices. The bot does not delete anything from that chat — clearing it is up to you, from Telegram itself (section 7). If you want a result kept somewhere else, forward it — the chat is already your archive.

7. Your rights

Delete everything. Open the Mini App → Privacy → 🗑 Delete my data. The screen that opens lists what will go, asks you to tick "I understand this cannot be undone", and then does it — immediately, not "within 30 days", and not on a nightly schedule.

What the button deletes, for good:

your support requests, with our replies
your Telegram username and language, and the link you came through
your time zone and the hours you are usually active
the hashes of your texts in your processing records
the account link on your detection records
the errors you saw, and photo-recognition records older than today (today's stays only to keep the daily limit)

What stays, and why:

Your credit balance, purchases, level, credit history and what you earned for inviting friends — that is your money, and these records are the proof of what you bought and spent. Amounts, dates and payment IDs; we need them to reconcile money and to honour credit restorations, and they contain none of your text. You do not lose credits by deleting your data.
Processing records without text — which tool, how many words, what it cost — until they expire, because your credit history refers to them.
Shared cache entries — processed paragraphs, stored by the content of the paragraph and not by account. Nothing in them points back to you, and they expire on their own within 30 days.
Encrypted backups — what you deleted leaves them as the older copies expire, within 8 days (section 5).

Deleting your data does not close your account: if you keep using Redrafty afterwards, new records appear again, the same way they do for anyone.

If you would rather we did it, message us (/support in @RedraftyBot, or the contact form at redrafty.com/contact): we run the same erase on your account by hand and write back when it is done.

Close the account itself. The account record cannot disappear completely: your payment records have to belong to an account, so the bare record — your Telegram number, balance and purchases — stays, holding nothing else. If you want the account closed all the same, message us (/support in @RedraftyBot, or the contact form at redrafty.com/contact): we run the same erase by hand, switch off every offer and announcement for it, and write back when it is done.

Clear your Telegram chat. Everything you and the bot have said also sits in your Telegram chat, like any other conversation. The bot does not delete messages there. To remove them, open the chat with the bot → the menu at the top right → Clear History.

Keep the two apart, because they do different jobs: clearing the history removes the messages in Telegram; the delete button removes what we hold on our servers. Neither one does the other's work, and you can do either, or both.

See what we hold, and get a copy. Mini App → Privacy → 📄 What we store about you shows the real counts for your account. 📦 Send a copy of my data to the chat sends everything we store about you as one file (redrafty-my-data.json) to your chat with the bot — records of processing, checks, purchases, credits and support requests; your texts are not in it, because we do not keep them. You can also send /support in the bot and we will tell you what is stored under your user_id. We aim to answer within 24 hours, and within 48 hours over a weekend.

Stop using the bot. Press 🗑 Delete my data, then block the bot. We are not going to email you — we do not have your email.

8. Limits we cannot get around

We would rather say these out loud than have you discover them.

Telegram sees everything you send to this bot. Chats with bots are ordinary cloud chats. They are not end-to-end encrypted, and they cannot be. Telegram stores them on its servers and can read them. This is true of every Telegram bot, including ours. If your text is so sensitive that Telegram must not see it, do not send it to a Telegram bot — ours or anyone's.

The bot does not delete your chat. Every text you sent and every result stays in your Telegram chat until you remove it, whatever we do on our side.

To clear the chat, do it from Telegram. Open the chat with the bot → the menu at the top right → Clear History. That removes the whole conversation from your side.

These two things are different:

Data in our database — deleted immediately when you press 🗑 Delete my data; the encrypted backups catch up within 8 days.
Messages in your Telegram chat — yours to clear, with Telegram's own Clear History. That clears your chat, and it leaves our records alone — the delete button is what reaches those.

We cannot delete anything from our AI provider's side. Its published policy says prompts and outputs are not retained by default, so in normal operation there should be nothing to delete — but that is their statement about their systems, not something we can verify or act on.

9. Changes to this policy

If we change how we handle your text — a new provider, a different retention period, anything that matters — we will update this page and change the date at the top. For changes that affect what leaves our server, we will tell you in the bot before the change takes effect, not after.

10. Contact

In the bot: /support — the same form as in the Mini App, and it works when the Mini App does not
Contact form: redrafty.com/contact — if you can't use the bot

Write to us in English or any language the app supports. Ask anything about this policy — including questions it does not answer.