Effective October 17, 2026 (Asia/Shanghai).

Privacy Policy

This policy explains how the operator of FormPostbox (“we”) handles information when you visit formpostbox.com, use an account, or submit information through a website form connected to FormPostbox. For privacy questions, contact support@formpostbox.com.

Account information can include your name, email address, password hash, verification status, session information, and account access and closure records. Workspace information includes website origins, form settings, notification recipients, Developer API key metadata, and optional website-form Turnstile settings.

Form submissions include the fields and values sent through a connected website, the associated form and workspace, receipt time, and retention and review information. The website owner decides what its forms ask for. Avoid sending passwords, payment-card details, government identifiers, health information, or other highly sensitive information through ordinary contact forms.

Operational information includes request and security metadata, rate-limit information, notification delivery events, deletion records, and audit records. Billing information includes checkout, subscription and transaction references, selected plans, amounts, currency, status, and billing periods. Payment information for checkout is entered on Waffo’s hosted page. FormPostbox billing records do not contain full payment-card numbers or security codes; information you place in a connected form remains submission content.

We use information to operate accounts and connected forms, display and export retained submissions, send requested notifications and account messages, administer subscriptions, prevent abuse, investigate failures, maintain security, and respond to support requests and applicable legal obligations. New accounts must verify their email with FormPostbox before full workspace access.

Website owners are responsible for informing their visitors about their forms and for having authority to collect the information they request. If you submitted a form on someone else’s website, contact that website owner first about access, correction, or deletion of your submission. You can also contact us for help identifying the appropriate owner.

These services process information to operate FormPostbox or when you or a website owner chooses to use them:

ServiceInformation and purpose
CloudflareHosts the application and stores account, workspace, form, submission, billing-reference, security, and operational information in D1. Cloudflare Queues carries task identifiers for notification and billing-webhook work; Cron starts scheduled maintenance. Cloudflare security services protect requests.
ResendReceives transactional email addresses, message content, delivery instructions, and delivery events. A full submission notification can include submitted fields. A reminder notification contains form and site details and an authenticated inbox link, without submitted fields or a Reply-To address.
Cloudflare Turnstile (account access)When configured, processes one-time verification tokens and browser/request signals for account sign-up and sign-in. The public site key may be returned to the browser; the verification secret stays server-side and is not returned.
Cloudflare Turnstile (optional website form protection)When a website owner enables it, processes verification requests and signals used to help distinguish legitimate submissions from abuse. The website owner supplies and controls the widget keys.
WaffoHosts checkout and processes payment details entered on its checkout page. FormPostbox receives payment, checkout, subscription and webhook references, plan, amount, currency, status, and billing-period facts for entitlement and support.
CNB encrypted backup storageStores encrypted backup archives attached to a pinned repository commit for disaster recovery. The backup contains exports of business D1 and the separate erasure database; a signed manifest and encrypted hashes are checked before an archive is counted.

Workspace owners can export retained submissions or grant read access through Developer API keys. Information then reaches the systems and recipients they choose. We do not guarantee that information will be processed or stored in a particular country or region.

We may disclose information as required by applicable law, to investigate misuse or protect rights and security, or to providers supporting the service. We do not sell submission content for advertising.

FormPostbox uses session cookies for account access and a browser preference cookie for language. When you use Turnstile or Waffo hosted checkout, those services may use their own cookies or browser technologies under their notices. Blocking necessary cookies can prevent sign-in or checkout from working.

Form submissions have a retention deadline based on their plan: 40 days on Free and one calendar year on Starter. Builder records are archived without a time limit while Builder is active. When Builder access ends, records received during that period remain available until the later of one calendar year after receipt or 30 days after access ends. Upgrading to Builder extends records that have not expired yet. A form owner can preview and confirm a shorter per-form cap: 7 or 30 days on any plan, and 90 or 365 days on a paid plan. A cap applies only to records that are still live when confirmed, can never extend the plan deadline, and continues to apply if the form is deleted or the plan later changes. Returning to the plan default or choosing a longer cap affects future submissions only. Expired or deleted submission content is excluded from normal inbox and export access and is not restored; deletion metadata can remain.

After a deletion request is accepted, account access and new submissions stop immediately. On completion we remove the name, email address and password hash from the account profile, scrub workspace names, origins, notification addresses and Turnstile secrets, revoke API keys, and clear stored submission and notification content. If cleanup is interrupted, access stays stopped and processing continues automatically; the deletion receipt distinguishes pending from completed. After completion the same email can register a new Free account with fresh verification, without old records, keys or paid rights. Minimal identifier-only deletion tombstones are retained to enforce erasure after backup restoration. Transaction references, amounts, dates and audit evidence remain for reconciliation, disputes and legal obligations; they are not restored account access. Encrypted backups are rotated by verified set count, with a target of seven sets. New backup attachments request automatic expiry after 30 days only when the bounded backup policy is explicitly enabled; existing, foreign, or unverifiable attachments and provider enforcement still require verification; failed backups can delay rotation or expiry. Backup restoration must replay the independent deletion journal before service resumes. Payment and email providers apply their own retention practices; already delivered emails remain in recipient mailboxes.

These application and backup retention controls do not establish a provider-wide retention period or guarantee that every copy held by an external provider is erased on the same schedule.

Account owners can manage form settings and notification recipients, export retained submissions, delete individual records, and use the account-closure controls when eligible. Contact support@formpostbox.com for other access, correction, deletion, or privacy requests. We may need to verify that a request relates to you or an account you control. Rights and exceptions depend on applicable law.

We use access controls, password hashing, and other technical safeguards, but no online service can guarantee absolute security. Keep passwords and API keys private, and revoke keys you no longer need. The effective date above identifies this version of the policy.