Skip to content

Privacy Policy

Last updated:
In short
  • We collect what we need to run Humanizely: your account, usage counts and, in the mobile app, ad identifiers for ads.
  • Text you check or rewrite is processed to produce your result and is not stored as content on our servers.
  • On the website, we use analytics tools if you accept our cookie banner; you can decline or change your choice at any time.
  • Payments are handled by our payment partners; we never see your full card details.
  • You can clear your history or delete your account at any time, in the app or on our website.

1. Who we are

Humanizely (“Humanizely”, “we”, “us”) is operated by JayBee Technologies. This policy explains how we collect, use and protect personal data.

2. Data we collect

  • Account data: name, email address and sign-in method (email, or Google sign-in).
  • Subscription data: your plan, its renewal and expiry dates, and billing status, received from RevenueCat.
  • Usage data: the time and word count of each humanization, used to apply your plan’s limits. We do not keep the text itself.
  • Advertising data (mobile app only): if you use the free plan in the app, Google AdMob may collect your device’s advertising identifier (Apple’s IDFA or Google’s Advertising ID), the ads shown to you and how you interact with them. See section 4A.
  • Analytics data (website, if you accept cookies): if you accept our cookie banner, Google Analytics and PostHog collect pages viewed, approximate location, and device or browser type on the website. See section 4B.
  • Technical data: IP address and browser or device information in server logs, used for security.
  • Support data: emails you send us.

3. Your text

Text you submit to the AI Detector is analyzed by our own model on our servers. Text you submit to the Humanizer is sent to OpenAI to generate the rewrite. Uploaded documents (such as .docx files) are read on your device, and their text is then handled the same way. We don’t store your text, and we don’t use it to train models. To avoid re-scoring the same text, we keep a cache of detection results (scores and the character positions they point to, not the text itself) for up to 24 hours, and per-passage scores for up to 7 days. Under OpenAI’s API terms, data sent through the API is not used to train their models by default. Your history is stored only on your own device: in your browser’s local storage on the web, or in the app’s local storage on your phone.

4. How we use data

  • Provide and secure the Service, including usage limits and abuse prevention.
  • Manage subscriptions.
  • Show ads in the free mobile app, if you have not opted out (section 4A).
  • Understand how the website is used, if you accept analytics cookies (section 4B).
  • Respond to support requests and send service emails.

4A. Advertising in the mobile app

The free Humanizely mobile app shows ads from Google AdMob, which is a Google service. Before showing ads, we ask for consent where the law requires it, using Google’s consent form. Depending on your choice and your location, ads may be non-personalized (not based on your activity across apps and sites) or personalized (based on that activity). Personalized ads use your device’s advertising identifier. On iPhone, the system will ask whether you allow tracking; if you decline, the app does not use your identifier for tracking.

You can change your choices at any time: in the app’s settings, through your phone’s privacy settings (“Reset advertising identifier” or “Ads personalization” on Android, “Allow Apps to Request to Track” on iPhone), or in your Google account. Google’s own privacy policy describes how AdMob handles data: policies.google.com/privacy.

4B. Analytics on the website

On the website only (not the mobile app), we use Google Analytics (GA4) and PostHog to understand how Humanizely is used — such as pages viewed, approximate location, and device or browser type. These tools are client-side only and do not load until you accept our cookie banner; if you reject or don’t respond, no data is sent to either. You can change your choice at any time using the “Cookie preferences” link in the website footer. See our Cookie Policy for details, Google’s privacy policy at policies.google.com/privacy, and PostHog’s at posthog.com/privacy.

5. Who we share data with

  • Supabase (accounts and database), our hosting providers, and OpenAI (Humanizer processing).
  • Google, for sign-in (if you use Google sign-in), for AdMob advertising in the mobile app (section 4A), and for Google Analytics on the website if you accept analytics cookies (section 4B).
  • PostHog, for website analytics, if you accept analytics cookies (section 4B).
  • RevenueCat and our payment processor for web purchases, and Apple or Google for in-app purchases.
  • Authorities, when required by law.

We do not sell your personal data.

6. How long we keep data

We keep account and subscription data while your account exists. Usage records are kept as long as needed to apply your plan’s limits and for 24 months afterwards. Deleting your account deletes your account, subscription and usage records. Advertising identifiers are managed by your device and by Google under its policies.

7. Your rights and deleting your account

Depending on where you live, you may have the right to access, correct, delete or export your data, and to object to or restrict certain processing. You can delete your account from Settings in the app. If you cannot use the app, you can request deletion on our account deletion page. You can also lodge a complaint with your local data protection authority.

8. Cookies

We use essential cookies to keep you signed in, and optional analytics cookies (section 4B) if you accept them. See our Cookie Policy.

9. International transfers

Your data may be processed outside your country. Where required, we use appropriate safeguards such as standard contractual clauses.

10. Children

The Service is not directed to children under 16, and we do not knowingly collect their data.

11. Security

We use reasonable technical and organizational measures to protect data, including encryption in transit.

12. Changes

We will post updates here and notify you of material changes.

Contact

If you have questions about this policy, contact us at [email protected] or through our contact form.