1Overview
Deooch Forms is a form builder. You create forms, publish them at a public link, and collect responses in one place. This policy covers the app at forms.deooch.com and the MCP server at forms.deooch.com/api/mcp.
Two different relationships run through this service, and the difference matters for your rights.
- Your account data. We decide how it is handled, so we are the controller. This is the information you give us to have an account with us at all.
- Your respondents’ answers. You decide what to ask and why, so you are the controller and we are your processor. We hold that data on your behalf and act on your instructions.
We do not sell personal data. We do not use your forms, your responses, or your connected account data to train AI models.
2Information we collect
We collect only what the product needs to work. Nothing below is bought from a data broker or scraped from anywhere else.
| Category | What it includes | Why we have it |
|---|---|---|
| Account data | Your email address, name, workspace role, and plan. | You give it to us at sign up. It identifies your account and controls what you can reach. |
| Content you create | Form titles, descriptions, fields, settings, and version history. | It is the product. Version history lets you recover an earlier draft. |
| Form responses | Whatever your respondents type into your public forms, plus the time of submission, the submitting IP address, and the browser user agent. | You asked for the answers. The IP address and user agent support spam prevention and, on forms with a signature field, evidence that a signature was actually made. |
| Payment records | For paid accounts: amount, currency, date, status, plan, and the Stripe reference. | So you can see your billing history, and because tax law requires us to keep records of what we were paid. |
| Connected account data | A token for each service you connect, such as Google or Slack, plus the email address of the connected account. | It is what lets a connection keep working without asking you to sign in again. |
| Usage analytics | Aggregate, cookieless page metrics from Vercel Analytics. | To see which pages people use. There is no cross site tracking and no advertising identifier. |
We never receive or store your card number. Card details go directly to Stripe. See Payments for the detail.
3How we use information
We use the information above for these purposes and no others.
- To run the service. Building, publishing, and serving your forms, recording responses, and showing them back to you.
- To keep it working. Diagnosing errors, preventing abuse and spam, and enforcing plan limits.
- To communicate with you. Notifying you of new responses, answering your support requests, and telling you about changes that affect your account.
- To take payment. Processing subscriptions, issuing receipts, and meeting our tax and accounting obligations.
- To do what you asked. Delivering a response to a service you connected yourself, such as writing a row to your spreadsheet or posting a message to your Slack channel.
If you are in the EEA or the UK, our legal bases are: performance of our contract with you, our legitimate interest in keeping the service secure and usable, your consent for anything you switch on yourself, and compliance with a legal obligation for financial records.
4Google account data
Connecting a Google account is optional and switched on per account. Nothing in this section applies until you open Settings, then Integrations, press Connect, and grant consent on Google’s own screen.
We request the narrowest permission that can do each job. Where a broader and easier permission exists, we have deliberately not asked for it.
| Permission | What it gives us | What we do with it |
|---|---|---|
| drive.file | Access limited to spreadsheets this app itself created for you. We cannot see, open, or list anything else in your Drive. | Create the response spreadsheet and append a row as each submission arrives. |
| calendar.freebusy | Busy and free time blocks on your primary calendar. It carries no event titles, no attendees, no descriptions, and no locations, and we never receive them. | Hide appointment slots for times you are already booked. |
| calendar.events | The ability to write events to your primary calendar. | Create one event when someone books an appointment through your form. We do not read, edit, or delete your existing events. |
| openid, email | The email address of the Google account you connected. | Show you which account is connected on the settings page. |
What we store is a single refresh token for your account. We use it only to obtain access tokens that expire after one hour. We do not copy your Drive files, your calendar, or your events into our database. The data moves in one direction, from your form into Google.
Deooch Forms’ use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We do not share Google user data with anyone. We do not sell it, we do not use it for advertising, and we do not use it to train AI models, including the assistant integrations described in the next section.
You can disconnect at any time from Settings, then Integrations, or revoke access directly at myaccount.google.com/permissions. Either route takes effect immediately: the refresh token stops working, we mark the connection revoked, and syncing stops. Spreadsheets and calendar events already created stay in your Google account, and they are yours to keep or delete.
5AI assistants and MCP
You can connect an AI assistant such as Claude or ChatGPT, or any client that speaks the Model Context Protocol. The assistant signs in over OAuth and acts on your behalf with a scoped access token. It can read and write only the forms and submissions your own account can already reach.
Once data leaves our server in response to the assistant’s request, it is handled under that vendor’s own privacy policy. We never send your data to a model provider ourselves, and we do not use it to train any model.
You can revoke a connection at any time from your client’s connector settings or from Settings, then Connected apps. Revoking invalidates the token immediately.
6Payments
Billing runs on Stripe. Every card entry, whether at checkout or when you replace a card in Settings, then Billing, happens inside a field that Stripe serves and controls. Card data never touches our servers or our database.
What we keep is a ledger of your own payments: amount, currency, status, date, the Stripe identifier, and which plan it bought. It exists so you can see your history and download receipts without leaving the app, and because we are legally required to keep records of what we were paid. We do not store your card number, expiry date, billing address, or any card fingerprint.
If you collect payments from your own respondents, that runs through Stripe Connect against yourStripe account. We record only that a submission was paid, the amount, and Stripe’s reference for it. Your respondents’ card details are between them and Stripe, and are never visible to us or to you through this service.
7How we share information
We share information with the service providers we need to operate, and with nobody else. Each one is bound by contract to use the data only to provide their service to us.
| Provider | What they do for us |
|---|---|
| Supabase | Database and authentication. |
| Vercel | Hosting and cookieless analytics. |
| Stripe | Payments, card processing, tax calculation, and invoicing. |
| Resend | Notification and transactional email. |
Beyond these, we share data in only two situations: when a service you connected yourself asks for it, such as your own Google spreadsheet or Slack workspace, and when the law requires it, such as a valid court order. If we are ever compelled to hand over your data, we will tell you unless we are legally barred from doing so.
If Deooch Forms is ever acquired or merged, your data may transfer to the new owner. We will give you notice before that happens and before any change to this policy takes effect.
8How long we keep information
- Forms and submissions. Kept until you delete them. Deleted forms are soft deleted first, then purged within 30 days.
- Account data. Removed within 30 days of you closing your account, along with all associated forms and submissions.
- Connection tokens. Invalidated the moment you disconnect, and deleted with your account.
- Payment records. Retained for as long as tax and accounting law requires, which is several years. See the note below.
Payment records are the one exception to deletion. Because the law requires us to keep them, a request to close your account does not erase them. Instead we sever the link between the record and you. What remains is an anonymous ledger line, an amount, a date, and a Stripe reference, that can no longer be traced back to a person. This is the approach Article 17(3)(b) of the GDPR contemplates when erasure meets a legal retention duty.
9Security
Traffic is encrypted in transit with TLS, and data is encrypted at rest. Access is scoped per workspace and enforced at the database layer, so members of one workspace cannot read another workspace’s data. Tokens for connected services are stored server side and are never sent to a browser.
No system is perfectly secure. If a breach affects your data, you will hear about it from us promptly, and within the deadlines the law sets where they apply.
10Your rights and choices
You can access, correct, export, or delete your data at any time. Most of it you can handle yourself from the dashboard, and we will do the rest if you email us.
- If you are in the EEA or the UK. The GDPR rights of access, rectification, erasure, restriction, portability, and objection apply, as does the right to complain to your local supervisory authority.
- If you are in California. The CCPA rights to know, delete, correct, and opt out of sale apply. We do not sell data, so there is nothing to opt out of, and we will never discriminate against you for exercising a right.
- If you are a respondent, not an account holder. The form owner is the controller of your answers. Contact them first. If you cannot reach them, write to us and we will help.
We answer every request within one business day and complete it within 30 days. We do not charge for this.
11International transfers
We are based in Europe, and our providers operate in Europe and the United States. Where data moves outside the EEA or the UK, it is covered by the European Commission’s Standard Contractual Clauses, or by an adequacy decision, or by the EU US Data Privacy Framework, depending on the provider. You can ask us which applies to a specific provider and we will tell you.
12Children
Deooch Forms is not directed at children under 13, and we do not knowingly collect their personal data. If you believe a child has given us data, write to us and we will delete it. If you use a form to collect data from children, that is your responsibility as the controller, and you are required to have the consent the law in your country demands.
13Changes to this policy
If we change this policy in a way that materially affects you, we will update the date at the top of this page and email every account holder before the change takes effect. Smaller corrections, such as fixing a typo or naming a provider more precisely, are made without notice, but the updated date always tells you when the text last changed.
14Contact us
For privacy questions, data requests, or anything else in this policy, write to us. We reply within one business day.
See also our Terms of Service.