Skip to main content
Mojo White
Back to legal hub

Privacy

Privacy Policy

The full privacy notice for account data, uploaded content, generated audio, AI processing, analytics, retention, and privacy rights.

Version
v1.7
Effective
May 22, 2026
Last updated
October 10, 2026

Legal entity: Haro LLC. Product brand: Mojo White. For legal questions, contact help@mojowhite.com.

Who Controls Your Information

Haro LLC operates Mojo White and is the controller for account, product, privacy-rights, billing-administration, and support data unless a separate agreement says otherwise.

Mojo White is not directed to children under 16. If a parent or guardian believes a child under 16 provided personal information, they may contact help@mojowhite.com to request deletion.

When a business customer uses Mojo White under a separate written agreement, Haro LLC may process some information as a processor or service provider for that customer. This public Privacy Policy applies to Mojo White's general consumer and product operations unless a separate agreement says otherwise.

Information We Collect

  • Account information: email address, authentication records, account status, role, preferences, and subscription state.
  • Content: uploaded documents, scans, images, extracted text, transcripts, generated audio, prompts, assistant conversations, podcast jobs, and related metadata.
  • Usage, security, and operational diagnostic data: word counts, plan limits, product interactions, device/browser metadata, security events, crash and hang diagnostics, abuse-prevention signals, and service logs.
  • Billing data: plan, invoice, payment, chargeback, refund, Stripe metadata, and Apple App Store transaction metadata.
  • Local data: offline drafts, cached scans, and app-managed local storage that remains on the device unless synced or uploaded.
  • Service records: while you are signed in, on the iPhone app and the Android app, Mojo White keeps first-party records of how the service worked for your account, such as whether an upload or a purchase succeeded, when audio started playing, and which upgrade offers were shown to you. These records never include your document text, titles, file names, prompts, or generated audio. They exist to run and support the product and are not controlled by the optional analytics cookie setting.
  • App installation identifier: the iPhone app and the Android app each create a random identifier for your installation of the app and keep it on your device. We use it to connect what happened before you signed in (for example, opening the app and the welcome screens) with your account after you sign in. We store it only in a one-way scrambled form, never in its original form. It is not your Apple advertising identifier, it is not the Android advertising identifier, and it is not built from your device's hardware.
  • Apple Search Ads attribution: if you install the iPhone app after tapping an Apple Search Ads advertisement for Mojo White, Apple gives the app a one-time code. We exchange that code with Apple once to learn which Mojo White campaign, ad group, or keyword led to the install, and we delete the code within 48 hours. This never uses your Apple advertising identifier and never involves a tracking prompt. If Apple has no ad to report, we record nothing about an ad.
  • Google Play install referrer: when you install the Android app from Google Play, Play can give the app a short note about how the install came about, for example from the Play store itself, from a paid Google ad, or from a link in one of our campaigns such as an email or a social post. We store the kind of source we conclude from it, and the campaign tags the note carries (source, medium, campaign name, content, and term). We never store the note itself. If the note contains a web address, we do not use it, and the install source is recorded as unknown. We do not store a click identifier, and we do not read the Android advertising identifier. Installs from testing, internal review, a debug copy, or a copy installed outside Play are recorded as unknown, never as an ad.
  • Optional audience question: after you have listened to a couple of your own documents, the app may ask, optionally and at most twice, what brings you to Mojo White (for example school, work, or reading for yourself). Only if we have no record of how you found us, it may also ask how you first heard about Mojo White. You pick from a fixed list; there is no free text. Your answer is stored with your account and used only to understand who uses Mojo White and to improve it. It is never shared with advertisers or any other third party, and you can change or clear it at any time in Settings.
  • Campaign names on our website: if you arrive on our website from a link that carries a campaign name, for example one of our ads, the App Store and Google Play buttons carry that campaign name so Apple and Google can tell us how many downloads each campaign produced, in totals only. We also count, per day and per campaign, how many times our download page and campaign links were viewed and how many App Store and Google Play button taps followed, without any cookie or identifier and without storing your IP address. The campaign name contains nothing about you, and we do not connect it to you.
  • Advertising cookies on our website: on our marketing pages, such as the home page and the download page, we use the Meta Pixel and the Google Ads tag to learn whether an ad led you to tap the App Store or Google Play button. These companies may collect information about your activity on our site and across other websites over time. In the EU, EEA, UK, Switzerland, Quebec and Brazil they run only if you say yes. Elsewhere they run unless you turn them off with Your Privacy Choices at the bottom of every marketing page, or your browser sends Global Privacy Control. We do not respond to Do Not Track signals. They never run on legal pages, in the Mojo White apps or in the web app. You can also opt out of ads based on your activity at aboutads.info/choices. What they receive: Meta receives your IP address, browser information, the address of the page and of the page you came from, its own cookies (_fbp, and _fbc when you arrive from a Meta ad), a page view, and a Lead event naming which store button you tapped. Google receives your IP address, browser information, the full address of each marketing page you visit (including campaign tags and Google's ad click identifier), its own cookies (_gcl_au, and _gcl_aw when you arrive from a Google ad), and a conversion event when you tap a store button. Neither receives your name, email address, account or documents. When you turn Advertising off, the tags stop and their cookies on our site are deleted.

Sources of Information

  • You: account details, uploads, scans, imports, prompts, preferences, support messages, research choices, export requests, and deletion requests.
  • Your device and browser: app version, operating system, browser, language, region signals, session identifiers, consent choices, diagnostics, and security events.
  • Connected services: Google Drive, Dropbox, Apple, Stripe, WorkOS, and similar services may send the account, import, billing, entitlement, or authentication data needed for the feature you choose.
  • Service providers and security tools: hosting, logs, analytics, fraud-prevention, bot-prevention, malware-scanning, and abuse-monitoring providers may produce operational records.

User Content and Sensitive Information

Mojo White content can include documents, scans, images, extracted text, assistant messages, podcast inputs, generated scripts, generated audio, citations, and project metadata. This content may contain personal, sensitive, confidential, copyrighted, educational, financial, health, biometric, or other regulated information depending on what you choose to upload or generate.

Mojo White does not require users to upload sensitive information. If you choose to do so, you are responsible for ensuring that you have the rights, authority, notices, consents, and legal basis required for that processing.

Unless a feature clearly says otherwise, Mojo White is not designed to host regulated medical records, payment card numbers outside Stripe-hosted checkout, government identifiers, student education records, attorney-client files, or other information requiring a specialized compliance agreement.

How We Use Information

  • Provide OCR, parsing, text-to-speech, podcast generation, assistant responses, imports, playback, account access, and subscriptions.
  • Maintain security, prevent abuse, enforce quotas, investigate reliability issues, and comply with legal obligations.
  • Improve reliability and product experience using aggregated or de-identified metrics where appropriate.
  • Send transactional notices, support replies, privacy-rights responses, billing notices, and service updates.
  • Operate cookie choices, privacy settings, marketing opt-outs, do-not-sell/share requests, data exports, and deletion workflows.
  • Measure conversion, retention, feature reliability, crash/error patterns, fraud risk, and abuse trends, subject to the Cookie Policy and processed opt-out requests.
  • Support account export, deletion, research opt-in/out, refunds, disputes, chargebacks, tax, accounting, and legal-response workflows.

How We Share Information

We share information with service providers only as needed to operate, secure, support, improve, and enforce Mojo White, or where you direct us to connect an integration.

We may disclose information to comply with law, respond to valid legal process, protect safety, prevent fraud or abuse, enforce agreements, investigate security incidents, complete a business transaction, or with your consent.

We do not sell customer documents, extracted text, prompts, generated audio, or account content. We do not disclose such content to advertisers for behavioral advertising.

International Transfers

Mojo may use service providers that process data outside your country, including in the United States. Where required, we use appropriate safeguards for international data transfers.

AI Processing and No-Training Commitment

When you use an AI or cloud-powered feature, Mojo White sends only the content needed for that feature to third-party service providers, including AI, speech, OCR, hosting, search, and other infrastructure providers that Mojo White uses from time to time to operate and provide the service. These providers process that content only to operate and deliver Mojo White, not for their own purposes. Examples of the AI and speech services that may receive your content are given on the How Your Data Is Processed page. The specific services may change, and a current provider list is available on request from help@mojowhite.com.

Mojo White does not sell customer content and does not use customer documents, extracted text, prompts, or generated audio to train Mojo White or third-party provider models as part of normal product use.

The no-training promise depends on provider API terms, DPAs, and account settings. Haro LLC relies on provider terms that restrict model training for ordinary API/business use and treats DPA or equivalent provider records as part of the vendor-review file.

Providers may retain limited logs for abuse monitoring, security, reliability, legal compliance, or billing according to their own terms. Mojo White prefers enterprise/API provider settings that prohibit model training by default and documents exceptions through legal or privacy review.

Some AI features use tool calls against your own Mojo White documents or metadata. Those tool calls are limited to the account context needed for the requested assistant response, but you should still review outputs before reliance.

Your Permission for Cloud AI & Voices

Starting with version 1.4.1 of the Mojo White iPhone app, the first time you use a feature that sends your content to a third-party AI, speech, OCR, or other cloud processing provider (for example the Assistant, quizzes and summaries, podcasts, scan and image import, or cloud voices), the app asks for your permission. We record your choice with its date, the version of the notice you saw, and where in the app you made it.

If you choose Not now, those features do not send your content to these providers. Your documents can still be read aloud with a voice available on your device, and features that need cloud processing show that they require it.

You can turn Cloud AI & Voices on or off at any time in Settings. Turning it off records a withdrawal and stops new cloud processing for these features. Content that was already processed follows the Retention section.

Retention

Server-side uploaded files, extracted text, generated audio, transcripts, and similar content are generally deleted after 30 days unless a listed exception applies.

Research Program participation may allow longer retention of anonymized or de-identified research snapshots as described in the Research Program terms.

Billing, security, fraud-prevention, operational diagnostic issue metadata, legal, backup, and tax records may be retained for longer periods where needed for operation, compliance, dispute resolution, and audit.

Raw crash diagnostics, device hashes, and native session denominator rows are kept up to 30 days. Grouped non-content stability issue metadata may be retained up to 365 days so Mojo White can track versions where issues were introduced, fixed, or regressed.

Deleted content is removed from active service systems according to the retention rules, but encrypted backups may retain copies briefly until backup rotation completes.

Retention Details

  • Account records: kept while the account is active and then deleted or anonymized after account deletion, subject to legal, security, tax, and billing exceptions.
  • Documents, scans, extracted text, podcast files, assistant context, and generated audio: generally deleted from active systems after the product retention period or account deletion, unless you save, export, regenerate, participate in research, or a legal/security hold applies.
  • Security, abuse, bot-prevention, access logs, and operational diagnostic issue metadata: kept long enough to protect the service, investigate incidents, enforce terms, track fixed/regressed app versions, and preserve evidence. Raw per-device stability events are kept up to 30 days.
  • Billing and transaction records: limited records may be kept for up to seven years where needed for tax, accounting, chargeback, refund, fraud prevention, audit, App Store restore support, and platform obligations.
  • Service records and app activity: detailed records of individual steps (such as an upload attempt or a playback start) are deleted 18 months after they happen. Records from an app installation that never signed in to an account are deleted after 60 days. Apple Search Ads attribution codes are deleted within 48 hours. All of these are deleted with your account when you delete it.
  • Optional audience answers: kept while your account exists. You can change or clear them in Settings at any time, and they are deleted with your account.
  • Backups: encrypted backup copies rotate out on the backup schedule and are not used for ordinary product access after active deletion.
  • Local/offline data: cached files, drafts, and downloads on your device may remain until you delete them, clear app/browser storage, or uninstall the app.

Your Controls and Rights

  • Access: request a copy of personal information associated with your account.
  • Deletion: delete your account and associated server-side data, subject to legal and security exceptions.
  • Correction: update account details and preferences.
  • Export: use available product controls or contact help@mojowhite.com for a data export.
  • Opt out or restrict: manage marketing preferences, cookie choices, do-not-sell/share requests, and legally available opt-out rights.

Verification, Authorized Agents, and Appeals

For privacy, export, correction, and deletion requests, Mojo White may verify account control, request the account email, require session authentication, or ask for information reasonably necessary to match the request to an account.

Authorized-agent requests may require proof of authorization and direct verification with the account holder unless applicable law provides otherwise.

If a request is denied, limited, or only partially completed because of legal, security, fraud, account-matching, or technical reasons, you may contact help@mojowhite.com to appeal where applicable law provides an appeal right.

Automated Decisions

Mojo White may use automated systems to detect spam, bot activity, malware risk, quota abuse, suspicious authentication, payment fraud, policy violations, or unsafe AI requests.

Mojo White does not intend to use automated processing to make decisions that produce legal or similarly significant effects about employment, credit, housing, education, insurance, public benefits, medical care, or eligibility for essential services.

US State Privacy Rights

Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Florida, and other states may have access, deletion, correction, portability, opt-out, appeal, or sensitive-data rights where applicable thresholds and laws apply.

Mojo White routes state privacy requests through help@mojowhite.com and tracks request receipt, verification, deadline, response, and outcome for operational compliance.

Contact

Privacy requests may be sent to help@mojowhite.com. Haro LLC may ask for information reasonably needed to verify the request and match it to an account.

Related disclosures

Privacy Policy - Mojo White Legal