Privacy Policy

Data we process

• Account data: email address, login/session records, plan status, preferences, and admin allowlist status.
• Company profile data: sectors, regions, value bands, keywords, and company details you choose to enter.
• Uploaded tender packs: files you upload, extracted text, generated analyses, and cited source spans.
• Public procurement data: notices and awards from public feeds with source attribution.
• Operational data: events, health signals, suppression records, request logs, and payment/webhook metadata when configured.

Lawful bases

• Contract: to provide accounts, uploads, analysis, billing, and support.
• Legitimate interests: to secure the service, improve reliability, measure conversion, prevent abuse, and conduct proportionate B2B outreach about TenderReader.
• Consent: where required for non-essential cookies or marketing choices.
• Legal obligation: where tax, accounting, or lawful request duties apply.

Uploaded pack isolation

Uploaded packs are stored under the owning user's account boundary. App routes require the signed-in owner before showing packs, analyses, files, or generated outputs.

In development, uploads use local storage. In production, the current automatic backend stores file bytes in the database unless another backend is explicitly configured.

Processors and service providers

The current or planned processor list is kept deliberately conservative so it does not imply features that are not active.

• Railway: application hosting, Postgres, deployment logs, and scheduled jobs.
• Stripe: checkout, subscription, invoice, and payment metadata once production billing keys are configured.
• Resend: transactional email and delivery webhooks once production Resend keys are configured.
• Sentry: error monitoring only if SENTRY_DSN is configured.
• LLM provider: tender-pack text may be sent to the configured non-stub model provider; external providers require their API keys, while local Ollama uses the configured local endpoint.
• Not currently active in code: PostHog browser analytics and Cloudflare R2 upload storage.

Retention

Launch-stage retention is conservative and manual: account records, uploaded packs, analyses, events, and suppression records are retained until account deletion, a valid deletion request, or operational cleanup. Automatic expiry jobs have not been implemented yet.

Some records may be retained where required for security, abuse prevention, accounting, or legal duties.

Your rights and requests

UK GDPR rights may include access, rectification, erasure, restriction, objection, portability, and complaint to the ICO. To make a data subject request, use the operator contact channel already used for your TenderReader account or onboarding conversation.

We will verify the request before disclosing or deleting account data.