Security

Encryption

All traffic between your browser and Contexory is encrypted in transit with TLS 1.2 or higher. Workspace content, AI logs, and integration configuration are stored in PostgreSQL hosted by Supabase, with AES-256 encryption at rest provided by the underlying storage layer. Secrets — GitHub installation keys, Stripe customer IDs, third-party API tokens — are stored encrypted and accessed only by backend processes that need them.

Authentication

Sign-in is handled by Supabase Auth. We support email-and-password with verified email addresses, and Google OAuth. Sessions use rotating refresh tokens with secure, HTTP-only cookies. If you sign in with Google, two-factor authentication is handled by your Google account.

Access controls

Within a workspace, every member has a role — Owner, Admin, or Member. Roles gate sensitive actions like inviting members, connecting integrations, and changing billing. Inside the database itself we enforce row-level security: a query for one workspace can never return rows from another, even if application code has a bug.

AI processing

AI features send prompt and document context to OpenAI for inference. Where the scoping assistant needs to ground unfamiliar terms, we send the relevant query to Tavily. We do not permit either provider to use your content for model training. Telemetry to LangSmith is opt-in and disabled by default; operators must explicitly enable it via environment variable.

Payments

Card details are never seen or stored by Contexory. Stripe Checkout and the Stripe Customer Portal handle all payment-instrument collection and management. We hold only Stripe customer and subscription identifiers needed to apply seat counts and AI usage allowances to your workspace.

Integrations

The GitHub integration uses a GitHub App installation, not a personal access token. Permissions are scoped to the repositories you explicitly approve during install. Webhook deliveries from GitHub are verified by signature on each request; deliveries with invalid signatures are rejected.

Infrastructure

Contexory runs on serverless infrastructure with managed Postgres and edge networking. Backups of the workspace database are taken daily and retained for at least 7 days. Recovery is tested as part of routine operations.

Logging and monitoring

We log authentication events, billing events, integration sync events, and significant errors. These logs are retained for at least 90 days and are reviewed during incident response. We do not log AI prompt or completion bodies in long-term storage; only metadata necessary for billing and quota enforcement.

Vulnerability disclosure

If you have found a security vulnerability in Contexory, email security@contexory.com. Please give us a reasonable opportunity to investigate and fix before disclosing publicly. We do not currently run a paid bounty program but we will acknowledge contributors with their permission.

Out of scope for disclosure: denial-of-service testing, social engineering of Contexory staff, physical attacks against our infrastructure or staff, and findings on subprocessor systems themselves (those should be reported to the subprocessor directly).

Incident response

If we detect a security incident that affects your workspace, we will notify you without undue delay and in any case within the timelines required by applicable law. Notifications include what happened, what data was involved, what we have done in response, and what action (if any) we recommend you take.

More

Our Privacy Policy lists the third-party subprocessors that handle your data. The Terms of Service govern overall use of the Service.