Privacy Policy

1. Data Controller

LEISSON OÜ (registry code 16952932), registered in Tallinn, Estonia, is the data controller for personal data processed through ProUXAudit. Contact: privacy@prouxaudit.com.

2. Data We Collect

Account data: email address and, for sign-in, one-time codes stored only as keyed hashes for at most 10 minutes. Usage data: audit history, feature usage, IP address, browser type. Billing data: processed by Stripe; we store only Stripe customer and subscription IDs, not payment card details. Website data: fetched page content, structural (DOM) analysis, measurements taken in a browser, and screenshots of the public websites you submit for auditing.

3. How We Use Your Data

We use your data to provide the audit service, process payments, send transactional emails (account, billing, audit notifications), improve the product, and comply with legal obligations. We do not sell your personal data.

4. Legal Basis (GDPR)

We process data based on: contract performance (providing the Service), legitimate interest (product improvement, security, cookieless page-view counts), consent (marketing emails, analytics), and legal obligation (tax and financial records).

5. Data Sharing

We use service providers for payments, email, hosting, data storage, error monitoring and, with your consent on public pages, Google Analytics and PostHog. Vercel Web Analytics and Speed Insights count page views and page-load timings on public pages without cookies and without identifying you. Their processing terms and transfer safeguards apply. We do not sell personal data to advertisers.

6. Data Retention

Account data is retained while your account is active and for 30 days after deletion. Audit data (screenshots, reports) is retained for 90 days after the audit, or until you delete it. Billing records are retained for 7 years per Estonian tax law.

7. Your Rights

Under GDPR, you have the right to access, correct, delete, export, and restrict processing of your personal data. You can exercise these rights by emailing privacy@prouxaudit.com. We will respond within 30 days.

8. Cookies

Essential authentication cookies work independently of analytics. On public pages, Google Analytics and PostHog activate only after you choose “Accept analytics”. You can decline or change your choice using the analytics control on a public page. Vercel Web Analytics sets no cookie and stores nothing on your device, so it counts visits regardless of that choice; it receives only the page path, never the query string. We do not send email addresses, audit URLs, report tokens or form text as analytics events.

9. Security

We use encryption in transit (TLS), encryption at rest for database backups, bcrypt password hashing, and strict access controls. We monitor for security incidents via Sentry and conduct regular security reviews.

10. International Transfers

Data may be processed in the EU and US (Vercel, Cloudflare). US transfers are covered by the EU-US Data Privacy Framework. All processors maintain appropriate safeguards.

11. Changes

We may update this policy at any time. Material changes will be communicated via email. Continued use after changes constitutes acceptance of the updated policy.

12. Public MCP Connector

You can request an audit through a compatible AI client, such as Claude, ChatGPT or Codex, when our public MCP connector is enabled. We receive the website URL and optional report language submitted to the tool. The connector does not request your conversation history, AI account profile or email address. Your AI client separately processes the tool inputs and results under its own terms.

We fetch the public page and analyse its content and structure. We store extracted page text, evidence, measurements and findings rather than a complete copy of the fetched HTML. When browser capture is enabled and available, we also process the rendered page and may capture a screenshot and browser measurements. Public page content can contain personal data; submit only public URLs you are entitled to audit and avoid confidential information in URLs or page content.

We store the audit result and make a public report available after a completed connector audit or reuse of a completed result. Anyone with the report link can view the report, including its public page information and evidence. New report links expire after 90 days by default; an existing link retains its configured expiry and can be revoked. Link expiry or revocation does not delete the underlying audit or copies made by others.

Execution records include the submitted and captured URLs, creation and completion times, job status, capture method, evaluation version and whether the audit started through the connector. Fresh verification links two audit runs internally. If you save an anonymous audit to an account, we record its new ownership and the time of the first successful claim.

For connector reliability, we record a tool-use event with the tool name, outcome, whether the response was cached and duration, together with the event time and the fixed connector route. These connector events do not include the audited URL, IP address, auditHandle, account identifier or conversation text. Audit execution and an optional later account claim have separate operational records.

To limit requests, the connector reads the caller IP from request headers and uses a keyed hash, request count and reset time in server memory. It does not store the raw IP in this counter. The counting window is 60 seconds by default and can be configured. An expired counter stops contributing to the limit, but its entry is replaced only on a later request with the same key or removed when the server process ends; the window is not a deletion deadline. Hosting providers also process network requests under their own settings and terms.

The auditHandle is a secret access token valid for 14 days from issue. The server checks expiry and revocation before allowing access. Anyone holding a valid token can read that audit, request a fresh audit of the same URL and, after signing in, save an unclaimed audit to their account. Saving does not automatically revoke existing tokens or report links. Keep the token private; to request revocation, contact privacy@prouxaudit.com. Expiry blocks access but does not delete the token record or audit.

For connector data, these specific retention details apply: stored URLs, extracted page evidence, screenshots, results, execution records, token and report-link records, and connector tool-use events currently have no automatic deletion deadline in the service. They may remain after access tokens or report links expire, until a deletion request is fulfilled. Request deletion at privacy@prouxaudit.com. The 14-day token lifetime, default 90-day report-link lifetime and request-counting window are access or counting limits, not promises of automatic data deletion. Provider logs and backups follow the applicable provider settings and terms; this connector does not set a separate deletion deadline for them.

Vercel processes connector requests and hosts the application; Neon stores audit, token, report-link and event records. Screenshots, when available, are stored in private Vercel Blob storage and served through access checks in the application. Browserless receives the target URL and processes the page when browser capture is used. If the optional AI summary is configured, OpenAI receives audit and job references, URLs, extracted page details, findings, evidence and recommendations to generate that summary; the API request sets response storage to false, which does not establish a retention period for provider logs. The audited website and resources loaded during browser capture also receive network requests. Which optional processors are used depends on the enabled capture and summary settings.