Synchronise uses read-only access to scan your documents for drift. We process content ephemerally and never store your document contents. Your data stays yours.
What actually happens during a scan
Processed ephemerally
Document content lives only in memory during analysis
PRD: Q2 Mobile Launch
Full text read to detect drift against downstream work.
→Analyze the source document and compare it with connected artifacts
→Generate a finding only if there is a concrete mismatch
Discard raw content after processing
Stored in Drift
Metadata and findings needed to review the issue later
We request minimal OAuth scopes. Synchronise never modifies, creates, or deletes anything in your tools.
All data is encrypted using TLS 1.3. OAuth tokens are encrypted at rest with AES-256-GCM.
Your data is never used to train AI models. We use Claude API with data retention disabled.
We store only metadata: document titles, unique identifiers, timestamps, and the findings we generate. Document contents are processed in memory and immediately discarded after analysis.
Your integration tokens are encrypted using AES-256-GCM before storage. We use refresh tokens where available to minimize re-authentication. You can revoke access at any time from your settings.
We use Anthropic's Claude API for analysis (with zero data retention), Supabase for database and authentication, and Vercel for hosting. All processors are SOC 2 compliant.
We're happy to answer any questions about how we handle your data.
Contact us