Security - Thought Pins

Account and session security

Production deployments require authenticated accounts, rate-limit sensitive endpoints, hash passwords using a memory-hard password algorithm, rotate refresh sessions, and support revocation and device management. Local no-auth sessions are restricted to development and are not part of submitted public builds.

Tenant isolation

Application queries are scoped to the authenticated user. The production database path includes tenant-aware schema design and database-level row security as defense in depth. Authorization checks are tested at API and data-access boundaries.

Transport, storage, and secrets

Production traffic is designed to use TLS. Credentials and provider keys are server-side configuration and are excluded from public clients and API responses. Protected content can use encryption at rest, and exported data is delivered only through an authenticated account workflow.

Operational safeguards

Request IDs, structured logs, health checks, processing queues, audit events, backups, restore procedures, dependency scanning, and release gates support incident investigation and reliable recovery. Sensitive request bodies and authorization values should be scrubbed from diagnostics.

Data lifecycle

Users can remove individual entries, export account data, revoke devices, and permanently delete the account and associated memory data. Lifecycle operations are tenant-scoped and are covered by automated tests.

Responsible disclosure

Report suspected vulnerabilities privately to security@thoughtpins.com with a concise description, affected surface, reproducible steps, and impact. Do not access other users' data, perform denial-of-service testing, use social engineering, publish sensitive findings before remediation, or test production without authorization. Thought Pins does not currently operate a paid bug-bounty program.