Skip to content
DocInfra

Privacy & Personal Data Processing Policy

Version 1.0, effective September 28, 2026, last updated September 28, 2026.

This policy explains how DocInfra processes personal data. It is both our privacy policy and our personal data processing policy under Colombian law (Ley 1581 de 2012 and Decreto 1074 de 2015), and it is written to support the transparency obligations that may apply to us in other jurisdictions. It is not a certification of compliance with any specific law.

1. Who is responsible

The data controller (“Responsable del Tratamiento”) for the processing described here is DocInfra, a trade name of its operator, an individual entrepreneur established in Colombia. Contact for personal data matters: privacy@apidocinfra.com, or the support page at apidocinfra.com/support/ (category “Privacy / data request”). The operator’s legal identification details are available on request and will be published here once the corresponding registration is completed.

For content that a business customer processes through the API on its own behalf (its own documents and texts, which may contain personal data of third parties), the customer is the controller and DocInfra acts as processor (“Encargado del Tratamiento”) under the Data Processing Addendum at apidocinfra.com/dpa/.

2. What we process

Account data. Email address, display name, the identity provider you used (email and password, or Google) and the technical identifier it gives us, whether the email is verified, and the dates of creation and last sign-in.

Workspace data. The workspace name, your membership and role, and the metadata of your API keys (name, prefix, creation and last use). We store a hash of each key, never the key itself.

Usage data. Counts and timings of each operation (conversion, text rewrite, document rewrite): words in and out, bytes, duration, outcome, plan limits consumed. Rewrite telemetry records the percentage of text changed and the intensity used, never the text.

Product analytics. Anonymous events from the website and the dashboard (page viewed, tool started, sign-up completed, checkout started and similar) with the page path, language, the domain of the referring site and campaign parameters. There is no user identifier in these events and no content.

Billing metadata. Plan, subscription status, period dates, the identifiers Lemon Squeezy assigns to the customer, subscription and orders, and the events it sends us. Card numbers never reach DocInfra.

Support data. The email address, category, subject and description you write in a support case, the case number and its status history.

Technical and security data. Server logs with request identifiers, timestamps, status codes and error codes; security events; the audit trail of actions in a workspace. For the free Humanizer and the support form we compute a keyed hash of your IP address to apply hourly limits; the hash is stored, the address is not.

Content you submit. The text and documents you send for rewriting or conversion. Section 5 describes exactly what happens to them.

Legal acceptance records. When you accept the Terms and this policy, we record your user identifier, the document, its version and hash, the language, the source of the acceptance and the time. For the free Humanizer, the same record is anonymous: the hash used for rate limiting instead of a user.

We do not collect data from public sources, we do not buy data and we do not profile you.

3. Why we process it and on what basis

We process personal data only to:

  • provide the Service and its features;
  • authenticate you and keep your account secure;
  • detect and prevent abuse, fraud and attacks;
  • measure usage and apply plan limits;
  • bill paid plans through our merchant of record;
  • answer support, privacy and security requests;
  • send transactional messages (account verification, password reset, case confirmations, service notices);
  • improve reliability using counts and timings, never content;
  • keep the records the law requires and comply with legal obligations.

The legal basis is, depending on the case, your authorization (given when you create an account or click Humanize), the performance of the contract you have with us, our legal obligations and our legitimate interest in keeping the Service secure and working. We do not use your data for marketing. If we ever add marketing communications, we will ask for a separate, optional consent first.

4. Artificial intelligence

The Humanizer, Text Rewrite and Document Rewrite send the text to be rewritten to Cloudflare Workers AI through Cloudflare AI Gateway, where a language model generates the result. Our configuration:

  • our application logs never contain the prompt or the output;
  • AI Gateway runs with payload collection disabled, so the gateway keeps metadata (timings, tokens, status) and not the text;
  • DocInfra does not use your text to train or tune any model;
  • Cloudflare states that Customer Content processed by Workers AI is not used to train its models or improve its services without explicit consent.

We do not claim “zero retention” on the provider’s side, because we do not hold a specific contractual commitment with that wording. What we control, and what is stated above, is what we send and what we keep.

5. Where your content goes and for how long

Free Humanizer. The text is processed for that request and returned. DocInfra does not persist it as content: it is not written to the database or to logs. Only the word count, timing, outcome and the anonymous legal record remain.

Text Rewrite (API and dashboard). The original and the result are not stored in the database and do not appear in logs. If you send an Idempotency-Key header, an encrypted copy of the response may stay in Redis for up to one hour so that a retry returns the same answer; it is then deleted.

Document operations (conversion and document rewrite). The original and the result are stored in our object storage (Cloudflare R2) so that you can download them, and are deleted 24 hours after the operation; the storage bucket has an independent lifecycle rule that removes any remaining object after 2 days.

Account, workspace and billing metadata. Kept while the account exists. After a valid deletion request we delete or anonymize it within 30 days, except records that must be kept by law (see section 6).

The full retention schedule is in section 6.

6. Retention

Data Retention
Humanizer text Not stored
Text Rewrite original and result Not stored; idempotent replies in Redis up to 1 hour
Documents (conversion, document rewrite) Deleted 24 hours after the operation; storage lifecycle 2 days
Account, workspace, API key metadata Life of the account; deleted or anonymized within 30 days of a valid request
Product analytics events 12 months, then deleted automatically
Security and audit logs 12 months, unless a documented legitimate need requires longer
Support cases and privacy requests 5 years from case closure
Acceptance of Terms and policies, billing and commercial evidence 10 years where Colombian commercial record keeping rules apply

Customer content is never kept for 10 years because of the commercial record keeping rule: that rule covers the evidence of the contract (acceptances, orders, invoices), not the texts and documents you processed.

7. Who receives data

We use service providers that process data on our behalf. The current list, what each one does and where, is published at apidocinfra.com/subprocessors/ and kept up to date. In summary: Cloudflare (hosting of the website and dashboard, network edge, object storage, the AI model, bot protection and privacy-oriented web analytics), Contabo (the server that runs the API, in the United States), Resend (transactional email), Lemon Squeezy (merchant of record for paid plans) and Google (only if you sign in with Google).

Because these providers operate in the United States and other countries, your data may be processed outside Colombia. We choose providers that publish data processing terms and apply security measures, and we send them only what each function needs.

We do not sell personal data and we do not share it with advertisers. We disclose data to authorities only when the law requires it.

8. Your rights

You have the right to:

  • know which personal data we hold about you and access it;
  • update and correct it;
  • request its deletion when there is no legal reason to keep it;
  • revoke the authorization you gave, where the processing depends on it;
  • know how your data has been used;
  • submit queries and complaints about the processing;
  • complain to the competent data protection authority (in Colombia, the Superintendencia de Industria y Comercio) after using the procedure below.

To exercise a right, open a case at apidocinfra.com/support/ with the category “Privacy / data request”, or write to privacy@apidocinfra.com. Every request receives a case number. We answer queries and access requests within 10 business days and complaints, correction, deletion and revocation requests within 15 business days, counted from receipt; if a request needs more time we tell you why and when. We do not ask for an identity document up front; we verify your identity only when the request requires it, usually by sending a confirmation to the email address on the account.

You can also export your account data (profile, workspace, key metadata, usage summary) by opening a case of type “Export account data”.

9. Cookies and local storage

The public website does not set cookies and does not use browser storage. It loads two third-party scripts: Cloudflare Turnstile, only on the pages with a form (the Humanizer and the support page), to tell people from bots without a captcha puzzle, and Cloudflare Web Analytics, a privacy-oriented measurement beacon that does not use cookies or fingerprinting.

The dashboard sign-in uses session cookies set by our authentication server on auth.apidocinfra.com; they are strictly necessary to keep you signed in. During sign-in the dashboard keeps a short-lived entry in your browser’s local storage to complete the login securely, and removes it afterwards. Session tokens are kept in memory.

There are no advertising cookies, no behavioral tracking and no third-party trackers, so there is no cookie banner. If that changes, we will ask for consent before loading anything that is not strictly necessary.

10. Security

Data travels encrypted (TLS). The API and the processing engines run without direct internet access, files are scanned for malware before processing, secrets are kept outside the code, access to production is limited to the operator and logged, and the actions in a workspace leave an append-only audit trail. Details are on the security page at apidocinfra.com/security/.

If a security incident affects personal data, we follow an internal response procedure: we contain it, establish what data and which people are affected, assess the risk and, when the law or the risk requires it, notify the affected people and the competent authority without undue delay.

11. Children

The Service is not directed to people under 18 and we do not knowingly collect their data. If you believe a minor has created an account, write to privacy@apidocinfra.com and we will delete it.

12. Changes

Each version of this policy has a version number and an effective date, and its content is recorded so it can never be modified silently. Material changes are published as a new version and registered users are asked to authorize the processing again before they continue using the dashboard.