Privacy Policy

Data we collect

DrukOrbit accesses your Google Contacts via the Google People API only after you explicitly log in with Google and grant permission. We collect:

• Your name, email, and profile picture (from your Google profile)
• Your contacts — names, emails, phone numbers, organizations, job titles, addresses, and any other fields available through the Google People API
• OAuth tokens (access and refresh tokens) to keep your contacts synced

How we use your data

Your data is used solely to display your contacts as a personal org chart. Contact data is never shared with other users, third parties, or used for training AI models. Each user’s contacts are isolated and private.

Data storage

Contacts are stored in a PostgreSQL database (Neon). Session data is stored in Redis (Upstash). Both are encrypted at rest. We retain your contact data until you disconnect your Google account or request deletion.

Data deletion

You can delete your data at any time by contacting us. When you disconnect your Google account or request deletion, all associated contacts, tokens, and session data are permanently removed.

Google API disclosures

DrukOrbit's use and transfer to any other app of information received from Google APIs will comply with the Google API Services User Data Policy, including the Limited Use requirements.

Compliance & certifications

DrukOrbit is built on infrastructure that meets enterprise and government compliance standards:

• SOC 2 Type II — Our infrastructure providers (Vercel, Neon, Upstash) are SOC 2 audited for security, availability, and confidentiality.
• ISO 27001 — Information security management certified infrastructure.
• GDPR — Data is processed in accordance with GDPR requirements. Contact data is stored in region-specific databases with data residency controls.
• FedRAMP — Vercel, our hosting platform, maintains FedRAMP authorization, supporting government-adjacent deployments.
• Encryption — AES-256 encryption at rest (PostgreSQL, Redis) and TLS 1.3 encryption in transit for all API traffic.
• Data isolation — Each user's contacts are strictly partitioned by userId. No cross-user queries exist. Identity matching is within-user only.