🧪 PRE — staging environment, nothing here is real (no real payments, no real customer data)

Security & privacy

Wattprint is a multi-tenant SaaS hosted by us. Tenant isolation is enforced at the application layer: every request is scoped to the authenticated organization, and all data access is authorized against that organization.

What we store

  • AI usage metadata: model, provider, tokens, latency, date, team/application tag.
  • The people directory you import: email, name, department, manager, country, cost center.
  • AI licence assignments and their last activity.
  • Calculated footprint (energy, CO₂e, water) and the calculation engine applied.
  • Audit logs of sensitive actions (who did what, and when).

What we do NOT store

  • We do not store prompts. We read counts and costs from your providers; the content of your requests never reaches us.
  • We do not store model responses.
  • We do not store documents or files from your Microsoft 365 — only directory, licences and usage reports.

Credentials & tokens

  • Your provider API keys (OpenAI, Anthropic…) are encrypted at rest with Fernet (AES-128-CBC + HMAC-SHA256), using a key derived from the server secret that never leaves the server, and are never displayed again once saved.
  • Microsoft OAuth tokens are encrypted with the same scheme.
  • You can rotate or revoke connector credentials at any time from Settings.

Microsoft Graph permissions

The connector uses read-only permissions under least privilege: read users and directory, read licences, read usage reports. Each permission is explained in the connection wizard before admin consent, and you can disconnect the tenant and delete imported data at any time.

Authentication & access

  • Passwords hashed with scrypt and salt; signed sessions with HttpOnly/SameSite cookies.
  • Rate limiting on login and registration.
  • Per-organization roles: Owner, Admin, Analyst, Viewer, Developer.
  • Microsoft sign-in (SSO) available to every customer, configured per organization; password login uses scrypt hashing.

Application hardening

  • Forced HTTPS (Let’s Encrypt) with HSTS in production; encrypted transport end to end.
  • Security headers on every response: Content-Security-Policy, anti-clickjacking (X-Frame-Options / frame-ancestors), nosniff and a strict referrer policy.
  • CSRF protection by origin verification, combined with signed SameSite session cookies.
  • Rate limiting on sign-in and sign-up, and an audit log of sensitive actions (plan changes, credentials, syncs, admin access).
  • Tenant isolation: every request is scoped to the authenticated organization and every data access is authorized against it, which is designed to prevent cross-organization access. The platform backoffice is a separate surface, restricted to a single configured administrator address, and its access is logged.

Your data, your control

GDPR-ready principles: data minimization (metadata only by default), right to erasure (per-organization deletion on request), documented methodology. Because we process your employees' data as a processor, a <strong>DPA is available to any customer on request</strong> — not just large accounts. Custom security reviews and questionnaires are handled for contracted accounts. We do not claim certifications (SOC 2, ISO 27001) we do not yet hold.

Security or privacy questions? security@wattprint.com