Legal
Privacy Policy
This Privacy Policy explains how Askery, Inc. ("Askery", "we", "us") handles personal data when you visit our website, create an account, build forms, or submit a response to a form built on Askery. It covers what we collect, why, the legal bases we rely on, who we share it with, how long we keep it, how we protect it, and the rights you have. Please read it together with our Terms of Service, Data Processing Addendum and Cookie Policy.
Last updated: 19 May 2026
About this document
This document is published in good faith as a clear, industry-standard template so that customers, respondents and prospective customers can understand how Askery approaches this topic. It is provided for transparency only and is NOT legal advice, and it does not create an attorney-client relationship. Laws differ by jurisdiction and by how you use the service. Askery, Inc. and its customers should each have qualified counsel review and, where appropriate, adapt this document before relying on it. If a separately negotiated and signed agreement exists between you and Askery, Inc., that agreement controls to the extent it conflicts with this page. We will update this page as the product and applicable law evolve; material changes are described in the "Changes to this policy" section below.
Who we are and our roles
Askery, Inc. operates the Askery form-building platform. For data about our own account holders, billing contacts and website visitors, we act as a data "controller" (we decide why and how it is processed). For personal data that a customer's respondents submit into that customer's forms ("Respondent Data"), the customer is the controller and we act only as a "processor" acting on the customer's documented instructions. The terms governing that processing are set out in our Data Processing Addendum. This Privacy Policy describes our practices as a controller and explains, for transparency, how Respondent Data is handled as a processor.
Personal data we collect
Account and identity data: name, email address, password (stored only as a salted hash), workspace and organization details, and role/membership within a workspace. Billing data: plan, billing contact, and limited payment metadata - full card numbers are handled by our payment processor and are never stored on our servers. Usage and device data: log entries, IP address, browser and device type, pages viewed, feature usage, and diagnostic events used to operate and secure the service. Support data: the content of messages you send us and related correspondence. Form definitions: the questions, options, logic and settings you create (these are your content, not personal data about you, though they may describe data you intend to collect). Respondent Data: whatever a customer chooses to ask in their forms - which may include names, contact details, free-text answers, and any other information the customer's form requests - processed strictly on that customer's behalf.
How we use personal data
We use personal data to: create and administer accounts and workspaces; provide, maintain, secure and improve the service; authenticate users and enforce tenant isolation; process payments and send service and billing communications; provide customer support; detect, prevent and investigate abuse, fraud, spam and security incidents; comply with legal obligations; and, where permitted, send product updates you can opt out of. We do not sell personal data, we do not "share" it for cross-context behavioral advertising as those terms are defined under California law, and we do not use Respondent Data for our own purposes, to build advertising profiles, or to train machine-learning models, except strictly as needed to deliver the feature the customer requested.
Legal bases for processing (EEA/UK)
Where the GDPR or UK GDPR applies and we act as a controller, we rely on: performance of a contract (to provide the service you signed up for); legitimate interests (to secure, operate, debug and improve the service, prevent abuse, and run our business, balanced against your rights); consent (for non-essential cookies and optional marketing, which you may withdraw at any time); and compliance with a legal obligation (for tax, accounting and lawful requests). For Respondent Data we process as a processor, the relevant lawful basis is determined by the customer acting as controller, not by us.
Sub-processors
We rely on a limited set of vetted sub-processors to deliver the service. By category these are: managed Postgres + authentication infrastructure (the primary store for accounts, form definitions and responses; Supabase, Singapore); application hosting + CDN + container registry + static-asset blob storage (Microsoft Azure - AKS in Pune for compute, Front Door / Blob globally for delivery); transactional email delivery (Brevo, EU); hosted LLM API for AI-powered features such as form generation, AI editing, Form Intelligence and AI insights, plus optional per-workspace Google Workspace integrations (Sheets sync, Calendar booking, Meet links - engaged only when an owner explicitly connects their Google account), both provided by Google (Gemini API + Workspace APIs, governed by Google's terms); payment processing for paid subscriptions (Razorpay, India - billing details only, never respondent answers); and Cloudflare for DNS plus the optional Turnstile anti-abuse challenge a form owner can enable (rolling out). Each sub-processor is bound by written terms requiring confidentiality and appropriate security, and is engaged only to the extent necessary. A current, itemized sub-processor list - including entity names, processing purpose and hosting region - is published at /legal/subprocessors; customers may subscribe to advance notice of additions or replacements as described in the Data Processing Addendum, and may object to a new sub-processor on reasonable data-protection grounds. NOTE: when an owner enables Form Intelligence or AI insights on a form, the answers submitted to that form (or their aggregated content) are sent to our LLM sub-processor for evaluation as part of producing the personalised result page or insight narrative.
International data transfers
Askery may process and store data in data centers located in one or more countries. Where personal data is transferred out of the EEA, the UK or Switzerland to a country without an adequacy decision, we put appropriate safeguards in place - primarily the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum where applicable) - together with supplementary technical and organizational measures such as encryption in transit and strict access controls. Customers who require a specific hosting region or data-residency commitment should contact us; regional residency is part of our published roadmap and is designed into the data model.
Data retention
We retain account, billing and form-definition data for as long as your account is active and as needed to provide the service. Respondent Data is retained according to the customer's configuration and instructions; customers control deletion and export of their responses. When an account is closed, or upon a verified deletion request, we delete or irreversibly anonymize the associated personal data within a commercially reasonable period (target: within 30 days), except where we are required to retain certain records to comply with legal, tax, accounting or dispute-resolution obligations, or where data persists in routine encrypted backups that age out on a defined rotation schedule and are not used for any other purpose.
How we protect data
We apply layered technical and organizational measures, including: encryption of traffic in transit (TLS); tenant isolation enforced at the database layer through Postgres row-level security rather than only in application code; a single audited, security-definer write path for public form submissions and no anonymous insert access; form passwords stored as salted bcrypt hashes in an isolated table that no API can read (user account passwords are handled by our authentication provider using current best-practice hashing); least-privilege access with the service-role key confined to the server; per-IP and per-form rate limiting on public submission endpoints, plus a built-in honeypot field enforced on both the client and the database write path; optional Cloudflare Turnstile challenges on forms the customer has flagged as abuse-prone; and routine managed backups. No system is perfectly secure, but security is treated as an architectural property of the platform. See our Security page for a fuller description.
Your privacy rights
Subject to applicable law, you may have the right to: access the personal data we hold about you; correct inaccurate data; delete data; restrict or object to certain processing; obtain a portable copy; and withdraw consent where processing relies on it. California residents additionally have the right to know, delete, correct, and to opt out of "sale"/"share" (we do not sell or share personal data for cross-context behavioral advertising) and to non-discrimination for exercising these rights. EEA/UK residents may also lodge a complaint with their supervisory authority. If your request concerns Respondent Data, the customer who operates the form is the controller - we will refer you to, or assist, that customer as appropriate.
How to exercise your rights
To make a request, email support@askery.app from the address associated with your account, or use the export and deletion controls in your account where available. We will verify your identity before acting, respond within the timeframe required by applicable law (generally within 30 days, extendable where the law permits with notice), and will not charge a fee for reasonable requests. If we cannot fully honor a request, we will explain why. You may authorize an agent to act on your behalf, subject to verification.
Children's data
Askery is a business tool and is not directed to children. Accounts may not be created by anyone under the age of 16 (or the higher age required in their jurisdiction). We do not knowingly collect personal data directly from children as a controller. Customers are responsible for their own forms; if a customer chooses to collect data from minors through a form, that customer is the controller and is responsible for obtaining any required parental or guardian consent and complying with applicable child-protection laws. If we learn we have inadvertently collected a child's personal data as a controller, we will delete it.
Third-party links and integrations
The website and product may link to or integrate with third-party services (for example, webhook destinations or integrations a customer configures). Those third parties operate under their own privacy policies, and we are not responsible for their practices. Customers are responsible for configuring integrations lawfully and for the destinations to which they send data.
Shopify app
Askery publishes a Shopify app on the Shopify App Store. When a merchant installs the app on their Shopify store, Shopify shares with us a small set of merchant-account fields needed to power the integration: the store's myshopify.com domain, the store name, the store contact email, the store country code, the store's Shopify plan name, the OAuth access token Shopify issues for our app, and the scopes the merchant granted. We store these in encrypted form in our managed Postgres database to render the embedded admin page, identify the store across requests, and respond to webhook events Shopify sends us. We do NOT request or store Shopify customer personal data (name, email, address, payment details, order history) in v1, and the app's storefront block renders Askery forms via an iframe loaded from cdn.askery.app - Shopify shoppers' responses are submitted directly to Askery and are treated as Respondent Data under this policy (the merchant is the controller; we are the processor). When a merchant uninstalls the app we receive Shopify's app/uninstalled webhook and mark the installation as revoked; 48 hours later Shopify fires the shop/redact compliance webhook and we permanently delete the installation record and any associated metadata. We also implement Shopify's customers/data_request and customers/redact compliance webhooks; because we do not store Shopify customer personal data, those handlers are audit-only.
Changes to this policy
We may update this Privacy Policy to reflect changes to the product, our practices, or the law. When we make material changes we will update the "Last updated" date and, where appropriate, provide additional notice (for example, by email or an in-product notice). Your continued use of the service after an update takes effect constitutes acceptance of the revised policy to the extent permitted by law.
Contact us
For privacy questions, requests, or to reach our privacy contact, email support@askery.app. For Respondent Data questions about a specific form, please also contact the organization that operates that form, since they are the controller of that data.
Questions about this document? Contact support@askery.app.