Blankform / Policies

Privacy notice

How information is handled during Blankform development and testing.

Draft for development & testing ? Updated 11 November 2026

1About this draft#

This notice describes the current testing experience for account holders and people answering published forms. It was updated on 11 November 2026. It is not a statement that Blankform is ready for public release.

The operator's identity and contact details, retention periods and complete provider information must be confirmed before public launch. This draft does not replace any rights that apply to you.

2Information used#

Please use fictional or non-sensitive information while testing.

2.1Account information#

Account testing uses your name, email address, password hash, chosen avatar and session records (including available device/IP details) to provide account access. Verification and password-reset flows use your email address. If enabled, two-factor authentication stores an encrypted authenticator secret, encrypted recovery codes and verification/lockout state. Do not share your password with another person.

2.2Forms and answers#

Blankform stores saved form content, published versions and submitted answers. A submission includes its submission time and the form version answered. The form creator can view and export responses through their account.

The questions a creator asks determine what respondents provide. Avoid sensitive information, confidential records and information about other people during testing.

2.3Sessions and technical processing#

Sign-in uses cookies to maintain your session. Hosting, database and email services process information needed to operate the application. A complete cookie and service-provider inventory is still being prepared; this draft makes no promise that testing activity is anonymous.

3How information is used#

Information is used to create and authenticate accounts, save and publish forms, collect and display responses, send account-related emails and investigate problems during development. Do not enter real personal data solely to test a feature when sample data will work.

4Who can access information#

Published questions are visible to anyone with access to the public form link. Submitted answers are available to the creator through their account and CSV exports. A public form link does not provide the creator's response-management access.

Service providers and authorised operators may need to process stored information to run, maintain or troubleshoot the service. Final provider, processing-location and access details remain to be documented before public release.

5Storage, retention and deletion#

Testing data may be changed or removed as development progresses. Keep a separate copy of information you need. Permanent form deletion removes the form, saved versions and responses from the application.

Account deletion in Settings removes the account, profile, sessions, authenticator records, account-linked verification records, forms, versions and responses from the active database. Retention schedules, operational log retention and backup expiry are still being defined. We cannot yet give a confirmed timeframe for removal from backups. Downloaded CSV files are separate copies managed by whoever downloaded them.

6Questions and requests#

If you are answering a form, ask its creator about the purpose of its questions and any request concerning your answers. For an issue with Blankform itself, use the channel through which you were invited to test. A dedicated public privacy contact will be provided before launch.

Do not send passwords or sensitive response data when reporting a problem. Read the Help centre for guidance on account access and form deletion.

7Changes to this notice#

This draft will be revised as product and operating decisions are confirmed. Check its date when returning to testing. Material changes and any required notices will need to be addressed before public release.