Privacy Policy

This policy explains what form data is stored, why it is used, who controls it, and when it should be deleted.

Effective November 11, 2026

At a glance

Form owner

The form owner chooses the questions and must explain the purpose for collecting each answer.

Respondent

The respondent provides only the information requested and should receive a clear privacy notice.

Stored response

The service keeps the answer for the stated workflow and should remove it when that need ends.

Data we handle

Hosted forms store the answers a respondent submits, the submission time, and the form needed to interpret those answers. The public website may receive standard server logs used for reliability and abuse prevention.

Purpose and retention

Form owners control the questions they ask and are responsible for providing an appropriate privacy notice. Response data should be retained only for the workflow that justified collection. Production deployments must document retention periods, deletion requests, backups, and subprocessors before collecting personal data.

Advertising, cookies, and consent

Web-Forms.net does not currently place advertising cookies. If advertising is enabled, this policy and the consent interface will be updated before ads are served.

Advertising providers, including Google, may use cookies, web beacons, IP addresses, or similar identifiers to deliver, measure, limit, and personalize advertising where permitted. Visitors in regions that require consent will be offered the required choices through an approved consent platform before nonessential advertising storage is used.

Advertising will be limited to publisher-content pages. It will not be placed inside form editing, response management, submission, confirmation, or other private workflow screens. The site will not ask visitors to click ads or present an advertisement as navigation, a template action, or a download control.

Sensitive information

Do not use a general form to collect passwords, full payment card details, medical records, or government identifiers. Other regulated data needs a deployment designed and approved for that specific use.

Related implementation guidance

Use the form privacy and security hub to translate data minimization and access principles into a working review. Then create a form response retention schedule for primary records, exports, notifications, and backups.