Privacy Policy

How Recensa collects and uses account data, uploaded PDF and Word documents, AI model processing, Google Drive imports, Stripe billing, retention, and subprocessors—in plain English.

Last updated 2026-05-13

Summary

Important: These pages describe how Recensa is intended to work and how we handle data. They are not a substitute for legal advice. Ask qualified counsel to review them before you rely on them for compliance, customer contracts, or regulatory filings.

What Recensa is

Recensa is a document review and proofing platform—not a law firm. You upload finished documents (for example PDF or Microsoft Word files), may attach supporting or context files when your plan allows, and receive structured outputs such as issue lists, proof reports, reviewed or corrected documents, and related logs. Recensa does not provide legal, financial, medical, tax, compliance, or other professional advice.

Information we may collect

Account and session information, such as the email address you use to start a session in the app.
Main documents you upload for review or fix—the editable target of your Document Check.
Supporting, source, or context files you attach when your plan allows. These are used as reference material for review and should not be treated as the editable target document unless the product flow expressly indicates otherwise.
Text and instructions you type into the product, such as context, review focus, or do-not-change notes.
Generated outputs from review or fix runs, including documents, PDFs, reports, ledgers, logs, and similar artifacts.
Feedback you submit through feedback or feature-request flows, including optional attachments you choose to include.
Google Drive, if you connect or use Drive: files and metadata involved in import or save-back actions you initiate, such as file identifiers, names, and content needed to run the job.
Payment and subscription data processed by Stripe, such as plan status and billing events. Recensa does not need to store full payment card numbers to operate hosted Checkout; card details are handled by Stripe according to its terms and privacy policy.
Operational data such as job identifiers, status, errors, timestamps, and security or diagnostic logs needed to run and protect the service.

How we use information

To provide document assurance, proof checks, source-grounded edits, and export features you request.
To generate reviewed or corrected outputs and related artifacts.
To process supporting or context files you provide as reference material for review.
To manage subscriptions, entitlements, and fair-use limits.
To troubleshoot, secure, maintain, and improve the product.
To respond to support or feedback messages you send us.
To perform Google Drive import or save-back when you choose those actions.

AI and model providers

To perform review and fix workflows, Recensa may send document text or extracted content, together with instructions and context you supply, to third-party AI model providers. Depending on how your deployment is configured, those providers may include OpenAI, Anthropic, Google (Gemini), or other model vendors added over time. Those companies process data on their own systems under their own terms and privacy policies. We do not control their retention or deletion practices.

Do not upload content you are not authorized to share with such providers. You remain responsible for reviewing and approving final documents and for verifying outputs before you rely on them for filing, publication, or business decisions.

Google Drive

If you use Google Drive integration, Recensa accesses Drive only in connection with actions you take, such as choosing a file to import or asking us to save a new output file. We do not manage, scan, or synchronize your entire Drive. Save-back creates new files; we do not silently overwrite your originals in Google Docs or other native formats in place. Google's own terms and security practices also apply.

Retention and deletion

Uploaded files and generated outputs are kept only as long as needed to operate the service and according to retention settings configured for your deployment. Jobs are typically assigned a scheduled deletion time—for example based on a default hour window, or a shorter window when you enable sensitive-style handling for a run. A background process removes eligible files from our storage after that time. Exact timing can vary with load and maintenance; we do not promise immediate deletion the moment a job completes.

Some metadata or logs may be retained longer for security, troubleshooting, billing, or legal reasons, or where the product still depends on them. Deletion from our systems does not necessarily mean deletion from every third-party provider that processed content during your job; provider practices govern their copies.

There is no self-service “delete everything” button guaranteed in the product today. For deletion requests, contact privacy@draftlensai.com (see also Data security). We will respond consistent with our capabilities and applicable law.

Service providers and disclosure

We use subprocessors and infrastructure partners as needed to run Recensa, which may include:

AI model providers, as described above.
Cloud hosting and storage vendors.
Payment processing through Stripe.
Email or analytics vendors if enabled for a deployment.

We may also access, preserve, or disclose information when we reasonably believe it is necessary to comply with law, protect safety, or enforce our terms.

Security

We apply reasonable administrative, technical, and organizational measures appropriate to the service. No method of transmission or storage is free of risk. Use strong access practices and do not upload materials you are not permitted to process.

Children

Recensa is not intended for children under 13 or for minors where prohibited. Do not use the service if you are not old enough to consent in your jurisdiction.

International users

Recensa may be operated from or hosted in the United States or other regions. If you use the service from outside those regions, your information may be processed where we or our providers operate. We do not represent that the product satisfies every local law; consult counsel if you have cross-border requirements.

Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating this page and the “Last updated” date shown in the page header.

Contact

Privacy questions: privacy@draftlensai.com
General support: support@draftlensai.com

Before listing these addresses in Google OAuth branding or customer materials, configure mailboxes or forwarding—see docs/trust-and-email-setup.md.