Legal · Privacy
Privacy Policy
Last updated: November 9, 2026
DriftMap helps teams review API contract changes. This policy describes what happens to the payloads, workspace information, and account details you choose to use with the service.
Local-first by default
The browser Workbench processes imported samples and inferred contracts locally and stores its default workspace data in IndexedDB. Your payloads are not uploaded to DriftMap by default. Cloud storage is used only when you explicitly enable and use workspace sync; data sent to a synced workspace is handled as described below.
Google sign-in
Google OAuth is used to authenticate you and identify the owner of a synced workspace. DriftMap uses the account identity required for sign-in and workspace ownership, not for advertising or unrelated profiling.
Synced workspaces and survey responses
If you enable workspace sync, cloud baselines and related workspace data are securely stored in DriftMap’s access-controlled Neon PostgreSQL database. If you complete the optional onboarding survey, your company-size range, primary API type, and CI/CD tool are stored with your user profile. Admin reporting uses aggregate category counts and does not return individual survey records or email addresses.
Retention and deletion
Browser data remains in your browser until you clear it. Synced baselines and survey responses remain in cloud storage until they are removed or you request deletion. To request deletion of cloud data associated with your account, contact DriftMap support through the support channel provided with your account or service communications and identify the account or workspace you control. We may verify ownership before processing the request.
Contact
For privacy questions or data requests, use the support channel provided with your account or service communications. Do not send account identifiers or other sensitive details through public channels.