Last updated: November 11, 2026 · Contact: mobtakirapp@gmail.com
This Privacy Policy explains how Mobtakir (“we,” “us,” “our”) collects, uses, shares, and protects information when you use the Mobtakir iOS app, the website mobtakirr.com, and related online services (the “Service”). Read it together with our Terms of Use. If you do not agree with this policy, please do not use the Service.
1. Who we are
Mobtakir is a service based in the State of Qatar and is responsible for your personal data under this policy. For privacy requests, email mobtakirapp@gmail.com.
2. Scope
This policy applies to:
- The Mobtakir iPhone and iPad app;
- The website mobtakirr.com, including the verification form and website checkout;
- Our backend services, including Supabase-hosted APIs, Edge Functions (such as the AI function), the database, and storage;
- Features that connect to third parties: Apple, Google, Polar, RevenueCat, Expo, OpenRouter and other AI model providers, and services you connect yourself, such as a Supabase project or GitHub.
It does not govern apps you build with Mobtakir and publish to your own users (you are responsible for their privacy policies), or third-party websites and services beyond what Mobtakir provides.
3. Information we collect
3.1 Information you provide
- Account: email and password, or Sign in with Apple or Google identifiers. Used for authentication, account recovery, and security.
- Profile: display name, avatar, or profile fields you choose. Used for community, sync, support, and personalization.
- Project content: app ideas, chat messages, plans, briefs, answers to questions, attached images, and selected skills. Used for AI planning, building, editing, and project storage.
- Generated output: source code, configuration files, previews, and version history. Used to deliver the Service, sync, and restore versions.
- Connectors and project keys: a Supabase project URL, publishable keys, or other connector settings you enter, and service keys you add under “Project keys.” Used to apply integrations to your generated app.
- Community and support: messages you post in community features or send to support.
- Store metadata: app names, descriptions, and listing fields you enter for publishing guides.
- Verification requests on the website: your name, the email of your Mobtakir account, and an optional note. Used to review the request and link it to your account.
Do not submit service role keys, passwords, or secrets that must never appear in client apps. You are responsible for what you paste into the Service.
3.2 Purchases and payments
- In the App: purchases go through Apple’s App Store. We receive purchase and entitlement status through RevenueCat. We do not receive your card details.
- On the website: orders are processed by Polar, our Merchant of Record. Polar collects your payment details, name, email, and billing country or address directly, under Polar’s Privacy Policy. We receive from Polar the information needed to provide your plan: your email, a customer and subscription reference, the plan, country, transaction amounts, and status. We never receive or store your full card number.
3.3 Information collected automatically
- Device and app: device model, OS version, app version, language, and feature flags, for compatibility, security, and gradual rollout.
- Identifiers: internal profile and device identifiers and the Apple Push Notification token, for sync, notifications, and account linking.
- Usage and diagnostics: server-side event logs (feature usage, errors) and AI credit ledger entries, for operating credits, debugging, and preventing abuse.
- Preview error reports: when your app crashes in Expo Go, the error text (up to 400 characters), file name and line number, and platform, so the AI can fix the error in your next request.
- App check: a screenshot of the first screen of your app, taken when an app check runs, to verify that the app runs.
- Website visits: we count visits without cookies. For each page view we store the page path, language, country (from our hosting provider), device type, the referring site’s domain, and a campaign tag if present, together with a non-reversible hash that changes every day. We do not store your IP address. If your browser sends “Do Not Track” or Global Privacy Control, the website does not send these visit records. Your language choice is saved in your browser’s local storage.
We do not sell your personal information.
3.4 Information stored primarily on your device
Your projects (chat, files, previews, Expo links, and versions) are stored on your device first. Some or all of this may be uploaded to our cloud when sync conditions are met. If sync fails, local data stays on your device.
3.5 Preview and Expo Snack
When you preview a project, the code bundle is sent to Expo Snack and stored on Expo’s servers so it can run in Expo Go. The bundle does not contain your private keys or the data of your app’s users.
3.6 AI processing
When you use AI features, we send the relevant parts of your input to our servers and then to third-party AI providers, including OpenRouter and model providers reached through routing gateways, to produce plans, code, and edits. This may include prompts and chat history for the current project, existing project files when you request edits or fixes, and metadata needed for credit reservation. We instruct providers to process data only to provide the Service. Do not include sensitive personal data (health information, financial account numbers, government IDs, or other people’s private data) in prompts.
3.7 Images you attach to your app
Images you attach in chat to become part of your app (such as a logo or product photos) are stored in a public storage bucket operated by Mobtakir so they appear in the preview and the published app. Anyone with the link can see an image. Do not attach private images. These images are deleted when you delete your account.
3.8 A Supabase project connected to your app
If you connect your own Supabase project, Mobtakir may create the items your app plan requires, with your approval, using the access token you give Mobtakir. Your app users’ data stays in your project; Mobtakir does not copy or retain it. Keys you add under “Project keys” are sent once to your project; Mobtakir does not store or display them.
3.9 App check
Mobtakir may check your project code on a separate check server that opens each screen and captures a screenshot of the first screen. The check runs on a temporary copy of your code without internet access or real data. The copy and the screenshot are deleted right after the check; the screenshot is sent only to the AI model building your app during that same step.
3.10 Publishing to the App Store
When you use “Submit to App Store” to publish your app from your own Apple Developer account:
- Apple ID password: sent once over an encrypted connection (TLS) to sign in to Apple. We never store it or write it to any log.
- Apple session: the session that results from signing in is stored encrypted and used only for the publishing steps you request for your own apps.
- App Store Connect key: we create an App Store Connect API key in your Apple team, store it encrypted, and use it only to upload your builds and check their status. You can revoke it at any time in App Store Connect under Users and Access → Integrations.
- Distribution certificate: we create an Apple distribution certificate and its private key in your team, store them encrypted, and delete our copy when you sign out of Apple.
- Building and uploading: your app’s files, together with the distribution certificate, the provisioning profile, and the App Store Connect key, are sent to our build runner on GitHub Actions and then to Expo’s build servers (EAS), which build the iOS binary and upload it to App Store Connect. They are used only to build and upload that app.
- Deleting this data: sign out of Apple in the publish window, or delete your account.
3.11 Cookies on the website
We do not use advertising cookies or third-party tracking cookies. The website uses essential cookies only, all set by our own domain and not readable by JavaScript:
- Session (sb-…): keeps you signed in.
- Language and appearance (mbk_lang, mbk_theme): remember your choice for a year.
- Device (mbk_device): a random id for this browser, used to sync your projects across your devices and prevent conflicting edits.
- Free TSHEESA device (mbk_dev): a random id that stops the free allowance from being claimed again on the same browser (Section 3.12).
- Cookies for specific operations (mbk_ai, mbk_after_sign_in, mbk_google_flow, mbk_profile_skip): your model choice, returning you to your page after sign-in, protecting Sign in with Google, and postponing the profile card.
You can delete them in your browser’s settings, but signing in and remembering your choices will not work without them.
3.12 TSHEESA
- Conversations: TSHEESA conversations are saved in your account so you can return to them. Your messages and the files you attach are sent to AI providers to produce the reply, as in Section 3.6.
- Free tier: it may answer through free models from third-party providers via OpenRouter. We ask for your consent before first use: if you agree, those providers may keep and use your free conversations to improve their models; if you do not, we ask them not to collect them. Do not put sensitive information in free conversations. This consent does not affect TSHEESA Pro conversations or app building.
- Preventing repeat free allowances: in the iPhone app we store a random id in the device’s keychain and may use Apple’s DeviceCheck; on the website we use the mbk_dev cookie. For new free accounts we keep a one-way hash of the IP address, never the address itself. We use these only to prevent multiple accounts claiming the free allowance.
- Images: image drawing is available in the iPhone app only; the image description is sent to an AI provider to produce it.
3.13 Composio
If you link your own Composio key, we store it encrypted on our servers only; it never reaches your device or our logs. We use it to send read requests to Composio when you ask, and write requests only after you confirm. You can delete it at any time in Connectors.
4. How we use information
- Provide the Service: authentication, projects, AI building and editing, previews, connectors, community, and settings.
- Subscriptions and AI credits: verify purchases from Apple or Polar, apply plans, and reserve, settle, and absorb credits on the server.
- Sync and backup of project data when sync is enabled.
- Communication: push notifications (if you allow them), support replies, and service or billing notices.
- Security and abuse prevention: suspensions, rate limits, and fraud prevention.
- Improvement: aggregated or de-identified statistics, including website visit counts, debugging, and feature flags.
- Legal compliance: responding to lawful requests, accounting and tax records, and enforcing our Terms.
Legal bases (EEA and UK users): performance of a contract, legitimate interests (security, improvement, and privacy-friendly statistics), consent where required (for example, optional notifications), and legal obligation.
5. How we share information
We share information only as needed:
- Supabase: account, profile, projects, logs, and storage, for hosting, authentication, the database, and server functions.
- Cloudflare and Fly.io: the website passes through Cloudflare (protection and caching) and its server runs on Fly.io; both process your IP address to deliver pages and protect the site.
- Composio: the read and write requests you ask for in your linked apps, using your own key.
- Polar: website orders, payments, taxes, invoices, cancellations, and refunds, as Merchant of Record.
- Apple: Sign in with Apple and App Store purchases; when you ask Apple to refund an App Store subscription, we automatically send the share of that period’s AI credits you used and that the service was delivered (Terms, Section 5.4); when you use “Submit to App Store”, signing in to your Apple Developer account and creating the certificate, key, and app record in App Store Connect.
- Google: Sign in with Google.
- RevenueCat: app user ID and purchase and entitlement data, for subscription management.
- OpenRouter and AI model providers: prompts and file excerpts needed to generate and edit your project.
- Expo / Snack: the project bundle for previews in Expo Go; when you publish, the app’s files, signing credentials, and App Store Connect key, to build the iOS binary on EAS and upload it.
- Build runner (GitHub Actions): the app’s files, signing credentials, and App Store Connect key, only while the app is built and uploaded.
- App check server: a temporary copy of your code and the first-screen screenshot.
- Other service providers under contract, for hosting, email, and support tools when used.
We may disclose information if required by law, to protect rights and safety, or in connection with a merger or sale of assets (with notice where required). We do not share your generated app’s source code publicly except as you direct.
6. International transfers
Our processors may store or process data in the United States and other countries. Where required, we rely on appropriate safeguards, such as Standard Contractual Clauses, for transfers from the EEA and UK.
7. Retention
- Account: while your account is active; deleted or anonymized within a reasonable period after a deletion request, subject to legal holds.
- Projects and chat: while your account exists and you keep the project. Local copies stay on your device until you delete them.
- Preview error reports: 14 days, and deleted immediately when the project or account is deleted.
- App check screenshots and temporary copies: deleted right after the check.
- Images attached to projects: deleted when you delete your account.
- AI credit ledger, purchase and transaction records: as long as needed for billing, disputes, fraud prevention, accounting, and tax law.
- Verification requests: as long as needed to review the request and manage your verified status.
- TSHEESA conversations: until you delete them or your account.
- Free-allowance protection records: one-way hashes kept as long as needed to apply the rule; they contain no IP address.
- Website visit records: kept for site statistics; they contain no IP address and only a hash that cannot be linked across days.
- Support messages and logs: as long as needed to resolve issues, and typically months for security logs, unless law requires longer.
8. Security
We use technical and organizational measures suited to the Service, including encryption in transit (HTTPS/TLS), strict security headers on the website, access controls on backend systems, and keeping privileged secrets on servers only. AI API keys are not stored in your generated app. No system is 100% secure; you are responsible for securing your device, your password, and any third-party keys you enter.
9. Account deletion
You can delete your account from inside the app. Your account data, profile, project images, and cloud projects are then deleted, along with the preview error reports linked to them. We may keep billing and credit records for as long as the law requires.
10. Your choices and rights
- In the app: manage notifications in iOS Settings, sign out, delete projects, and remove connector credentials you no longer need.
- On the website: turn on “Do Not Track” or Global Privacy Control to stop visit records.
- Free TSHEESA: you can change your consent to free-model providers keeping your conversations from “Free TSHEESA options” in TSHEESA’s menu.
- Access, correction, and deletion: depending on where you live, you may have the right to access, correct, delete, restrict, object to, or port your personal data, and to withdraw consent. Email mobtakirapp@gmail.com with the subject “Privacy Request” and enough detail to verify your account. We respond within the time limits required by applicable law, such as 30 days under the GDPR where it applies.
- Complaints: users in the EEA and UK may lodge a complaint with their local data protection authority.
- California: California residents may have the right to know, delete, and correct personal information and to opt out of “sale” or “sharing.” We do not sell or share personal information for cross-context behavioral advertising.
11. Children
The Service is not directed to children under 13 (or a higher age where required by law). We do not knowingly collect personal information from children. If you believe a child has given us data, contact mobtakirapp@gmail.com and we will delete it.
12. The apps you build
Generated apps may link to external services or request device permissions such as camera, location, or notifications. You must disclose these practices in your app’s own privacy policy and in the App Store and Google Play data forms.
13. Changes to this policy
We may update this policy. We will post the new “Last updated” date and, when required, give notice in the app or by email. Continued use after the effective date means you accept the updated policy. This policy is available in English and Arabic; if they differ, the English version prevails.
14. Contact
Privacy and data requests: mobtakirapp@gmail.com. Legal questions: the same address with the subject “Legal.”