What Madar OS touches, and what it never does.
Last updated 28 September 2026
Who operates this
Madar OS is built and operated by Ahmed Yahya Al Kindi Enterprise, a sole proprietor establishment registered in Muscat, Oman (commercial registration 1399884), trading as TSB Labs. Questions or requests about your data go to privacy@madar-os.com. Our data protection officer is Ahmed Al Kindi, at the same address. To report a security problem, write to security@madar-os.com.
This website
The site sets no advertising or tracking cookies and runs no third party analytics. The walkthrough and the demo workspace run a fictional company; every company, person and number in them is invented. If you use Design your Madar, the answers you give (your name, email, company and what you need) are stored on Supabase, in Frankfurt, Germany, so we can reply to you, and for nothing else. The first reply is written by Madar, our AI assistant, and says so; Ahmed sees every one.
Payments
Our order process is conducted by our online reseller Paddle.com, the Merchant of Record for all our orders. Paddle collects your card or payment details directly; we never see or store them. Paddle tells us your name, email, country, the plan you chose and the status of your subscription and payments, which we keep in our own records, on Supabase in Frankfurt, Germany, to run your account, invoice correctly and answer you. Questions about a payment or a refund go to billing@madar-os.com. Paddle's own handling is described in its privacy notice.
Emails from us
If you have an account, we email you about it, your trial and your payments; those are part of the service. Product news, offers, or a reminder when you started a checkout and did not finish are sent to customers and site visitors only if you agreed to receive them, for example by ticking the box in the checkout, and each has a one click unsubscribe. We keep a record of what was sent and whether it was opened or clicked, so you are never contacted twice by mistake.
If we wrote to you first
We sometimes write to a business we think Madar could help, at a business email address that was published on a company website or in a business directory. We record where and when we found each address, write at most twice, and never write to personal free mail addresses. We do not write this way to people in Saudi Arabia, or to named individuals in Oman or Qatar, unless they agreed first. If you reply "stop" or use the link in the email, we stop within 24 hours and keep your address only on a do not contact list, so it is never used again. You can ask where we found your address, or have it deleted, at privacy@madar-os.com; we answer within 30 days. Our data protection officer is Ahmed Al Kindi, at the same address.
The application, and Google account data
Separately from this website, Madar OS is an application the operator runs to manage their own business. It connects to a Google account only when the account holder explicitly authorises it through Google's own consent screen. Customer workspaces do not connect to a Google account today. The operator's own install requests these permissions:
gmail.modifyso it can read messages, apply labels, and prepare draft repliesgmail.settings.basicso it can read basic mailbox settingscalendar.readonlyandcalendar.eventsso it can see free time, and book or cancel a meeting once a person approves itspreadsheetsso it can read and update Google Sheets in that account, anddrive.fileso it can open files it created or was given
It never sends email on your behalf without you. Replies are written as Gmail drafts and left for a human to read, edit and send. Drafting is reversible. Sending is not.
Where the data goes
Each customer's workspace runs in its own isolated space, with its own database, on servers we operate, not on a shared platform. Today every workspace is in Frankfurt, Germany. A choice of a Gulf region is coming; until it opens, nothing is hosted in the Gulf. These are the companies that handle data for us, and what each one does:
- Oracle Cloud, in Frankfurt, Germany: the servers your workspace runs on, and the storage that keeps its backups.
- Anthropic, in the United States: writes Madar's answers. What you ask, and the parts of your business Madar needs in order to answer, are sent to Anthropic's Claude models for each reply.
- Paddle, our Merchant of Record: takes your payment and handles tax, receipts and refunds.
- Resend, which sends through Amazon SES in Tokyo, Japan: delivers the product's own mail, such as your welcome link, password resets and reminders.
- Zoho: our company mailboxes, so a message you send to one of our addresses is kept there.
- Supabase, in Frankfurt, Germany: our own records, including the answers you give on Design your Madar and the account details Paddle sends us.
For the operator's own Gmail connection, message content is read and processed on the operator's server to prepare a draft, and access tokens are stored in a restricted file on that server. We run no service that receives mail on anyone else's behalf, we keep no shared database of message content, and we do not sell, rent or trade any data to anyone, for any purpose, ever.
Language models are used to write answers and drafts. Only the material needed for an answer is sent to the model provider, and under Anthropic's commercial terms it is not used to train their models. Answers are written by AI and can be wrong, so check anything that matters before you rely on it; nothing leaves your workspace without your approval.
Backups
Every night, each workspace (its database, its files and its memory) is packed into one archive and encrypted with a key that is held on no server, so neither server can read a backup. The archive is kept for seven days on our servers, and a copy is stored in Oracle Cloud Object Storage in Frankfurt, apart from the server that runs your workspace, where it is kept until your workspace is deleted. Our own records are copied to the same storage every night, and that copy is checked by reading it back.
Limited use
Madar OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention, and how to end it
Message content is not retained after a draft is prepared. What is kept is an operational record: which addresses were written to and when, so the same person is never contacted twice by mistake.
You can revoke access at any moment at myaccount.google.com/permissions. Revoking takes effect immediately and the application loses all access. To have the operational record deleted as well, email privacy@madar-os.com and it will be removed within 30 days.
Your workspace is kept for as long as your subscription runs. When you leave, or at any time before, you can ask for an export of it or for its deletion.
Your rights
You can ask for a copy of the personal data we hold about you, have it corrected, have your workspace exported, have it deleted, or withdraw consent to marketing at any time. There is no export or delete button in the app yet, so our team does both by hand: email privacy@madar-os.com and it is done within 30 days. Backups of a deleted workspace are removed as they reach the end of the periods above. If something ever goes wrong with your data, we will tell you, and the authority where the law requires it, within 72 hours of learning of it.
Children
This is a business tool. It is not directed at, or intended for, anyone under 18.
Changes
If this policy changes materially, the date at the top changes with it, and anyone who has authorised the application is told by email before the change takes effect.