Skip to content
AIGator: Free AI Detector

Privacy Policy

Effective date: 13 July 2026
Last updated: 2 September 2026

This Privacy Policy explains how AIGator collects, uses, shares, and protects personal data when you visit AIGator.com or use the AIGator AI text checker and related services.

1. Controller and contact details

The controller responsible for AIGator is:

Roth Media GmbH
Lorrainestrasse 19
3013, Bern
Switzerland

2. Scope

This policy applies to AIGator.com, api.aigator.com, the AI Checker, AIGator accounts, saved reports, billing, the Prompt Library, the Blog, and other AIGator pages and features that link to this policy.

3. Data we process

Text submitted for analysis

When you use the AI Checker, the text you submit is transmitted securely to api.aigator.com and processed to produce an AI-likeness result, evidence trail, confidence level, and reliability information.

AIGator does not save the full submitted text in an AIGator application database by default. Text is processed for the request and sent to our API as described below. AIGator may temporarily cache a derived result in server memory using a cryptographic text fingerprint so that an identical repeated check can be returned without another model request. The cached result does not contain the full submitted text and normally expires within 24 hours or when the application process restarts.

Metadata-only check history

For verified signed-in accounts, AIGator may keep a metadata-only history of completed checks when the user’s Keep check history preference is enabled. This can include an optional report title, date and time, word and character counts, credits used, the overall classification, confidence, content-type classification, a short result summary, reservation identifiers, and keyed cryptographic fingerprints used to verify report integrity. Metadata-only history does not contain the full submitted text, sentence excerpts, highlighted passages, or the full result object.

Users can turn Keep check history off from Account settings. When it is turned off, AIGator stops creating future metadata-only entries and deletes existing summary-only history entries for that account. Reports the user explicitly chose to save are preserved and remain available until the user deletes them or their retention period expires.

Reports you choose to save

After a completed check, a verified signed-in user may choose Save report. This is optional. When selected, AIGator stores the submitted text and the detailed result in the user’s account so that the report can be reopened, renamed, printed, or permanently deleted. Saved report text and result data are encrypted by the application before they are written to the AIGator database.

The save dialog explains that the submitted text is not retained by default and asks the user to confirm before full text is stored. A saved report is accessible only through the authenticated account to which it belongs.

Account and billing data

When you create an account, we process information such as your email address, display name, WordPress password hash, verification status, security information, plan, quota, credit balance, usage reservations, and account activity. Passwords are handled by WordPress and are not available to AIGator in readable form.

When you purchase a plan or credit pack, we may store billing identifiers and status information such as Paddle customer, transaction, subscription, price, adjustment, and event identifiers; plan and subscription status; billing-period dates; credit grants; usage allocations; and immutable credit-ledger entries. AIGator does not receive or store full payment-card details.

Pausing, canceling, or otherwise ending a paid subscription does not by itself delete the AIGator account, metadata-only check history, saved reports, support correspondence, or billing records. These are handled under the choices and retention rules below. Subscription credits may become unavailable, expire, or be retired according to the applicable plan and billing state, while separately purchased prepaid credits may remain available unless they are refunded, disputed, expired, or otherwise reversed.

Technical and security data

Our hosting, content-delivery, and security systems may process technical data such as IP address, date and time, requested URL, browser and device information, referring page, error information, and security or rate-limit events. This information is used to deliver the site, prevent abuse, diagnose faults, and protect the service.

Analytics data

We use Google Analytics to understand how the website is used. Depending on your location and consent choices, Google Analytics may process page views, interactions, approximate location, device/browser information, referral information, and identifiers stored in cookies or similar technologies. We do not intentionally send submitted checker text or saved-report text to Google Analytics.

Communications

If you contact us, we process the information you provide, such as your name, email address, message, and related correspondence. We also process the information needed to send account verification, password-reset, billing, and service messages.

4. Purposes and legal bases

  • Providing the requested service: to analyze submitted text, return a result, operate accounts and billing, keep metadata-only check history, and store a full report when the user explicitly requests it.
  • Security and service reliability: to authenticate accounts, prevent abuse, enforce limits, investigate faults, protect saved reports, and protect AIGator and its users.
  • Billing and contract administration: to process purchases, maintain credits and subscriptions, reconcile refunds or disputes, and provide customer billing controls.
  • Analytics and improvement: to understand website usage and improve the service. Where required, we rely on your consent before non-essential analytics storage is used.
  • Communications: to verify accounts, provide service messages, answer inquiries, and provide requested support.
  • Legal compliance: to comply with applicable legal obligations and establish, exercise, or defend legal claims.

Depending on the circumstances and applicable law, processing may be based on performance of a contract or steps requested before a contract, legitimate interests, consent, or legal obligations.

5. API processing

The AI Checker uses our API to assist with writing-pattern and evidence analysis. Your submitted text is therefore sent to api.aigator.com for this purpose. Depending on the function and current configuration, AIGator may use commercial model APIs, including Anthropic and OpenAI. We do not opt in to using AIGator API inputs or outputs for provider model training. We configure requests not to create provider-side application history where supported. Provider-side operational, safety, or abuse-monitoring records may nevertheless be retained for up to 30 days under standard commercial API terms, unless shorter or zero-retention controls apply, or longer retention is required for security or legal reasons.

Choosing to save a report is a separate AIGator account feature. It does not change the storage-disabled setting used for the model API request. After the result is returned, AIGator stores the submitted text and detailed result in its own encrypted saved-report record only when the user explicitly confirms saving.

Do not submit confidential, legally privileged, secret, or sensitive personal information unless you are authorized to do so and accept the processing described in this policy.

6. Service providers and recipients

We may use service providers that process data on our behalf or as independent controllers, including:

  • Hosting and server providers: KnownHost, United States.
  • Cloudflare: content delivery, network security, traffic management, Turnstile, and related technical services. See Cloudflare’s Privacy Policy.
  • api.aigator.com: AIGator’s application API for text analysis, account entitlements, billing reconciliation, Prompt Library generation, and saved-report functions.
  • Anthropic: commercial model API processing used for writing-pattern analysis where configured. See Anthropic’s commercial-customer privacy information.
  • OpenAI: commercial model API processing used for configured text, Prompt Library, and image-generation functions. See OpenAI’s business-data privacy information.
  • Paddle: merchant-of-record services for payment processing, subscriptions, taxes, customer billing, refunds, and disputes. See Paddle’s Privacy Policy.
  • Amazon Web Services / Amazon SES and WordPress mail tooling: transactional email delivery.
  • Google Workspace: receipt and management of support and business email.
  • Google Analytics / Google: website measurement and analytics, subject to your consent choices where required. See Google’s Privacy Policy.
  • Professional advisers and authorities: where reasonably necessary for legal, security, accounting, or compliance purposes.

7. International data transfers

Some service providers may process data in countries outside Switzerland, the European Economic Area, or your country of residence. Where required, we use recognized safeguards such as adequacy decisions, contractual protections, or other lawful transfer mechanisms.

8. Retention

  • Submitted checker text: not stored in an AIGator application database by default after the request; it is subject to the API processing described above.
  • Metadata-only check history: normally retained for 90 days and then deleted automatically, unless a shorter retention period is configured, the user deletes the entry sooner, or the user turns Keep check history off. Turning history off deletes existing summary-only entries for that account.
  • Saved reports: normally retained for 90 days from the save date and then deleted automatically, unless a shorter retention period is configured or the user permanently deletes the report sooner.
  • Derived in-memory result cache: normally up to 24 hours, or less if the application restarts.
  • Account, quota, billing, and credit-ledger records: retained while needed to provide the account and billing service, reconcile usage, meet accounting or legal obligations, resolve refunds or disputes, and prevent fraud or abuse. Some billing and ledger records may be retained after a subscription ends or an account-deletion request is completed where reasonably necessary for those purposes.
  • Aggregate API usage ledger: We store aggregate request counts, token totals, estimated API cost, and failure counts for the current UTC day. The ledger does not contain submitted text or user account identifiers. When usage is recorded on a new UTC day, the previous daily record is overwritten.
  • Server and security logs: Technical logs may contain information such as an IP address, timestamp, requested URL, browser or user-agent information, error details, and security-event information. These logs are retained under the log-rotation and retention settings of our hosting, content-delivery, and security providers for as long as reasonably necessary to operate, secure, and troubleshoot the service, prevent abuse, investigate incidents, and comply with legal obligations. Logs relating to an active security incident, abuse investigation, legal claim, or regulatory matter may be retained longer until the matter has been resolved.
  • Google Analytics data: retained according to the retention period configured in our Analytics property, currently 14 months.
  • Communications: retained for as long as reasonably necessary to answer the inquiry and meet legal or record-keeping obligations.

9. Cookies and similar technologies

AIGator and its providers may use essential cookies or similar technologies for security, authentication, traffic management, preferences, and service operation. Google Analytics may use analytics cookies or cookieless measurement depending on the consent configuration. Where applicable law requires consent, non-essential analytics technologies should not be activated until consent is provided.

You can manage cookies through your browser and any consent controls displayed on the site. Google also offers a Google Analytics opt-out browser add-on.

10. Your choices and rights

You can use the checker without saving a report. Signed-in users can disable metadata-only check history from Account settings, permanently delete individual history entries, and permanently delete saved reports. Turning history off deletes existing summary-only entries and prevents new automatic history entries, while preserving reports the user explicitly saved. Deleting a saved report removes its stored text and detailed result from the active AIGator database. Ending a paid plan does not automatically delete these account records. You may request deletion of the account and associated account content separately, subject to records that we must or reasonably need to retain for billing, security, dispute, fraud-prevention, or legal purposes.

Subject to applicable law, you may have rights to request information about personal data we process, access it, correct inaccurate data, request deletion or restriction, object to certain processing, receive portable data, or withdraw consent. You may also have the right to complain to a competent data-protection authority.

To exercise a right, request an account-data export or deletion, or ask a privacy question, email [email protected]. We may need to verify your identity before responding.

11. Security

We use technical and organizational measures designed to protect data, including HTTPS, access controls, short-lived account tokens, rate limits, server-side API credentials, keyed integrity fingerprints, application-layer encryption for saved-report text and results, security monitoring, and data minimization. No internet service can guarantee absolute security.

12. Children

AIGator is not directed to children under 16. If you believe a child has provided personal data without appropriate authorization, contact us.

13. Changes to this policy

We may update this Privacy Policy as the service, providers, or legal requirements change. The current version will be published on this page with an updated date.

14. Contact

Privacy questions can be sent to [email protected].