Privacy policy

Who operates Ademi

Ademi is operated by Sofuto Solutions LLP. Questions and privacy requests can be sent to hello@ademi.ai.

Data we process

• Account identifiers, email address, subscription status, and authentication records.
• Model requests, token usage, cost estimates, and operational logs needed to provide and protect the service.
• Project files, recent project chat history, and prompts that you choose to process through the Ademi web, desktop, or iOS applications.
• When you connect the Desktop Companion, sanitized chat text, project and conversation display names, message status, and verified hosted-site links are temporarily relayed so your phone can display and control the live desktop session. Local paths, credentials, attachments, private reasoning, and raw tool output are excluded.
• Payment identifiers and purchase status. Ademi does not store complete payment card numbers.
• Registrant contact details required to register a domain. Pending contact records are encrypted and removed after successful registration.

How we use data

We use data to authenticate accounts, enforce plan limits, route model requests, fulfill purchases, prevent abuse, provide support, and maintain service reliability.

Service providers and AI sharing

Ademi operates its own email-based account system and uses Whop only for payment processing and subscription records. When you ask Ademi to generate or change code, the prompt, bounded project source files, and recent project chat history are sent through Ademi's servers to OpenRouter and the selected model provider so they can return a result. The iOS app asks for explicit permission before its first AI request for each account, and that permission can be revoked in the app. Vercel hosts the application, Upstash stores account and order state, Namecheap registers domains, SendGrid sends transactional email, and Amazon S3 hosts application downloads. Each provider processes data under its own terms.

Advertising measurement

Advertising measurement applies to Ademi's website product and checkout surfaces. Those website surfaces use the Meta Pixel and Conversions API to understand whether an advertisement led to a product view, checkout, or verified purchase. This may include browser identifiers, click identifiers, IP address, browser information, and a one-way hash of your email address. Browser and server events share an event ID so Meta can deduplicate them. Your website choice is stored for up to 180 days, and you can decline or change it here without losing access to Ademi. The native iOS app does not embed the Meta Pixel or Meta SDK and does not send native workspace activity to Meta.

Retention and security

We retain account, payment, usage, and domain ownership records for legal, fraud prevention, support, and accounting needs. Pending domain contact details are encrypted and deleted from the order record after fulfillment. Desktop Companion relay data is available only to the same signed-in account, expires after a limited period, and is removed when you choose Disconnect. The desktop's local conversation archive remains the source of truth. Desktop access tokens are stored in the operating system credential manager and are never placed in a QR code. On iOS, the first-party session cookie is held by the system networking stack. If changes have not finished saving, iOS may keep a protected, account- and project-scoped recovery draft on that device until the changes are saved or discarded.

Your choices and account deletion

You may request access or correction by emailing us. Signed-in users can initiate account deletion inside the Ademi iOS app by opening About Ademi and choosing Delete account. We review and process verified deletion requests within 30 days, deleting or de-identifying eligible active account and project data. Some records may be retained only for as long as reasonably necessary for payments, fraud prevention, taxes, disputes, security, or legal obligations.

International processing

Our providers may process data in countries outside your residence. We use established providers and appropriate contractual protections where required.

Changes

We may update this policy as the service changes. Material updates will be posted here with a new effective date.