Trust isn't asettings page.

Every operational record on the platform is scoped to an organization at the database layer. Reads and writes that don't include the organization scope are rejected by the data-access layer. Cross-tenant reads have never happened in production, and we run automated checks on every change to keep that record.

Refresh and access tokens are stored encrypted at rest in our primary database, scoped to the connecting organization. Tokens are never written to logs or shared with third-party services. You can revoke access at any time at myaccount.google.com/permissions or from your Hello Native dashboard at /dashboard/core/integrations/google.

We use Google data only to provide the user-facing features the customer connected the integration for. We don't use Google data to train AI models. We don't transfer it to third parties except to provide or improve user-facing features, for security, or to comply with law. We don't allow humans to read it except with explicit consent, for security, by legal obligation, or for aggregated/anonymized analytics. Full disclosure on /privacy.

Sensitive fields including OAuth tokens, third-party API keys, payment-processor secrets, and integration credentials are encrypted at rest. Decryption happens in-memory at the time of use; we don't expose plaintext to logs, errors, or analytics.

TLS in transit on every public endpoint. AES-256 at rest for the primary database. Field-level encryption for sensitive columns inside the database. Backups encrypted at rest using rotating keys.

PII (names, emails, phones, addresses) is stored in tenant-scoped tables with field-level encryption on the most sensitive columns. We do not store payment-card numbers; payments are handled by Stripe directly via tokenized checkout, which keeps Hello Native out of PCI scope.

If we detect or are notified of a security incident affecting customer data, we triage immediately, notify affected customers within 72 hours, and publish a remediation post-mortem. Email security@hellonative.ai (forwards to founder) to report a suspected vulnerability or incident.

We are not currently certified under SOC 2 or ISO 27001. Our security controls map to the most common SOC 2 Type 1 control families (access, encryption, monitoring, change management). We are not a Business Associate under HIPAA and the platform should not be used to process Protected Health Information.

Yes. Email info@hellonative.ai with your organization name and we'll send our standard DPA, which incorporates Standard Contractual Clauses for international transfers.

Hello Native commits to providing a 60-day data export window in any change-of-control scenario. Tenant websites are real Next.js codebases that customers can self-host independently. The shutdown clause is in our Terms (§12).