Privacy policy
Draft under review. This page is waiting for legal review and is not in force yet. The highlighted words in brackets are still to be filled in.
This policy explains what SagePigeon collects, why, where it is kept, for how long, and who else handles it. It covers two groups of people:
- Customers: people who sign up for SagePigeon and the teammates and client logins they invite.
- People who fill in a form: visitors who send a form, or reply to an email, that a customer runs through SagePigeon.
SagePigeon is run by Code Sage Labs (Pvt) Ltd, [REGISTERED ADDRESS]. [COMPANY NUMBER]. Questions and requests go to hello@codesagelabs.com.
This policy covers the hosted service at https://sagepigeon.com. SagePigeon can also be self-hosted; a self-hosted copy is run by whoever installed it, and this policy does not apply to it.
Our role
For the account you create, your workspace settings and your billing details, Code Sage Labs (Pvt) Ltd is the controller. We decide how that data is used.
For what people type into your forms, the files they attach and the replies they send, you are the controller and SagePigeon is your processor. We handle that data only to provide the service to you and on your instructions, which are the settings you choose in your workspace. [DPA LINK]
If you filled in a form that uses SagePigeon, the business that runs the form decides what happens to your answers. Read their privacy policy, and send requests about your data to them first. We will help them answer.
What we collect about customers
Your account. Your email address and password when you sign up. The password goes to Amazon Cognito, which stores it; SagePigeon does not keep a copy. Cognito also emails you the confirmation and password-reset codes.
Your workspace. Its name and kind, the forms you build (including the recipient addresses and routing rules you enter), email templates and their version history, clients and groups, branding images, verified sending domains, API keys (we keep a hash, never the key itself) and connected integrations.
Your team. The email address and role of everyone you invite, and invitations, which expire after 14 days.
Activity. An activity log of changes made in the workspace, with who made each one and the IP address it came from. Workspace owners and administrators can read it.
Billing. When you upgrade, we create a Stripe customer with the owner's email address and the workspace name, and keep the Stripe customer and subscription ids, the plan, the billing period and whether a payment has failed. Your card details go straight to Stripe; we never see or store them. If tax collection is on, Stripe also collects your billing address and tax id.
Google Sheets. If you connect Google, we keep the access grant Google gives us, who connected it and when. See "Google user data" below.
Error reports from the dashboard. When the dashboard fails in your browser, it sends us the kind of error, the page as a pattern (such as /app/forms/:id), the release, and the error message with anything that looks like an email address, token, id or long number removed. Your browser removes those first, and our server removes them again before keeping the report. We use these reports only to fix the product.
What we collect about people who fill in a form
On a customer's behalf, SagePigeon stores:
- What was typed into the form. Up to 100 fields per submission.
- Files, when the customer's plan and form allow uploads.
- Technical details of the request. The IP address, the browser's user agent, the page the form was sent from, the country (worked out from the IP address by our network provider) and the browser's language.
- Replies. On Pro and Scale, when someone at the business answers from their own email, the reply text is kept on the submission and sent on to the person who filled in the form. The original email is held for 30 days, then deleted.
- What happened next. Who the submission was sent to, who on the team took it on, and the delivery log of every email and integration it triggered.
Submissions our spam checks catch are kept for 7 days so the customer can release a real one, then deleted. They are stored with the same technical details.
If a customer turns on Cloudflare Turnstile or Google reCAPTCHA for a form, the check runs in the visitor's browser, and SagePigeon sends the resulting token and the visitor's IP address to Cloudflare or Google to verify it.
To stop floods, SagePigeon counts submissions per IP address for each form, keyed on a hash of the address. Those counters expire on their own within 2 hours.
What we do not do
- We do not sell personal data, and we do not share it for advertising.
- The SagePigeon site and dashboard load no analytics, advertising or tracking scripts. Our fonts are served from our own domain, so opening a page makes no request to Google Fonts.
- SagePigeon does not set cookies. The dashboard keeps your sign-in tokens, the workspace you last opened and whether the sidebar is collapsed in your browser's local storage. Accepting an invitation briefly keeps its id in session storage. Signing out removes the tokens.
- People at SagePigeon who run the service use an operator console that shows workspace names, member email addresses, form names and counts. It cannot show what anyone submitted.
How we use it
- To run the service you asked for: receive submissions, send notifications, auto-replies and the email your code sends, deliver to the integrations you set up, and show you the results.
- To keep it working and safe: rate limits, spam checks, bounce and complaint handling, and the sending limits that protect every customer's email from one account's bad list.
- To bill you, through Stripe.
- To email account holders about their workspace. Some of these are scheduled, such as unanswered-request nudges, quiet-form warnings, the monthly report and failing-integration alerts; an owner or administrator can turn each of those off in Settings. Billing emails, invitations, confirmation codes and password resets are always sent.
Where the law asks for a legal basis: we rely on our contract with you for running the service and billing, on our legitimate interest in keeping the service secure and working for the error reports, logs and abuse limits, and on legal obligation for the billing records we must keep.
Where it is stored
SagePigeon runs on Amazon Web Services in the [AWS REGION] region:
- Accounts and passwords in Amazon Cognito.
- Workspaces, forms, submissions, the email log and the activity log in Amazon DynamoDB.
- Uploaded files in a private Amazon S3 bucket, and the original copies of incoming replies in another private bucket.
- Branding images (logos for your emails and hosted forms) in a separate S3 bucket that is public on purpose, because a logo has to load in a mail client long after the email was sent. Do not upload anything private as a branding image.
- The service runs on AWS Lambda, with a job queue in Amazon SQS that carries only ids. Form contents never go through the queue.
- Email is sent and received by Amazon SES, which also scans incoming replies for spam and viruses.
- Pages, the API and form endpoints are served through Amazon CloudFront, which has locations worldwide.
Data is encrypted in transit, since every address redirects to HTTPS, and encrypted at rest by AWS. Uploaded files are private; SagePigeon shows them to your team through links that expire.
Who else handles it
| Who | What for | When |
|---|---|---|
| Amazon Web Services | Hosting, storage, email, sign-in | Always |
| Stripe | Payments, invoices and tax | When a workspace upgrades |
| Writing rows to a spreadsheet you choose | Only when a workspace connects Google Sheets | |
| Google (reCAPTCHA) or Cloudflare (Turnstile) | Checking a form's captcha | Only on forms where the customer turns it on |
The places you send submissions to are your choice, and you are responsible for them: Slack, Microsoft Teams, Discord, Google Chat, Mattermost, Telegram, a webhook to your own server, or any service subscribed through a REST hook. When you add one, SagePigeon sends each submission there as you configured it, and that service's own terms apply. A chat message carries the submitted fields. A webhook carries the fields plus the technical details listed above (IP address, user agent, page and country) and any file references. A REST hook carries the fields, the IP address and the names of any files. A CSV export includes the IP address too.
We will disclose data when the law requires it, and we will tell the customer first unless the law forbids that.
International transfers
Your data is stored in [AWS REGION]. Stripe, Google and Cloudflare may process it in other countries, including the United States, and CloudFront serves it from the location nearest the visitor. Where data leaves the EU or UK, we rely on [TRANSFER MECHANISM].
How long we keep it
| Data | How long |
|---|---|
| Submissions | 30 days on Free, 1 year on Pro, 2 years on Scale, counted from when each arrived. A customer can set a form to remove submission contents sooner, as soon as the notification is delivered or after a set number of hours. |
| Spam | 7 days |
| Uploaded files | Deleted with their submission when someone deletes or erases it, or when the form removes contents. In any case, removed 400 days after upload. Files attached to a notification email as a link can be downloaded through that link for 7 days. |
| Original copies of incoming replies | 30 days |
| The email log (each message's addresses, subject, status and any reply text) | 400 days |
| Email API send records | 90 days |
| Activity log | 1 year |
| Suppression list (addresses that bounced or reported mail as spam) | Until a customer removes the address |
| Branding images | Until a customer deletes them |
| Dashboard error reports | 30 days |
| Form failure reports from browsers | 14 days |
| Service logs | 30 days |
| Account, workspace and billing records | While the account exists, and billing records for as long as tax law requires |
| Backups | DynamoDB keeps a continuous backup for up to 35 days, so deleted records can remain in backups for that long before they are gone for good |
Expired records are removed automatically, usually within a few days of their expiry date.
When a form removes contents, it removes what people typed, the search index built from it, file references and any estimate. It keeps that a submission arrived, when, which form, where it was routed and its delivery log, so the customer can still show an enquiry was received and answered. The technical details of the request and any replies stay until the submission itself expires.
Your choices and rights
If you are a customer, you can:
- see and change your forms, templates and team in the dashboard;
- export submissions as CSV on Pro and Scale, and export the email log as CSV on any plan;
- delete a single submission from the Inbox;
- find and delete everything a workspace holds about one email address, through the API (
GET /api/v1/privacy/search?email=andDELETE /api/v1/privacy/erase?email=), which you can use to answer requests from the people who fill in your forms; - remove a teammate, disconnect Google, delete API keys, sending domains, templates and branding images;
- cancel a paid plan from Billing.
There is no button yet to delete a whole workspace or your account. Email hello@codesagelabs.com from the account's address and we will delete it.
Wherever you are, you can ask us for a copy of the personal data we hold about you as a customer, or to correct or delete it, or to restrict or object to how we use it. Email hello@codesagelabs.com. If you filled in a form, ask the business that runs it; if you cannot reach them, write to us and we will pass your request on.
You can complain to [SUPERVISORY AUTHORITY].
[DPO]
[EU/UK REPRESENTATIVE]
Google user data
When a workspace administrator connects Google Sheets, SagePigeon asks Google for one permission: https://www.googleapis.com/auth/spreadsheets, which Google describes as seeing, editing, creating and deleting all of your Google Sheets spreadsheets. It does not include the rest of your Google Drive, your Gmail or your contacts.
With that permission, SagePigeon only:
- reads the title and tab names of the spreadsheet you paste into a form's settings, to check it exists and that you can edit it;
- reads the first row of the tab you chose, to line up columns;
- writes a header row if the tab is empty, then adds one row for each submission: the time it arrived, the form name, the submission id and the submitted fields.
SagePigeon does not open any other spreadsheet and does not read other rows.
We keep the grant Google returns (a refresh token) on your workspace, with who connected it and when. Choosing Disconnect Google on the Integrations page deletes that grant from SagePigeon and turns off every form's sync. To withdraw the permission at Google as well, remove SagePigeon from the third-party access page of your Google account.
SagePigeon'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. In particular, we use Google user data only to add your form submissions to the spreadsheet you chose. We do not use it for advertising, we do not sell it, we do not use it to train AI models, and no person at SagePigeon reads it unless you ask us to for support, it is needed for security, or the law requires it.
Rows written to your spreadsheet then live in your Google account under Google's terms. Deleting a submission in SagePigeon does not delete its row.
Children
SagePigeon is a tool for businesses. You must be at least [MINIMUM AGE] to create an account.
Changes
If we change this policy in a way that matters, we will email workspace owners at least [NOTICE PERIOD] days before the change takes effect and update the date at the top.
Effective [EFFECTIVE DATE].