1. What this document covers
This explains what Banafsh collects when you use the service, why, who it is shared with, and what control you have over it.
This is version 2.4.
2. What we collect
Mobile number: to sign you in and identify your account. A one-time code is sent to you through an SMS provider.
First and last name: optional, only if you enter them in your profile. Also your chosen language.
IP address and country: for security, abuse prevention and geographic restrictions. They are written to the audit log when an account is created, when a request is blocked and for the other sensitive events listed under “Audit log” below; the audit log is kept as described in section 7. This is separate from the sign-in history listed below, whose IP addresses are removed after 90 days.
Chat content: only if “save chat history” is on. With it off, no message is ever written.
Attachments: images you upload into a chat.
Financial information: wallet balance, transactions, redeemed top-up codes and subscription state. We do not receive or store your bank card details.
Feedback you send through the feedback tool, together with the page it was sent from.
Sign-in history: for every sign-in and every failed sign-in attempt we record the time, whether it succeeded or failed (and why), your IP address, the country and the approximate city and region worked out from that IP address (an estimate that may be wrong), and the type of browser and device used. The record is linked to your account, and your mobile number or email address appears in it only partly hidden. If a mobile number or email address that has no account is tried, the failed attempt is recorded without that number or address, and without any account.
Telegram bot: if you use the Banafsh image bot on Telegram, we record your Telegram numeric ID and display name, the chat ID, the descriptions you send, the images generated, your acceptance of the terms and this policy, and your balance and the amounts charged.
Audit log: sensitive events such as account creation, acceptance of terms, key issuance and support actions.
3. Why we process it
To provide the service itself; to bill accurately; for security and abuse prevention; to support you; and to meet legal obligations.
The sign-in history is used to keep your account secure and to improve the service. Only our staff can see it.
Public gallery: if you tap “Share to the gallery” in the bot, we show that picture and the text of its description publicly in Banafsh's Telegram channel and, only if you allow it, your Telegram username under it. This happens only through your own action, is removed by withdrawing the post, and copies that Telegram or its users keep are outside our control. For safety we check the picture automatically, and sometimes by a person, before it is shown.
We do not sell your information or make it available to others for advertising.
4. Your chats
“Save chat history” is yours to control in settings. Turn it off and chat still works, but nothing is stored.
When it is on, message titles and text are stored encrypted (AES-256-GCM).
You can delete any single conversation, or all of them at once, from inside the app.
To produce a reply, your message must be sent to a model provider; see section 6.
5. Attachments
Files are stored outside the public web path and are readable only through a signature-gated endpoint.
Images are re-encoded before storage, and EXIF metadata — including GPS location — is stripped at that point.
An attachment not linked to a stored message is deleted automatically after about an hour. For a user with history off, it is deleted immediately after being sent to the model.
6. Who we share it with
SMS provider: your mobile number, to deliver your sign-in code.
AI model providers: your message text, attachments and image descriptions are sent, through our gateway, to our AI service provider and the model suppliers it uses. A reply or image cannot be produced otherwise. Under the terms we have with these providers, they do not use your content to train models. Some suppliers may keep descriptions and outputs flagged by their safety systems for a limited time to check for abuse; we do not control that retention.
Telegram: your messages with the bot travel through Telegram's servers and are subject to Telegram's own policy. To reach Telegram we use a relay server that we operate, which only passes messages through and does not store their content.
Voice notes: if you send the bot a voice note, the audio is sent for transcription to our AI service provider and its supplier. Under the terms we have with them, this supplier does not use your audio to train models and may keep it for a limited time to check for abuse.
Feedback analysis: where enabled, your feedback text is sent to an external AI service for automatic categorisation, and may be recorded in our issue tracker (a private repository).
Infrastructure: hosting, database and backups.
Sign-in history: not shared with anyone. The country, the approximate city and region, and the device type are worked out on our own servers; your IP address is not sent to any outside service.
Authorities: where legally required.
7. Retention and deletion
Chats are kept until you delete them, or until you close your account.
Closing your account deletes your chats and attachments immediately — not on a later schedule.
Account and financial records — including the transaction ledger — are kept while the account is active and, including after you close it, for as long as tax and commercial law requires. They remain visible to Banafsh staff.
Any wallet balance you hold when you close your account is frozen, not deleted: it stays on the account but cannot be spent, and is written off to zero 180 days after closure if the account is not reopened.
Sign-in history: each record is kept for 12 months and then deleted. The IP address in a record is removed after 90 days, and at once when you close your account; the rest of the record (time, result, country, approximate city and region, browser and device type) stays until the 12 months are up.
The audit log is append-only and deliberately survives deletion of user data; that record is needed for security and accountability.
The database is backed up in encrypted form and those backups are retained for several months. Deleting a record therefore does not immediately erase it from every backup, though backups are not used unless restored and age out on their own cycle.
Images and videos made in the Telegram bot or on the website: the generated image or video and the text of its description are kept for 14 days for your history and then deleted; you can delete them yourself sooner, except an image you have reported. If you report an image, that image and its description are kept for 30 days from the report so that we can review it, then deleted. Closing your account deletes all of them at once. The copy that stays in your Telegram chat is held by Telegram and we cannot delete it.
8. Security
Your chat text and your keys are stored encrypted, and the encryption key is held separately from the data.
Admin access is restricted to an internal network, and every support action on your account is written to the audit log.
No system is completely safe; we take care, but we cannot guarantee absolute security.
9. Your rights
Access and correction: you can view and change your profile information.
Deleting chats and attachments: from inside the app, at any time.
Not storing anything: by turning chat history off.
Closing your account: available at any time from Settings inside the app. It ends your access immediately, deletes your chats and attachments right away, and revokes every API key. As explained in section 7, financial and audit records are retained and any remaining balance is frozen rather than deleted. Reopening a closed account is not self-service — contact us at privacy@banafsh.com — and reopening does not restore deleted chats or grant a second welcome credit.
For any question about your data, write to the same address.
10. Cookies
We use a single essential cookie to keep you signed in. There are no advertising or third-party tracking cookies.
11. Changes to this policy
If we change this policy materially, the version number goes up and you will be asked to accept the new version the next time you sign in.
12. Contact
For any privacy question or request: privacy@banafsh.com