Privacy Policy
Effective 2026-10-02
How Stagware collects, uses, stores, and shares information when you use Picket, including the Gmail data you choose to connect.
Summary
- Picket is an email service. If you choose to connect a Google account, we read your Gmail messages so they appear in a Picket mailbox, and we send mail you compose from that Gmail address.
- We access Google data only after you consent, only the data listed below, and only to provide those features.
- We do not sell your data, show advertising, or use Google data to train AI or machine-learning models.
- You can disconnect at any time, and you can ask us to delete your data.
Who we are
Picket is a multi-tenant email service operated by Stagware ("Stagware", "we", "us") at https://mail.henriksen.dev. It lets teams receive, read, and send email for their own domains, and optionally connect an existing Google account.
In this policy, "you" means a person who uses Picket. If you use Picket through a workspace run by your organization, your organization's administrators also control that workspace's mailboxes and settings.
Information we collect
- Account information: your email address, your name if you provide one, and your password, which is stored only as a salted hash and can never be read back.
- Mail content: the messages, attachments, drafts, labels, and contacts in the mailboxes you use, including the headers, subjects, addresses, and bodies of mail you send and receive.
- Workspace information: your organization, its members and roles, its domains, mailboxes, routing rules, and the settings you configure.
- Security and session records: your sign-in sessions and security events, such as when you signed in or changed a security setting.
- Connected-account data: if you connect a Google account, the data described in the Google user data section below.
- Operational logs: our hosting platform retains service logs. They can include the recipient address of an inbound message that could not be delivered, storage object keys, queue names, and error classifications. They do not include message bodies, subjects, passwords, or access tokens.
Google user data and Gmail access
Connecting a Google account is optional and starts only when you choose it. Picket asks Google for the following permissions and uses each one only for the purpose shown:
- openid — confirms which Google account you are connecting.
- email — reads the email address of that Google account so it can be shown and matched to the connection.
- https://www.googleapis.com/auth/gmail.readonly — reads messages so copies of your Gmail mail can be imported into your Picket mailbox.
- https://www.googleapis.com/auth/gmail.send — sends messages that you choose to send from your Gmail address through Picket.
Google data we access
If you connect a Google account, Picket accesses only the following Google user data:
- The email address of your Google account, to show it and match it to the connection.
- Message content: for each message we import, its sender, recipients, subject, date, headers, body, and attachments, received from Google as the complete raw message.
- Message metadata: message and thread identifiers, labels (used to place a message in Inbox, Sent, or archive), and the mailbox history position that lets us fetch only what has changed since the last sync.
- Messages you send: the message you compose in Picket, which we pass to Google to send from your Gmail address.
- We do not access your Google contacts, calendar, Drive files, photos, or any other Google service.
What we do with Google data
Picket's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Import: we copy mail from your Gmail account into the Picket mailbox you chose. You select whether to import only new mail or also the last 30 days, and new mail keeps syncing until you disconnect or pause the connection.
- Send: when you compose a message from your connected Gmail address, we send it through Google on your behalf.
- No changes to Gmail: Picket never asks for permission to modify, label, move, or delete anything in your Gmail account.
- Storage: your Google refresh credential is encrypted at rest and is never sent to your browser. Imported messages are stored like the rest of your Picket mail. If you turn on "Retain original copies", we also keep an exact copy of each newly imported message and a checksum of it.
- Who can read imported mail: everyone with read access to the Picket mailbox you connect can read the mail imported into it. We show this before you connect.
- Human access: Stagware does not read your Google data. We access it only if you ask us to help with a specific problem, where needed to investigate abuse or a security incident, or where the law requires it.
- AI: we do not use Google user data to develop, improve, or train generalized AI or machine-learning models.
- Prohibited content: we do not use Google APIs, or data received from them, to create, store, or distribute non-consensual intimate imagery, including AI-generated imagery.
- Advertising and sale: we do not use Google user data for advertising, and we never sell it.
- Third-party clients you authorize: if you choose to connect an assistant or another client to your Picket mailbox (for example through an API key, the MCP integration, or the IMAP and SMTP bridge), that client can read the mail in that mailbox, including imported Gmail mail, to the extent you authorize it.
Optional AI mail classification
With your explicit consent, enabled Jev questions send selected mail to TypeSafe AI for classification. We send the sender, recipient, subject, and up to 8,000 characters of message text. This can include imported Gmail mail. We do not send attachments, HTML, or full threads. Local tagging rules run in Picket without sending mail to TypeSafe.
You can disable automatic classification and cancel pending classification jobs in Mail insights. Your labels and corrections remain in Picket. TypeSafe's published policy states that inputs are not used to train or fine-tune models; its retention and processing terms apply to submitted content. We do not promise zero retention by the provider.
How we use information
We do not sell your information, we do not show advertising, and we do not build advertising profiles.
- To provide Picket: receive, store, display, search, and send your mail and keep your workspace working.
- To keep the service secure: authenticate you, prevent abuse, and investigate incidents.
- To support you: answer questions you send us and diagnose problems you report.
- To meet legal obligations.
Retention and deletion
- Your mail and workspace data are kept until you or your organization's administrators delete them or until the account is closed.
- Raw copies of inbound messages held only for processing are deleted after processing succeeds.
- Disconnect: you can disconnect a connected Google account at any time from Settings, External accounts. Disconnecting stops all access immediately and asks Google to revoke the credential. It never deletes anything in Gmail. Mail already imported stays in your Picket mailbox until it is deleted.
- You can also remove Picket's access from the Google side at any time.
- To have your account and its data deleted, email us. We will confirm the request and complete deletion within 30 days. Copies in backups can persist for a limited period afterward.
Security
Traffic to Picket uses HTTPS. Passwords are stored as salted hashes, connected-account credentials are encrypted at rest, and every mailbox, message, and domain is isolated by organization and by your permissions. No system is perfectly secure, so we cannot guarantee absolute security, but we design Picket to limit what any one failure could expose.
Your choices and rights
You can view and edit most of your information in Picket. Depending on where you live, you may also have the right to access, correct, export, or delete your personal information, to object to or restrict certain processing, and to lodge a complaint with a data protection authority. To use any of these rights, email us.
Children
Picket is not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child has given us information, email us and we will delete it.
Changes to this policy
We may update this policy. The effective date above shows when it last changed. If a change materially affects how we handle your information, we will notify you in the service or by email before it takes effect.
Contact
Stagware, operator of Picket. Questions, requests, and complaints about privacy: