Skip to content

Privacy policy

What we collect about you and why, who receives it, what we store in your browser, and how to use your rights over your data.

Version 1.2Last updated: October 22, 2026

Who is responsible for your data

The controller of the personal data we collect through the website, the 5abeer AI app and the API is the business that provides 5abeer and is the seller in every purchase on the site. Its full details are under "Who we are" in the terms of service.

For anything about your data, write to us with "Data protection" in the subject line. We will add the name of our data protection officer here once they are registered with Egypt's Personal Data Protection Center.

In short

  • We collect your account data, your usage records including your IP address, your payment records, and the content of your requests and chats.
  • We use them to provide the service and bill for it, to prevent abuse, and to contact you about your account.
  • Your requests go to the companies that develop the models, or to partners that run access to them, and many of our providers are outside Egypt.
  • In the support chat, an AI assistant answers you first, so your messages reach the companies that develop the models after sensitive data is removed from them; you can ask for a person at any time.
  • We do not sell your data and we show no ads. Analytics and advertising tools run by other parties work on the site only with your consent, and only on public pages. We count visits to public pages with our own counter, which uses no cookie and which you can switch off.
  • You can ask us for a copy of your data, to correct or delete it, or object to its processing, by writing to us.

Account data

  • When you create an account we store your email address, your username and, if we ask for it, your phone number; your password is stored hashed, in a form that cannot be read back.
  • We ask for a phone number so we can contact you about your account, your balance or your payments.
  • If you sign in with Google or GitHub, we receive your name, your email address and the account id that links the two accounts.
  • We send verification codes and account messages to your email through an email-delivery provider.
  • Account data is needed to create the account; without it we cannot provide the service.

Usage and payments

  • For each request through the API or the apps we record the time, the key used, the model, the token counts, the cost, the IP address, and information about the browser or app that sent the request.
  • If a request fails, we keep an error record with the time, the request id, the start of the key, the model, the IP address, the browser or app information, and the error text that came back, which may include part of what was sent.
  • We keep your balance, subscription and payment-order records: the payment method, the amount and the order's status.
  • For transfers through mobile wallets or InstaPay we keep the receipt you upload and the details of the account you paid from (wallet number or account name), and our team reviews them through an internal messaging tool used for payment review.
  • Card payments are processed by the payment provider, which sends us the payment's status, not your full card number.
  • If you ask for manual access to your subscription key, we keep the reason you gave and a record of every time the key is revealed or copied.
  • In the referral program we keep who invited you or whom you invited, the payments that count toward earnings, the earnings themselves, and your withdrawal requests with the wallet or bank-account details we pay to and the holder's name. An invitee's email address is shown to the person who invited them only partly hidden.
  • If you write to us by email or WhatsApp, we keep the conversation to follow up on your request.
  • We derive only your country from your IP address, on our own server and from a local database, to show the right site language and price currency on your first visit. We do not store your IP address for this or send it to anyone, and you can change the language and currency at any time. Country data: IP Geolocation by DB-IP.

The content of your requests and chats

What you send to a model, whether text, files or images, passes through our servers to the company that develops it, or to a partner that runs access to it, so that you get the answer. Those companies process it under their own terms and may keep some of it for a limited time to monitor misuse.

  • Your chats on the Chat page are kept in your account so you can return to them, until you delete them.
  • Chat memory is on by default: it remembers what you share to personalize answers. You can turn it off and clear what it remembered in the chat settings.
  • Files you upload and images created for you in Chat are kept in cloud storage linked to your account.
  • If you add a connector in Chat, we send the server you chose what it needs to carry out your request, and it processes that under its own terms.
  • If you use web search in Chat, we send your search words to a search provider.
  • Diagram previews in Chat load a script from a public content delivery network, which receives your IP address.

We do not use your requests or chats to train models.

The support chat

The support chat is a chat inside the site and the dashboard. Its conversations and attachments are kept on a support server we run ourselves, not by an outside support-software company.

  • An AI assistant answers you first, running on AI models through our servers. To write the answer, the text of your messages in the chat and the images you send in it, with their metadata such as where a photo was taken removed, reach the companies that develop those models, or our partners that run access to them, most of them outside Egypt.
  • Before the assistant reads your message, we remove the sensitive data we recognize in it: passwords, API keys, verification codes, card and account numbers, email addresses and phone numbers. The chat on the site does not send a message that seems to contain a password, a key or card details; it asks you to remove them instead.
  • If you are signed in, the assistant and the support team see a summary of your account so they can answer about your situation: your plan, when it ends and how much of its limits you have used, your balance, your key names and their status (never the key itself), your latest payment orders and their status, and your latest failed requests. We read this summary from your account when it is needed, never store it in the conversation, and keep it only for a short time.
  • If you write to us without signing in, we do not ask for your name or email address, and the conversation stays tied to this browser.
  • You can ask for a person at any time by choosing "Talk to a person". The conversation then passes to the support team, and the assistant stops answering you in it and stops reading what you write after that. The assistant returns to that conversation only if a team member hands it back to the assistant, or if the conversation was closed and you write in it again later; it may then read what was written in the conversation since you asked for a person, so it can answer you. A team member may also ask the assistant to help draft a reply or summarize the conversation, and they review what it suggests before anything is sent to you.
  • Support team members see the whole conversation. They are alerted through an internal messaging tool that a conversation is waiting, with only its number and the kind of request, never the text of your message or your name.
  • If you are signed in and our team replies while you are away from the chat, we may email your account address that you have a new reply, without the reply's text, at most once every 30 minutes for the same conversation. We keep your address for this purpose encrypted.
  • Before you start a conversation without signing in, we may ask for an automatic check that you are not a bot, run by a provider of that service, which receives your IP address and browser information.
  • We review samples of support conversations and your ratings of the answers, with personal data removed, to improve our answers and docs, and we may use AI models through our servers to do so. We do not use support conversations to train models.
  • If you answer "Was this page helpful?" in the docs, we keep your answer and your note, if you write one, without linking them to your account.

You can ask for a copy of your support conversations or for their deletion, as described under Your rights below.

Why we use data, and on what legal basis

Each purpose rests on one of the grounds Egypt's Personal Data Protection Law No. 151 of 2020 allows, which match the legal bases of the EU General Data Protection Regulation:

Purposes and legal bases
PurposeDataBasis
Providing the service: the account, sign-in, carrying out requests, plans and balanceAccount, usage and request contentPerforming our contract
Accounting and billingUsage and paymentsPerforming our contract; legal obligation
Service messages: verification codes, password and alertsEmail addressPerforming our contract
Contacting you about your account, balance or paymentsEmail address and phone numberPerforming our contract; the purpose you gave the number for
Preventing fraud and abuse, protecting accounts, reviewing payment receiptsIP address, browser information, usage, payments and receiptsOur legitimate interest in protecting the service and its customers
Support and answering your messagesWhat you send usPerforming our contract
Answering you in the support chat through the AI assistant, and handing you to the support teamYour messages and images in the chat, and your account summary if you are signed inPerforming our contract; our legitimate interest in answering you quickly
Reviewing support quality and improving answers and docsSamples of support conversations with personal data removed, and your ratings of the answersOur legitimate interest in improving the service
The referral programThe link between accounts, payments, earnings, withdrawal requests and transfer detailsPerforming our contract under the program rules
Improving the site through the error and speed beaconTechnical data with no id for youOur legitimate interest; you can switch it off
5abeer's own visit counter, to learn how many people visit and how many reach sign-up and paymentThe page opened, the source of your first page that day (campaign name, ad type or the site you came from), and a daily code computed from your IP address and browser without storing themOur legitimate interest; you can switch it off
Answering competent authoritiesWhat the law requiresLegal obligation
Measuring site visits and how our ads performEvents on public pages, the ad platforms' browser ids, the ad click id, and at sign-up or payment your email address and phone number as a hash, with the order's value and currencyYour consent in Privacy choices, which you can withdraw at any time
Marketing messagesEmail address or phone numberYour prior consent only

We make no fully automated decisions about you that have legal effects, and we do not use your data for a new purpose that needs your consent before asking for it.

Who receives it

We do not sell your data and we show no ads. We share only what is needed, with:

  • The companies that develop the models and our partners that run access to them: the content of your requests, so you get the answer.
  • The same companies in the support chat: the text of your messages and your images with sensitive data removed, and your account summary if you are signed in, so the assistant can write the answer.
  • The payment providers you choose: the payment's details.
  • The bank or wallet provider that carries a referral payout, including a bank in the United States for international transfers: the transfer details and the account holder's name.
  • Technical infrastructure providers: hosting, domain and network, cloud storage and backups.
  • Our email-delivery provider, our support tools (a mailbox and WhatsApp), and the internal messaging tool that alerts our team to payments to review and support conversations waiting for a reply (the conversation number and the kind of request only).
  • The provider of the automatic check that a sender is not a bot, when we ask for it before a support conversation without sign-in: your IP address and browser information.
  • The web-search provider and the servers you add as connectors, when you use them in Chat.
  • Analytics and advertising platforms (Google, Meta, TikTok, Snap and X), only if you allow them: events on public pages, the ad click id, and at sign-up or payment your email address and phone number as a hash, with the order's value and currency. We never send them your name, the content of your requests or anything from the dashboard.
  • A model's developer investigating a breach of its usage policies: only what the investigation needs.
  • Competent authorities, when the law or a court order requires it.
  • Whoever succeeds us in running the service after a merger or sale, provided they keep to this policy.

Transfers outside Egypt

Our servers and backups are outside Egypt, as are most of our providers, including the model developers, our partners, and our email and storage providers. Your data is therefore transferred and processed outside Egypt, in the United States, Europe and other countries whose data protection may be lower than in your country. This includes what the support chat's AI assistant reads.

We transfer data because it is needed to provide the service you asked for, and with the consent you give when you create your account, and we rely on the data-protection terms our providers commit to, where they offer them.

If you are in the European Union or the United Kingdom: there is no adequacy decision for Egypt, and what you type into our service reaches us directly from you. For our onward transfers to providers we rely on standard contractual clauses where the provider offers them.

What we store in your browser (cookies)

In your browser we use what is needed to run the site and your account, and the preferences you choose. Analytics and advertising tools run by other parties work only after you allow them in the privacy notice, and only on public pages, never in the dashboard or on the sign-in and payment pages. Our own visit counter (see Measurement) stores in your browser only that you switched it off, if you did, and that an account was created in this tab; it reads only those and your choice in the privacy notice, so it can respect a refusal. Saying no is as easy as saying yes, and you can change your choice at any time from Privacy choices at the foot of the page.

Needed to run the site and your account:

access_tokenlocal storage
Your signed-in session.How long: Until you sign out
refresh_tokenlocal storage
Renews your session without typing your password again.How long: Until you sign out
auth-storagelocal storage
A copy of your profile (name and email address) to show on the pages after sign-in.How long: Until you sign out
khabeer_oauth_startedlocal storage
That you started signing in with Google or GitHub, to finish when you come back.How long: Until the sign-in step ends
khabeer_oauth_providercookie
The account you are signing in with, during that step only.How long: 15 minutes
khabeer_mcp_oauth_bindingcookie
Ties the step of connecting a Chat connector to this browser.How long: 10 minutes
khabeer_e_auth_bouncetab storage
Stops a repeated redirect to the dashboard when you are signed in.How long: Until you close the tab
khabeer_desktop_authtab storage
A sign-in request from the 5abeer AI app, to finish after you sign in on the website.How long: 10 minutes or until you close the tab
khabeer-draft:*tab storage
The text of a Chat message you have not sent yet.How long: Until you close the tab
khabeer-skills:*tab storage
The skills you picked for the message you are writing.How long: Until you close the tab
khabeer-connectors:*tab storage
The connectors you picked for the message you are writing.How long: Until you close the tab
khabeer-generation:*local storage
A Chat reply still being written, so it can finish if you reload the page.How long: Until the reply is complete
khabeer-image-operation:*local storage
An image still being made in Chat, for the same reason.How long: Until the image is complete
e-gl-lossestab storage
How often the browser dropped the page graphics, to show a still image instead.How long: Until you close the tab
khabeer_chat_launch_retrytab storage
One automatic retry when opening Chat fails.How long: Until you close the tab
khabeer_rum_offlocal storage
That you switched off the error and speed beacon in this browser.How long: Until you switch it back on
khabeer_count_offlocal storage
That you switched off the visit counter in this browser.How long: Until you switch it back on
khabeer_count_new_accounttab storage
That an account was created in this tab, so the counter can count the payment step.How long: Until you close the tab
khabeer_consentcookie
Your privacy choice: whether you allowed measurement or advertising.How long: 6 months in Europe and the UK, 12 months elsewhere
khabeer_supportlocal storage
Your support chat session on this device, so you can come back to your conversation. It is created after the first message you send and does not hold your messages. If you sign in after writing to us as a visitor, the visitor conversation stays readable on this device for a week.How long: Until you sign out, and 30 days at most
khabeer_support_pilotcookie
A pass to try the support chat before its launch, for our team and the people we invite only, set when the trial link is opened. It does not identify you.How long: 30 days

Your preferences:

NEXT_LOCALEcookie
The site language you chose.How long: One year
KHABEER_THEMEcookie
Light or dark appearance, so the right one shows from the first moment.How long: One year
KHABEER_THEME_CHOICEcookie
That you picked the appearance yourself.How long: One year
themelocal storage
A copy of the appearance choice inside the browser.How long: Until you clear browser data
KHABEER_NUMERALScookie
The digit style you chose, so the right one shows from the first moment.How long: One year
khabeer-numeralslocal storage
The digit style you chose.How long: Until you clear browser data
KHABEER_CURRENCYcookie
The currency you chose to see prices in, so the right one shows from the first moment.How long: One year
khabeer_display_currencylocal storage
The currency you chose to see prices in.How long: Until you clear browser data
khabeer.home.pathlocal storage
Your choice on the dashboard home: subscriptions or the API.How long: Until you clear browser data
khabeer_docs_*local storage
The example language, operating system and setup style you chose in the docs.How long: Until you clear browser data
khabeer_models_viewlocal storage
How the models list is shown: table or cards.How long: Until you clear browser data
khabeer_chat_looklocal storage
The Chat interface you last opened on this device.How long: Until you clear browser data
e-loop-motionlocal storage
That you paused the moving rows.How long: Until you clear browser data
khabeer-dashboard-bglocal storage
The dashboard background you chose.How long: Until you clear browser data
khabeer-sidebar-collapsedlocal storage
Whether the dashboard sidebar is collapsed.How long: Until you clear browser data
zernio_onboardedlocal storage
That the dashboard welcome window has been shown to you.How long: Until you clear browser data
5abeer-v5-themelocal storage
The appearance choice on the previous version of the home page, if you open it.How long: Until you clear browser data

Invite code and visit source:

khabeer_referral_codelocal storage
The invite code when you arrive through a friend's link, so your sign-up is credited to them.How long: 30 days
khabeer_first_touchtab storage
Where your first visit came from, in this tab only.How long: Until you create an account or close the tab

Only with your consent, for measurement and advertising (set by the tools you allowed, on public pages):

khabeer_ad_attrcookie
The click id of one of our ads if you arrived through it, so your sign-up or order is credited to that ad.How long: 90 days
_fbpcookie
This browser's id at Meta, to measure our ads.How long: 90 days
_fbccookie
Your latest click on one of our ads on Meta.How long: 90 days
_ttpcookie
This browser's id at TikTok.How long: 13 months
_tt_enable_cookiecookie
That TikTok cookies are allowed in this browser.How long: 13 months
ttcsid*cookie
The current visit at TikTok.How long: Up to 13 months
_scid*cookie
This browser's id at Snap.How long: 13 months
_sctrcookie
The date of your last visit, at Snap.How long: One year
_ga*cookie
This browser's id and visit at Google Analytics.How long: Two years
_gcl_*cookie
Your click on one of our ads on Google Ads.How long: 90 days
_twclidcookie
Your click on one of our ads on X.How long: Two years

You can clear this data in your browser settings at any time; you will then need to sign in again.

Measurement, and the error and speed beacon

Pages count general events, such as opening a page, clicking a button or downloading the app, after removing any personal value from them. Unless you allow measurement or advertising in Privacy choices, these events are not sent to any analytics service; if you do, some of them, such as opening a public page, viewing a model or downloading the app, reach only the tools you allowed.

We also run our own visit counter, on 5abeer's own server only, to learn how many people visit the site, where they come from and how many reach sign-up and payment. It uses no cookie, shares nothing with any other party, and is off if your browser sends Do Not Track or Global Privacy Control, if you switch it off with the switch below this paragraph, or if you refuse measurement in the privacy notice when it appears. With each page the browser sends only its path; with the first page it also sends the campaign keys from the address (such as utm_source), whether a click id is present (not its value), and the site you came from, from which we keep only a short source label (such as Facebook, search or the campaign name), never the full address or a click id value. To count a visitor once a day we compute a code from your IP address, browser and the site name with a random key made for that day; your IP address and browser details are used in memory to compute the code and stop floods, and are not stored. The day's key is deleted after 2 days: until then someone holding our database who knows your IP address and browser could recompute that day's code, and after that nobody can. Because the code changes every day, it does not link your visits across days. With today's visit we keep the time of its first and last page, to show how many people are on the site now, and once the day ends both times are set to the start of that day. We keep these counts for 400 days, and our reports page shows totals only. The counter does not run in the chat or the dashboard, except that on the plan and wallet pages it only notes that today's visit reached the payment step if the account was created in this tab after the sign-up page. It never counts the sign-up page for someone who is signed in.

You can switch the visit counter off in this browser here:

Your choice applies at once, to this browser only, and is saved in it.

The error and speed beacon sends a small report about the page's performance to 5abeer's own server only. It uses no cookie, carries no id for your account or your visit, never contains the part of the page address after the question mark, and we do not store your IP address (it is used in memory for one minute to stop floods). A report contains:

  • The page path, language and appearance.
  • The browser engine, the operating system and its major version, whether the device is a phone, the screen size and density, and the connection class.
  • Speed measurements, and whether the page fell back to a still image for its graphics.
  • The error type and a short message scrubbed of personal data.

These reports are kept in the server log. You can switch the beacon off in this browser here:

Your choice applies at once, to this browser only, and is saved in it.

Visit source and invite code

If you arrive through an ad or a link, we keep in the tab only the campaign tags, the site you came from and the first page you opened, and send them with your sign-up once the server supports it, to learn which channels help our visitors.

An invite code is kept for 30 days and sent when you create your account, so the person who invited you gets their reward.

If you allow advertising, we keep the click id an ad adds to the link in the khabeer_ad_attr cookie for 90 days; it reaches our server with your sign-up and your orders, so we know which ad brought you. Before you allow it, nothing of it is stored.

Marketing messages

We send you marketing messages only with your prior consent, and every such message lets you unsubscribe easily. Service messages, such as verification codes, order confirmations and limit and balance alerts, are not marketing.

Security

  • The site, the app and the API connect to our servers over an encrypted connection.
  • Passwords are stored hashed, in a form that cannot be read back, and backups are encrypted.
  • Access to data is limited to the team members who need it for their work.
  • The support server keeps its access log with part of each IP address hidden.
  • If a breach affects your data, we notify the Personal Data Protection Center and tell you within the periods the law sets.

How long we keep data

We keep each kind of data for as long as the purpose it was collected for requires:

How long each kind of data is kept
DataHow long
Account dataWhile the account exists, then as long as closing the account, accounting and legal obligations require
Usage records, including IP addressesWith your account's records, as the basis of billing, support and abuse detection
Error recordsA limited time, long enough to diagnose problems
Payment records and receiptsAs long as accounting and tax law require
Chats, memory and filesWhile they are in your account, until you delete them
Support conversations and their attachmentsAs long as needed to follow up on your request and review support quality, then deleted periodically
The account summary in the support chatA short time; never stored in the conversation
The support assistant's records, with sensitive data removedA limited time, long enough to diagnose problems and measure answer quality
Error and speed beacon reportsIn the server log, with no id for you
BackupsEncrypted copies replaced in turn, so deleted data remains in older copies until they are replaced
What we store in your browserThe period given for each name in the cookies section

Your rights

Egypt's Personal Data Protection Law No. 151 of 2020 gives you the right to:

  • Know what data we hold about you and get a copy of it.
  • Withdraw your consent where processing relies on it.
  • Correct, update or delete your data.
  • Restrict the processing of your data to a defined scope.
  • Be told about any breach that affects your data.
  • Object to the processing of your data where it conflicts with your fundamental rights.

If you are in the European Union or the United Kingdom, you also have the right to data portability, and the rights the law of your country gives you.

To use your rights, or to delete your account, write to support@5abeer.ai with "Data protection" in the subject line. We may ask for proof that the account is yours, and we answer within the period the law sets. We do not delete what the law requires us to keep.

You also have the right to complain to Egypt's Personal Data Protection Center, or to the data protection authority in your country.

Children

The service is only for people aged 18 or over. If we learn that a minor has created an account, we close it and delete its data, except what the law requires us to keep.

For visitors from the United States

We do not sell personal information. We share it for cross-context behavioral advertising only with your consent in Privacy choices, and we treat a Global Privacy Control signal as an opt-out of that sharing. We do not knowingly collect data from children under 13.

Changes to this policy

If we change what we collect or how we use it, we update this page, its version number and its date, and we tell you about important changes by email or in the dashboard before they apply. If a new purpose needs your consent, we ask for it before we start.

A question about this page? Contact us