PRIVACY & DATA HANDLING

Privacy, explained
in practical terms.

This early-alpha notice describes the data handling currently implemented in Searqon. It is a transparency document—not a substitute for the final legally reviewed privacy notice required before general availability.

Early-alpha notice · legal review pending

The final controller identity, hosting region, complete processor list, retention schedule and formal rights-request process must be confirmed before the hosted service is opened for general use.

DATA THE WORKSPACE PROCESSES

What the application needs.

DataWhy it is processedCurrent handling
Email addressAccount identity and one-time sign-in delivery.Normalized and stored with the account; sent to the configured email delivery provider.
Name and organizationDisplay the user and create the initial workspace.Stored as profile and organization fields.
Authentication tokensVerify sign-in links and sessions.Magic-link and session tokens are stored as SHA-256 digests, not as raw token values.
Peer IP rate-limit digestLimit automated sign-in abuse.The server HMACs the socket peer address; raw IP values are not stored in the rate-limit table. Forwarded headers are not trusted by default.
Project detailsOrganize properties in a workspace.Project name and canonical target URL are stored.
Assessment report and audit metadataPreserve project assessment history and accountability.Structured reports and workspace audit events are stored. Raw submitted document bytes are not stored by the workspace assessment service.
RETENTION & SECURITY

Known controls.
Known gaps.

01

Authentication lifetime

Magic links expire after 15 minutes. Sessions expire after 30 minutes of inactivity or 24 hours absolute, whichever occurs first.

02

Stored credentials

Raw magic-link and session tokens are not stored in PostgreSQL. Session cookies are HttpOnly and Secure in production.

03

Assessment content

Assessment requests accept up to 2 MiB of caller-supplied content. The hosted workspace stores the resulting report, not the raw document body. Do not submit secrets, regulated data or material you are not authorized to share.

04

Retention is not yet fully automated

Automatic cleanup for expired auth tokens and rate-limit rows, and a customer-facing retention/deletion workflow for project records and reports, are not yet implemented. No fixed hosted data-retention period is currently promised.

SERVICE PROVIDERS & THIRD PARTIES

Infrastructure transparency.

When configured, transactional sign-in email is sent through Resend. The marketing, documentation and account pages currently load Instrument Sans and DM Mono through Google Fonts; those requests disclose normal connection metadata such as IP address to Google's font infrastructure. The production hosting provider, database region, backup provider and complete processor list are not yet finalized in this public notice.

No advertising or analytics tracker is intentionally included in the current website source.

CONTACT

Privacy questions.

For a privacy question or data-handling concern, contact hello@tinlance.com. A formal request-verification and response process must be published before general availability.

Last updated: 17 November 2026 · Early-alpha transparency notice.