LEGAL

Privacy Policy

What we keep, who receives it, how long it stays and how you delete it. Edition 2.2, 31 October 2026.

This is a translation. The Persian text at 1xai.ir/privacy is the binding version. Where the two differ, the Persian governs.

In edition 2.2: analytics no longer receives private links' codes or names; the text of a deleted creation goes at once; files for running code on our server go with the conversation; after an account is deleted, card-to-card receipt images stay with the payment records and voice-call history is erased; and a few sentences now match what the service does today. Some features are still switched on one at a time.

[01]PRIVACY · 01

What we keep

To create your account, answer your requests, bill you and support you, we keep the following. What you write and make in conversations is in the next section.

Account and identity: Email, password (only as a bcrypt hash), full name, national ID number and mobile number. We need the last three because each person has one account, a wallet with no known owner does not fit Iran's payment and tax rules, and support needs them to restore access. Once saved, only support can correct them, and every change is recorded with the previous value, who made it and their IP address. If you sign in with Google, we take only your email and Google account ID from Google.
Company account: If you create a company account: the company's name and domain and, for formal invoices, its legal name, national ID, economic code, registration number, province and city, address, postal code, phone and billing email.
Usage and cost: For each request: the model, token counts, the Toman cost, the response status and the time. We charge your allowance or wallet from these records and show them in your usage report.
Request text in usage logs: Next to each usage record we keep up to 64 KB of the request text and as much of the response, so you can see them in your usage report and we can find errors. In the site's chats, the system instructions (where your preferences, memory and project instructions live) are removed from this text, and a temporary chat keeps no text at all. The text is erased after 30 days, or sooner when you delete the conversation. Support sees the start of the response of failed requests to fix errors.
Payments: Amount, payment method, tracking number and the gateway's reply. From Digipay we also record the masked card number the gateway returns. For card-to-card transfers: the tracking number, the receipt text or image and any note you write; a receipt opens only for you and 1xAi admins. A proforma invoice keeps your name, national ID, mobile number and email as they were when it was issued.
Support: Ticket messages and their attachments, and the name, email and phone you give in the contact form or a ticket. If you ask for a phone call, the number is recorded too.
Sign-ins: If your settings show «داده‌ها و امنیت» (data and security), each sign-in to your account records the time, the sign-in method, your IP address, the country Cloudflare infers from it and your browser details, so you can see your sign-ins and, if you do not recognise a device, sign out everywhere else. Each sign-in is erased after 90 days.
IP address: Processed for security and rate limiting, and written to the server's request log. Apart from that it is stored only in a few security records: SMS code requests, changes to your name, national ID or mobile number, account deletion requests and, if they are recorded, your sign-ins.

[02]PRIVACY · 02

Conversations, files and memory

This data exists only when you use the feature in question. Some of these features are not yet on for everyone.

Conversations: Your messages, the replies, the text of files you attach and tool results (such as search, code runs or a service you connected) are saved in your account so you can see your history and continue, and they stay until you delete them. A document or spreadsheet the model makes, and any edit you make to it, is part of the same conversation, and the model is told which versions you wrote. On the site only you can see your conversations. Our admin panel has no tool for reading them; it shows only an answer you allowed in feedback, a conversation you shared, and the status of background jobs, which can include a conversation's title or a research run's questions and search queries.
Attachments: For documents (PDF, Word, Excel, PowerPoint, ZIP and text files) only the text stays in the conversation; the file itself is not stored. The two exceptions are under «Python» and «Running code on our server». Images you attach are stored as private files visible only from your account. Both are sent to the model provider to get an answer.
Audio files: If you attach an audio file (such as a recording of a meeting or a class), your browser cuts it into pieces where needed and each piece goes to OpenAI through our server to be transcribed. The audio itself is stored nowhere; the transcript stays in the conversation like the text of an attached document and goes to the model for the answer.
Temporary chat: It does not appear in your conversation list or search, gets no title, neither reads nor adds to memory, and is cleared when you close or reload the page. Its messages go to the model provider like any other chat. What remains: the usage records (model, tokens and cost, without text), the time and cost of voice calls, and any image or file you send or make in it, which is erased within 24 hours.
Memory: When memory is on, the assistant keeps lasting facts you state about yourself (such as your job, projects or preferences) and sends them to the model with your messages in later chats. Automatic learning sends your new messages and a short part of the replies to a low-cost model after replies, which may add, correct or remove up to five items per run; its cost appears in your wallet history as «به‌روزرسانی حافظه» (memory update). On the free plan automatic learning works only when you explicitly say «یادت باشه» (remember this). Both switches are on by default. Passwords, card numbers, IBANs, national ID numbers and API keys are never stored in memory, and automatic learning does not keep mobile numbers either. Memory is neither read nor written in temporary chats and company workspace chats.
Managing memory: Under «حافظه» (memory) in your personalization settings you see every item, add, edit or delete them, download the list and turn either switch off. Each conversation and each project has its own memory switch too. A deleted item is erased at once; only a hash of it remains, so the same wording is not saved automatically again. If you explicitly ask to remember it, its text waits up to 24 hours for your confirmation. The «پاک کردن کامل حافظه» (clear memory completely) button removes those hashes too. Deleting a conversation does not delete the items learned from it.
Skills: If you save a skill, its name, description, instructions and example stay in your account until you delete it. When you pick a skill for a message, its instructions go to the model with your message and its name is recorded next to your message. The skills export file is built in your own browser.
Suggested questions: If «نمایش پرسش‌های پیشنهادی» (show suggested questions) is on for you, after an answer your message and part of the answer go to a low-cost model, which suggests two or three questions to continue; its cost is recorded as «پیشنهاد پرسش بعدی» (next-question suggestion). The suggestions are stored with that answer and deleted with it. None are made in a temporary chat.
Feedback: If you rate an answer (thumbs up or down), the rating, the reason you pick and your optional comment (up to 1,000 characters) are recorded with the model's name, and our team sees them. The conversation text is visible only if you turn on the option to send it in the feedback form, and then only that answer and the question before it, not files, images or the rest of the chat. The option is off by default and does not exist in company workspace chats. We copy no text: when you clear the rating, turn the option off or delete the conversation, our access ends at once. Feedback is not sent to any company to train models.
Project files: A file you add to a project, both the file and its extracted text, is kept until you delete the file or the project. In each chat of that project, the relevant parts of that text go to the model with your message.
Images and video: Images and videos you make stay in your library with their prompts until you delete them, and only your account can see them. Deleting the conversation does not remove them. Those made in a temporary chat are erased after 24 hours.
Audio overviews: If you make an «پادکست صوتی» (audio overview) from a conversation or a project's files, that text (up to 40,000 characters) goes to the model that writes a two-host script, and the script goes to OpenAI to be voiced. The audio file and the script stay in your library (under «صدا», audio), only your account can play them, and deleting the conversation does not remove them. Overviews are not made in temporary or locked chats.
Songs: If you make a song, the description you write and any lyrics you give go to Google (its Lyria model); nothing else from the conversation goes with them. The song, with its description and lyrics, stays in your library (under «صدا») and only your account can play it; deleting the conversation does not remove it. A share link shows only a note that a song was made, without the file or the lyrics. Songs are not made in temporary chats.
Share links: If you share a conversation, anyone with the link can read it up to that message without signing in, and can make a copy for themselves. Your name and email, personal instructions, memory and the model's reasoning are not in the link, and files you sent appear only if you choose, as does Python output over those files. Results from services you connected and from running code on our server never appear. Your invite code is on the page, so a sign-up from it counts as your invite. We ask search engines not to index the page. The link stays public until you revoke it, lock the conversation or delete it; copies others made are not removed when you revoke it. Shared-conversation pages are not stored by Cloudflare, so a revoked link stops opening at once. Company workspace chats cannot be shared.
Locked chats: If you lock a conversation, it disappears from your conversation list and search, its share link is revoked, and it opens only with your four-digit PIN; its images and jobs are also hidden from the library and the jobs list until you unlock it. The PIN is stored only as a hash, and each unlock lasts, in that browser only, until 15 minutes after you last use it. Memory learns nothing from what is written in a locked conversation, even after the lock is removed. A lock hides the conversation from people who can use your device, not from us: what the admin panel shows of any conversation (see «Conversations») it shows of a locked one too. Company workspace chats cannot be locked. If the feature is turned off for you, the chats you locked stay locked and hidden and still open with your PIN.
Voice: For dictation, your audio goes to OpenAI; we keep neither the audio nor its text, and the text only lands in your message box. For read-aloud, the answer's text goes to OpenAI and stays in your usage report for 30 days, except in a temporary chat.
Voice calls: In a live voice call, your audio reaches OpenAI through our server and the audio itself is not stored. If calls with conversation context are on for you: your instructions, memory (in a personal conversation), the conversation's summary if it has one and up to its last 12 messages (shortened) go to OpenAI, whatever model the conversation uses; the text of each turn, what you said and the answer, is saved in that conversation (or a new one the call starts) like any other message, and memory learns from it as from the rest of the conversation; and the call's start and end, its number of turns and frames and its cost are recorded, without text, and erased when the account is deleted. In a temporary chat the call's text is not saved. If you turn on your camera or share your screen during a call, frames from it go to OpenAI and none is stored. Without these options, the call's text is not saved and only its usage and cost are recorded.
Web search and research: When search is on, the query goes to OpenAI's or Google's search tool, marked as a search from Iran; your IP is not sent. Our server fetches the pages and site icons that are read, so those sites see our server's address, not yours. Deep research works the same way.
Python: If Python is on for you, the code the model writes runs in your own browser, not on our server, and has no internet access from there. Data files you attach (CSV, TSV, Excel and JSON, marked «آمادهٔ تحلیل با پایتون», ready for Python) and the images and files a run makes are stored as private files so the code can reach them again, and stay until the conversation is deleted; in a temporary chat, 24 hours. The model sees a short preview of each data file (up to 6,000 characters); each run's code and output go to the model like other tool results and stay in the conversation.
Running code on our server: If running code on our server is on for you and you attach a ZIP file (a programming project, say), besides reading its text, its files are unpacked on our own server so the model can run and test code there. Each run happens in a separate container with no internet access. The files are erased 24 hours after the upload, or sooner when you delete the conversation. The output of commands and the files the model reads go to the model and stay in the conversation like other tool results. The ZIP's name, its file count and size, and each run's time, duration and CPU use, without the command or its output, are kept separately and erased two days after the files are; deleting the conversation erases the file's name at once.
Connections: If you connect a service under «اتصال‌ها» (connections), its address, the token you give (encrypted) and the list of its tools stay in your account until you remove the connection. When the model uses one of those tools in a conversation, our server sends the service the input the model wrote for that tool, which may come from the conversation; your name, email and IP do not go with it. The result goes to the model and stays in the conversation, and that service handles the data under its own policy. A tool the service itself has not declared read-only asks for your permission before it runs. Connections are not used in temporary chats.
Scheduled tasks: If you schedule a task, its prompt, schedule, model and target conversation are kept until you delete it. At each run our server, without you being online, sends that prompt to the model with what goes with an ordinary message (instructions, memory in a personal conversation, the project and the conversation's latest messages) and, if you turned search on for the task, runs one web search first. The prompt and the answer are saved in that conversation and charged like other messages. The run history (time, status and cost) is kept for 180 days, even if you delete the task.
Browser notifications: If you turn on browser notifications, the address your browser gives for notifications, its encryption keys and the name of your browser and operating system (such as «Chrome · Android») are kept until you turn them off or the browser revokes them; at most 10 devices. When research, a video or another long job finishes, or an answer that took more than 30 seconds arrives while you were away, we send a notification with the kind of job and the conversation's title (or a file's name); for a locked chat only «یک گفتگوی قفل‌شده» (a locked conversation). The encrypted notification travels through your browser maker's push service (Google, Mozilla, Apple or Microsoft), which cannot read it, but it shows on your device's lock screen. A record of the notices sent, without text, stays for 7 days.
Importing conversations: If you import your conversations from a ChatGPT or Claude export, your browser takes only the conversations file out of the ZIP and sends it compressed, so the images and files inside never leave your device; a browser that cannot do this sends the file itself, if it is small enough. The uploaded file stays on our server as a private file until the import ends and, if it is left behind for any reason, is erased about a day later. The conversations' text is saved in your account like any other conversation and stays until you delete it; images, attachments and the model's reasoning are not imported. No text goes to a model provider for this, and memory learns nothing from the imported text. «حذف گفتگوهای این انتقال» (delete this import's conversations) deletes every conversation of that import.
Importing memory: If you paste what another assistant knows about you and ask for a preview, that text goes once to a low-cost model to be turned into memory items, and its cost is recorded as «به‌روزرسانی حافظه». The text itself is neither kept nor left in your usage report; only the items you pick and save are added to memory.
Telegram and Bale: If you link your account to the Telegram or Bale bot, your numeric ID in that messenger and your chosen model are kept. If bot conversations are saved to your chat history, you see them in your conversation list marked «از تلگرام» or «از بله» (from Telegram, from Bale): like the site's conversations they stay until you delete them and you can continue them on the site, and your link remembers which conversation the bot is continuing. Otherwise bot conversations are not saved: only the last eight turns stay in the server's working memory, for up to two hours after the last message, so the bot keeps the thread. Questions you ask the bot in a group are never saved, and bot conversations add nothing to memory. Each message's usage and cost are recorded without text, like everything else.

[03]PRIVACY · 03

What we do not keep

Your bank card number: we never ask for it, and the bank's gateway takes the card details.
Your password or your locked-chat PIN in readable form; we keep only their hashes.
Dictation audio, audio files, voice-call audio, or camera and screen frames from a call. Dictation text is not stored either; the text of an audio file or a call is kept only as section 2 says.
The original file of a document you attach in a chat; we keep only its text, except data files for Python and a ZIP file for running code on our server (section 2).
Passwords, card numbers, IBANs, national ID numbers or API keys in memory.
Text you paste to import memory.
Your IP address alongside your conversations or usage records.
Advertising cookies or advertising tools.

Identifying headers are stripped. Your IP address, browser details and language are removed before a request reaches the provider, and your name and email do not travel with it.

[04]PRIVACY · 04

How the data is used

Running the service: Getting your request to the model and the answer to you, keeping history, memory and files, titling conversations, running the tasks you scheduled and sending the notifications you asked for.
Billing: Computing the cost, charging your allowance or wallet, invoices and usage reports.
Support: Answering tickets, checking usage and payments in disputes, and restoring access to your account.
Security: One account per person, stopping gift credit from being claimed twice, rate limiting and showing you your sign-ins.
Improving the service: Feedback you choose to give and aggregate site analytics.
Messages to you: Account emails (verification, password reset, invoices, debt and ticket replies) are always sent. Reminders (such as unused credit or an expiring gift) may come by email, SMS or the Telegram bot; in reminder emails we record opens and clicks on the button. If you turn off reminder emails in settings, or use the unsubscribe link in any email, reminder emails and reminder SMS stop.

We do not train models on your data, and we do not sell it.

[05]PRIVACY · 05

Companies, schools and the learning panel

Company workspace: Your chats in a company workspace are yours, and others cannot read them on the site. Company members see each other's names and emails, and members of a workspace see its usage report per member: name, email, requests, tokens and cost. The company's owner, admins and billing members see that report for every workspace of the company, and the owner and admins see every ticket filed in the company's name; billing members see its billing and top-up tickets. Company chats use no memory, cannot be shared and send no text with feedback. If you leave the company, your chats stay with you but can no longer continue on the company's account.
School: If you belong to a school in the learning panel, the principal and your class teacher see your learning-panel activity: answers and accuracy, study time, finished lessons, mastery, test scores and streaks. A student's email is not shown to them.
Learning panel: Your practice answers, tests, progress and points, and the files and answer sheets you upload, stay in your account. Leagues are optional and show a name you type or an alias, never your account name. The Friday mock exam table shows that name or alias with your score per subject to signed-in users. A link you make to a mock result opens without signing in. Questions and answer sheets go to the model providers for grading and explanation.

[06]PRIVACY · 06

Who receives data

We sell your data to no one. These receive it to do what you asked, and each handles it under its own policy:

Model makers: Your message and what goes with it (file text, images, memory, your instructions and skills, parts of project files and tool results) go to the maker of the model you chose: OpenAI, Anthropic, Google or DeepSeek. Conversation titles, memory updates and imports, suggested questions and audio overview scripts use a low-cost model from the same providers. Images are made by OpenAI or Google, video and songs by Google. Speech and audio-file transcription, read-aloud, overview voices and voice calls are OpenAI's.
API reseller: We buy Grok (xAI), Kimi (Moonshot), GLM (Zhipu), Qwen (Alibaba), MiniMax and Hunyuan (Tencent) from an API reseller, and requests for those models reach the maker through it.
Our relay server: Some requests to Claude and GPT models reach Anthropic or OpenAI through a separate server that we run.
Not sent with requests: Your name, email and IP address. Some requests to OpenAI carry an internal conversation number so the repeated part of a request can be read from their cache. We ask OpenAI not to keep requests in its logs. If you use the API, your request body arrives as you sent it.
Services you connect: If you connect a service under «اتصال‌ها» (connections), the input of the tools the model uses from it reaches that service from our server (section 2).
Browser push services: If you turn on browser notifications, they travel encrypted through your browser maker's push service (Google, Mozilla, Apple or Microsoft).
Payment gateways: Zarinpal: the amount, a payment description containing your email (or the company or school name), and your email. Digipay: the amount, your mobile number and, where needed, the items bought. SnappPay, when enabled: the amount, the items and your mobile number. These requests reach the gateway through our relay server in Iran. For card-to-card, you transfer the money to our card yourself and send us only the receipt.
Email: Emails are sent through Resend, which receives each email's address, subject and body.
SMS: Verification codes and reminder SMS go through an SMS provider, which receives the mobile number and the message text.
Google sign-in: If you sign in with Google, Google learns of that sign-in.
Infrastructure: Our main servers are outside Iran and the site's traffic passes through Cloudflare's network. Encrypted backups are kept in Telegram.
Team notifications: Notices our team receives about new tickets or payments arrive by email or a Telegram bot and may include your name, email or part of your ticket.

[07]PRIVACY · 07

Cookies and analytics

1xai_sess: Keeps you signed in, for 7 days. It holds only your account ID, role, terms-acceptance state, the time the cookie was made and, if your sign-ins are recorded, the ID of this sign-in, and is signed against tampering.
1xai_gs_…: Only during Google sign-in, for 15 minutes, so the browser that started the sign-in is the one that finishes it.
1xai_unlock: If you unlock a locked chat, until 15 minutes after you last use it. It is tied to this sign-in and this PIN, and stops working when you lock again, sign out or change the PIN.
1xai_ft: How you first found us, for 90 days: the address of the first page you opened without its parameters (for private links, such as a shared conversation or a gift envelope, only the section's name, such as /share), the site you came from and utm parameters. At sign-up it is saved on your account and copied onto your payments, so we know where customers come from. Addresses stored earlier with their parameters were rewritten without them on 31 October 2026.
1xai_ga_signup, 1xai_ga_purchase: Only after a sign-up or a successful payment, for up to 10 minutes: the sign-up method, or the internal payment number, amount, tax and kind of purchase, so the next page reports it to Google Analytics and deletes the cookie.

Google Analytics loads to count visits and a few events (such as clicks on rewards, the start of a payment, a sign-up and a successful payment with its amount and kind) and sets its own cookies. The addresses of the pages you open reach it, but no conversation text, email or API key does, and it never loads on shared-conversation pages. The code in a private link does not reach it either: email verification, password reset, company or class invitation and Telegram connection links arrive without their code, and exam result cards, weekly reports for parents, friend challenges and gift envelopes only as the section's name (such as /learn/p) and without the page title, which may carry a name. If your browser blocks it, the site still works.

Display settings, drafts (such as a ticket's text) and a few choices (such as the feedback text option) stay only in your own browser's storage.

[08]PRIVACY · 08

How long data is kept

Account and identity: Until the account is deleted; the history of name, national ID and mobile number changes is deleted with the account too.
Sign-ins: If recorded, 90 days.
Conversations, attachment text, feedback: Until you delete them; nothing erases them automatically. The same goes for imported conversations, voice-call text and scheduled tasks' answers.
Images attached in chats and Python files: Until the conversation is deleted; then the file's name is erased at once, the file usually within two days and its record 30 days later. In a temporary chat, 24 hours.
ZIP files for running code on our server: 24 hours after the upload, or sooner when the conversation is deleted. Its name and size, and the time and CPU use of runs, without commands or output, two days after the files go; deleting the conversation erases the name at once.
Images, videos and audio you make: Until you delete them from your library; deleting erases the prompt and an overview's script or a song's lyrics at once, and usually the file too. Only its technical details (such as kind, model, size and time) stay in the record for 30 days, then go. In a temporary chat, 24 hours.
Project files: Until the file or project is deleted; then erased within minutes.
Memory: Until each item is deleted. Hashes of deleted items stay until you clear memory completely.
Skills, connections and scheduled tasks: Until you delete them. Task run history, 180 days, even after the task is deleted.
Browser notifications: Each device until you turn its notifications off or the browser revokes it; the record of notices sent, 7 days.
A file you upload to import conversations: Until the import ends; if left behind, erased about a day later.
Share links: Until revoked or the conversation is deleted. Revoking erases the content; only the address is set aside so it is never given to anyone else.
Request text in usage logs: 30 days, or sooner when the conversation is deleted.
Usage and cost records: With no erasure date, for accounting, reporting and disputes. The same goes for the time, turns and cost of voice calls, until the account is deleted.
Payments, invoices, proformas: At least 10 years, as accounting law requires; card-to-card receipt images too, with those records.
Support tickets: Messages stay; attachments are erased 180 days after the ticket closes.
SMS verification codes: The code itself is not stored; the request record is erased a day after the code expires.
Sent-email log: 180 days.
Data exports: Erased 7 days after they are ready.
Learning panel: Until the account is deleted. A file or answer sheet you delete is erased at once.
Telegram and Bale bot: If bot conversations are saved to your history, like the site's conversations, until you delete them; otherwise no text is stored and the last eight turns stay in working memory for up to two hours. Group questions are never saved.
Backups: Every hour we keep an encrypted copy of the database and of the private files still in use (images and files of conversations and the library, ticket attachments and card-to-card receipt images) away from the server, so nothing is lost if the server is; a file you upload to import conversations and a data export are not in it. These copies are not erased automatically today, so something you delete may remain in older copies. If we ever restore the service from a backup, we delete again the conversations, memory, projects, files and links you had deleted before, and any account whose deletion had been carried out.

[09]PRIVACY · 09

Deleting data and your account

You can delete any conversation, memory item, skill, project file, image, video, audio, share link, scheduled task, connection or notification device yourself at any time; when each is erased is listed in section 8.

If your settings show «داده‌ها و امنیت» (data and security), you can take a full export of your data there: a ZIP with your conversations, memory, projects and their file lists, a list of your images and files, transactions, usage (without text) and sign-ins. You can make one a day, only you can download it, and it is erased after 7 days.

To delete your whole account, if your settings show «داده‌ها و امنیت», ask there (you first confirm your identity once more with your password or a code we send to your verified email or mobile); otherwise send a request through the contact form. Then:

One of our admins verifies your identity before anything else.
The deletion is not carried out sooner than 7 days after the request, and until it is, you can withdraw your request.
If your wallet has a balance, we settle it under the Terms of Service before deleting; deleting the account sets the wallet to zero.
If you own a company workspace or run a school, or a company is billed to your wallet, first hand it to someone else or delete it.
An admin carries out the deletion within 30 days of verifying your identity and, if your email is verified, tells you by email.

Deleted: conversations, memory, skills, project files, images, videos and audio, share links, scheduled tasks, connections and their tokens, notification devices, API keys, Telegram and Bale links, learning-panel data, sign-in and voice-call history, the history of name, national ID and mobile number changes, files you sent in tickets and the attachments of your personal tickets, and your account details.

Kept, because the law requires it or to prevent abuse:

Payment, invoice and proforma records for 10 years, without your name, national ID, email or mobile number; the amount, the tracking number and the masked card number the gateway returned stay.
The amounts, times and models of your usage, voice calls included, without text.
Card-to-card receipt images, with those payment records; a name or card number printed on the receipt stays in the image.
The text of support tickets, without your name, email or number.
Which version of the Terms you accepted, and when.
A hash of your email, mobile number and national ID, so a new account with them cannot claim gift credit again.

Deleted data may remain in encrypted backups; see section 8.

[10]PRIVACY · 10

Contact

For any privacy question, use the contact form or email support@1xai.ir.