Information the service handles
Account information includes your name, email address, password hash, authentication settings, and workspace membership. Your workspace may contain form configurations, submitted field values, attachments, processing records, and API credentials. Secrets needed by the application are stored in protected or encrypted form rather than displayed back in full.
Operational records include request times, account and workspace identifiers, authentication events, job activity, quota usage, and processing outcomes. Local abuse controls use keyed network identifiers. Hosting infrastructure may also record technical request information such as IP addresses and user agents.
Subscription billing
When you start a paid subscription, Stripe processes your billing contact, address, payment details, invoices and subscription. FormBastion stores Stripe customer and subscription identifiers, plan status, paid-period dates and processing records to manage your access. Your billing email can differ from your account email. We do not store card numbers or security codes. Stripe-generated payment records and any enabled receipts follow Stripe’s privacy policy.
We retain billing identifiers, complimentary plan grants and expiry dates, active-slot preferences, and entitlement history with your account for subscription administration and billing inquiries. Processed webhook metadata is removed after 90 days; unresolved processing records remain for review. Contact support about billing-data requests. Invoice and payment records held by Stripe are separate from form-submission retention.
Why this information is used
We use this information to provide accounts and workspaces, accept and store submissions, execute the actions you configure, apply usage limits, troubleshoot faults, handle support, and protect the service from misuse.
Form owners and people submitting forms
A workspace owner decides which information their forms request and how it is used. The owner is responsible for providing appropriate notices and obtaining any required permissions. If you submitted a form on another website, contact that website’s owner first for questions about your submission or its use.
Where information goes
Account and submission data are stored using the platform’s hosting and database environment. Attachments use private storage managed by the application. A configured webhook sends the relevant submission data to the destination selected by your workspace. Those destinations have their own privacy practices.
Form Bastion does not include advertising trackers.
Submitter confirmations and branding
When a form owner enables an autoresponder, we use its mapped email field and optional first name to send a receipt confirmation through our email relay. The email contains the owner’s configured message and branding; it does not quote the submitted message or attach files. A business name and logo do not indicate that FormBastion verified or endorsed the business. Uploaded branding images are public and retained for earlier emails. Confirmation delivery records follow submission retention; test-email records expire after 30 days. Email copies held by recipients and email providers are outside our deletion controls.
We keep keyed hashes of recipient addresses for rate limiting and stopped-confirmation preferences. Inactive unsuppressed rate records expire after 90 days; suppression hashes remain to honor the preference. The stop link requires confirmation and applies to submitter confirmations across FormBastion. It does not disable account-security messages or separately authorized team notifications.
Submission email notifications
If a workspace enables notifications, selected field values and response metadata are sent through our Google Workspace SMTP relay to recipients who explicitly confirmed permission. Recipient addresses, consent state, and delivery outcomes are stored separately from customer account identities. Emails include a stop-notifications link and no attachments. Copies held by recipients and email providers are outside the platform’s submission-deletion controls.
Consent links expire after 24 hours. Revoked or expired recipient records are removed after 90 days once no retained delivery refers to them. Delivery records expire with their submission; aggregate monthly email counts remain for usage accounting. FormBastion records relay acceptance, not inbox placement or reading. Learn about notification controls.
Contacting our team
When you contact us, we store your name, email address, selected topic, message, and any reference you provide in a separate support inbox. We use these details to respond and send an internal notification to our support email address. Please do not include passwords, API keys, recovery codes, or private submission contents.
Our contact form uses Enhanced protection with signed, expiring, single-use tokens, a short timing check, and a randomized honeypot. Necessary session cookies bind the form to your visit; short-lived keyed records prevent token replay. These checks run on our server and also work when JavaScript is disabled.
The platform copy is scheduled for deletion 90 days after receipt. Removal runs during scheduled maintenance. Copies and correspondence in our support email inbox are managed separately and may remain while needed to resolve your enquiry or an account or security matter. Contact support to request deletion assistance.
Retention and deletion
Submissions have a retention expiry based on the workspace’s applicable plan. Scheduled maintenance removes expired submissions and associated files and processing records. The actual removal time depends on maintenance execution. Workspace users with sufficient permission can delete submissions sooner.
Account and operational records may remain while they are needed to operate the service, resolve account or security matters, or meet applicable obligations. You can request account information or deletion by contacting support.
Cookies and local storage
Form Bastion uses necessary session cookies to keep you signed in and protect the public contact form from forged requests. Authentication and request-protection cookies support the service’s security. On public pages, your existing customer sign-in can be recognized to show your first name and links back to your account and workspace; this does not create an additional cookie. The application does not store submitted form contents in browser local storage as part of its standard workflow.
Your choices and requests
Manage your profile, authentication settings, and workspace data from your account. To request access, correction, export, or deletion assistance, email [email protected]. We may need to verify that you are entitled to act on the relevant account or data.
Changes to this notice
We will update this page when the service’s information handling changes. Material product changes are recorded in the public changelog.
Optional browser protection
When a website installs our optional script, it requests short-lived form protection tokens without sending the visitor’s field values. On submission, it sends the form fields and any attachments to the configured FormBastion endpoint. The script uses no analytics, cookies, or local storage. Tokens and retry state remain in page memory. Server protection stores keyed hashes for rate, email-frequency, replay, and matching-content checks; these records expire with their protection windows and are removed by maintenance.