Security & trust

Your data, protected by design

Firma deploys email signatures across your whole team, so access and data protection matter. Here is how we keep your data safe across Google Workspace and Microsoft 365.

No access to your email content

Firma manages signatures, not mail. On Google Workspace it holds no permission to read your emails, only to read directory profile data for personalization and to set Gmail signatures. On Microsoft 365, the Outlook add-in runs only to insert your signature as you compose. You approve access at install and can revoke it anytime from your admin console.

Encrypted in transit and at rest

All traffic to and from Firma is encrypted with TLS (HTTPS), and the data we store is encrypted at rest.

GDPR-compliant

Firma is built to comply with the GDPR. For customer data, we act as a data processor and handle it only to provide the service.

We never sell your data

We do not sell your personal information, and we never scan, store, or use the contents of your mailbox for advertising.

You stay in control

Admins control who has access. You can export or delete your data on request, and uninstalling Firma revokes its access to your workspace.

Managed infrastructure

Firma runs on established, managed cloud infrastructure with provider-level security, monitoring, and backups.

How Firma connects to your workspace

An admin approves access at install, and can revoke it at any time.

Google Workspace

Installed from the Google Workspace Marketplace. Firma uses OAuth permissions for your directory profile data (to personalize signatures) and Gmail signature settings (to apply them). It has no permission to read your email. Uninstalling from the admin console revokes access immediately.

Microsoft 365

An admin deploys the Firma Outlook add-in from the Microsoft 365 admin center, scoped to the users or groups you choose. Signatures apply in Outlook on desktop, web, and mobile. You remove access by removing the add-in from the admin center.

The exact Gmail API scopes Firma uses

On Google Workspace, Firma runs as a service account with domain-wide delegation, so the Admin console shows these scopes when you install. If any signature tool asks for a scope that reads your mail, ask why.

Scope What Google lets it do Why a signature tool uses it
gmail.settings.basic Change a user's Gmail settings, including the signature on each send-as address Writes the signature itself
gmail.settings.sharing Manage sensitive settings such as send-as aliases Google requires it to register an alias address before a signature can be set on it
admin.directory.user.readonly (and org unit, domain, schema read scopes) Read names, titles, phone numbers, departments and organizational units Fills each person's details and powers per-team or per-OU rules
gmail.readonly, gmail.modify, mail.google.com Read or change the messages in a mailbox Not needed for signatures. Firma requests none of these

Checked against Google's documentation in October 2026: sendAs.patch, sendAs.create (only available to service accounts with domain-wide delegation).

Data and privacy

  • We store the signature templates you create and the directory fields used to personalize them, plus your account details.
  • We do not sell your personal information, and we never scan, store, or use your email content for advertising.
  • You can export or delete your data on request, and uninstalling Firma revokes its access.

For the full detail, including the data we collect, retention periods, and our sub-processors, see our Privacy Policy, DPA and Sub-processors.

Report a security issue

Found something that looks like a vulnerability? Email hello@tryfirma.com with the details and we will respond promptly. We appreciate responsible disclosure.

Security FAQ

Deploy signatures your team and IT can trust

Free for up to 2 users. No credit card required.