Effective: 29 August 2026
Embedded Files
Privacy Policy
Privacy Policy
Last updated: 29 August 2026
1. Introduction
1. Introduction
1.1. This Privacy Policy explains how personal data is processed in connection with Vota, a form and survey builder consisting of a web application at vota.dozy.site (the "Service" or "Vota").
1.2. The Service is operated by David Kelen, an individual established in France, trading under the name "Dozy" ("Operator", "we", "us" or "our"). For the processing described in this Policy for which we determine the purposes and means, the Operator is the data controller. For personal data contained in responses submitted to a form, the roles are as set out in section 2.
1.3. This Policy covers personal data processed through your use of the Service. It does not cover the creation, authentication, management, or billing of your Dozy account, which are described in the Dozy Privacy Policy available at dozy.site. Where this Policy refers to information "from your Dozy account", that information is provided to the Service by the Dozy account system so that the Service can function.
1.4. Capitalised terms that are not defined in this Policy have the meaning given in the Vota Terms of Service. In particular, a "Creator" is a User who builds and manages forms, and a "Respondent" is any person who opens or submits a response to a published form.
2. Controller roles
2. Controller roles
2.1. Response data. When you create a form and collect responses, you (the Creator) decide what questions to ask, what data to request, and why. In respect of the personal data contained in or derived from those responses ("Response Data"), the Creator is the data controller, and the Operator acts as a processor on the Creator's instructions, as set out in section 9 of the Vota Terms of Service. The Operator is also an independent controller of Response Data for the limited operational purposes described in section 6.4 (for example security, abuse prevention, logging, and diagnostics).
2.2. If you are a Respondent. The Creator of the form you are responding to is responsible for telling you who they are, what they are collecting, why, on what legal basis, and how you can exercise your rights, and for handling your requests about that data. The Operator does not provide that notice on the Creator's behalf and does not have a direct relationship with you. This Policy describes only the limited processing the Operator carries out as operator of the Service. If you have a question about a specific form or want to exercise rights over your response, contact the Creator of that form. If you cannot identify or reach the Creator, you may contact privacy@dozy.site and we will make reasonable efforts to route your request.
2.3. Account and service level data. For the identity data of Creators taken from their Dozy account, and for technical and log data, notification registrations, and diagnostics, the Operator is the controller.
3. Categories of personal data we process
3. Categories of personal data we process
We process the following categories of personal data.
3.1. Identity data from a Creator's Dozy account. Account identifier, display name, nickname, email address, profile picture, and Plan tier. This data is provided to the Service by the Dozy account system so that the Service can authenticate the Creator and apply Plan limits.
3.2. Form content created by a Creator. Form titles and descriptions, questions, answer options, section names, branching rules, accent colour, header images, confirmation messages, redirect addresses, and form settings such as email collection, sign in requirement, response limits, and closing date.
3.3. Response Data. The answers a Respondent submits, an email address if the form collects one, an approximate location inferred from the Respondent's internet protocol (IP) address, the time of submission, and, if the form requires sign in or the Respondent is signed in, the Respondent's Dozy account identifier. The content of an answer is whatever the Creator's questions ask for, and is determined by the Creator, not by the Operator.
3.4. Draft data. An in progress draft of a Respondent's answers, saved so the Respondent can resume. For a signed in Respondent the draft is stored on the Service and is associated with their account identifier and the form. For a Respondent who is not signed in, the draft is stored only in that Respondent's browser and is not transmitted to us. A Creator's own test answers entered while previewing an unpublished form are stored only in the Creator's browser.
3.5. Submission activity. For a Respondent who is not signed in, a count of how many times they have submitted a given form, stored only in that Respondent's browser and used to apply the Creator's per Respondent submission limit. For a signed in Respondent, the same information is derived from the responses stored on the Service.
3.6. Notification data. If a Creator enables notifications for a form, a web push subscription associated with that Creator's browser, together with the per form notification preference. A notification we send through the browser push service contains a short message that a new response has been received.
3.7. Diagnostics. In the production version of the Service only, we collect error and performance diagnostics. A diagnostic event may include a Creator's account identifier and email address, the error message and stack trace, the application version, the platform (web), the page or action involved, and technical browser and environment information. Diagnostics are processed by our error reporting provider identified in section 7.
3.8. Technical and log data. IP address, request metadata, timestamps, and server logs generated when a device communicates with the Service, and operational logs of notification delivery.
3.9. On device data. The Service stores a small amount of data in your browser, including your theme preference, the builder clipboard, response and preview drafts, and submission counts. This data is described in the Vota Cookie and Storage Notice. It stays on your device and is not transmitted to us except where it forms part of a normal request to the Service.
We do not intentionally collect special categories of personal data through the operation of the Service. A Creator who chooses to ask for such data through a form is responsible for having a valid legal basis and for the additional safeguards that apply, as described in the Vota Acceptable Use Policy.
4. Response storage and encryption
4. Response storage and encryption
4.1. Data transmitted between a device and the Service is encrypted in transit using industry standard transport encryption (HTTPS).
4.2. Form content and Response Data are stored on infrastructure operated on our behalf and are encrypted at rest by that infrastructure provider. Access to stored data by the infrastructure provider's personnel is governed by our agreement with that provider.
4.3. Response Data is not end-to-end encrypted. In addition to the Creator and the Users the Creator authorises, the Operator and its administrators are technically able to access Response Data where necessary to operate the Service, to respond to reports and enforce the Terms and the Acceptable Use Policy, to maintain security, or to comply with law.
5. How responses are shown and disclosed
5. How responses are shown and disclosed
5.1. To the Creator. Responses to a form are visible to the Creator of that form and to any User the Creator authorises. Responses are not visible to other Respondents.
5.2. To Respondents. A Respondent sees only their own answers, and, where the Creator has enabled it, may edit their own submitted response while the form is still accepting responses. A Respondent does not see who else has responded or what they answered.
5.3. On a public link. A published form is reachable by anyone who has its link unless the Creator requires sign in. The link, and the questions on the form, are visible to anyone who opens it.
6. Purposes and legal bases
6. Purposes and legal bases
We process personal data for the following purposes. Where the General Data Protection Regulation or the UK GDPR applies, the legal basis for each purpose is indicated. For Response Data the legal basis for the collection itself is determined by the Creator as controller; the bases below describe the Operator's own processing.
6.1. To provide the Service, including authenticating a Creator's session with their Dozy account, displaying and saving forms, publishing forms, receiving and storing responses, saving and restoring drafts, applying submission limits, and making responses available for viewing and export. Legal basis: performance of a contract with the Creator; and our legitimate interests in operating the Service, including for Respondents who are not party to a contract with us.
6.2. To deliver notifications a Creator has asked to receive. Legal basis: the Creator's consent, given through the browser notification permission; and performance of a contract.
6.3. To operate abuse and safety features, including handling reports about forms, reviewing a form where a risk is identified, and unpublishing or removing forms that violate the Terms or the Acceptable Use Policy. Legal basis: our legitimate interests, and those of other users, Respondents, and the public, in a safe service; performance of a contract; and compliance with legal obligations.
6.4. To secure the Service and prevent abuse, including enforcing capacity and rate limits, detecting and responding to automated or fraudulent responses and to unauthorised access, and keeping operational and security logs. Legal basis: our legitimate interests in the security and integrity of the Service; and compliance with legal obligations.
6.5. To diagnose and fix problems and improve reliability, using error and performance diagnostics. Legal basis: our legitimate interests in a functioning and reliable service.
6.6. To communicate with a Creator about the Service, including service and policy notices. Legal basis: our legitimate interests in keeping users informed; performance of a contract; and compliance with legal obligations.
6.7. To comply with law and to establish, exercise, or defend legal claims, including responding to lawful requests from public authorities. Legal basis: compliance with legal obligations; and our legitimate interests in protecting our rights.
Where we rely on legitimate interests, you may object as described in section 10.
7. Subprocessors
7. Subprocessors
We use the following service providers to process personal data on our behalf.
Web push notifications are delivered by the push service of the Creator's own browser vendor. We do not choose that provider; it is determined by the browser the Creator uses.
We may add or change subprocessors as the Service develops. Where a change of subprocessor affects how personal data is processed, we will update this section, and for a material change we will provide notice in accordance with section 13.
8. International transfers
8. International transfers
8.1. Personal data is primarily stored and processed in the European Union.
8.2. Some of our subprocessors, in particular those providing web application delivery and diagnostics, are located in or transfer personal data to the United States or other countries outside the European Economic Area and the United Kingdom.
8.3. Where personal data is transferred outside the European Economic Area or the United Kingdom to a country that has not been recognised as providing an adequate level of protection, the transfer is made subject to appropriate safeguards, in particular the European Commission's Standard Contractual Clauses and, where applicable, the United Kingdom International Data Transfer Addendum, together with additional measures where necessary. You may request information about these safeguards using the contact details in section 15.
9. Retention
9. Retention
9.1. Form content is retained until the Creator deletes the form or the form is permanently deleted following archival.
9.2. Responses, answers, and drafts are retained until the Creator deletes them, the Creator deletes the form, or the form is archived and then permanently deleted. An archived form is recoverable for 30 days, after which the form and all of its responses, answers, and drafts are permanently deleted. A signed in Respondent's draft is deleted when the response is submitted. We may remove drafts that have been inactive for an extended period.
9.3. Identity data from a Creator's Dozy account is retained for as long as the Creator has an active Dozy account and uses the Service. Closure of the Dozy account results in deletion of the Creator's forms and responses within a reasonable period.
9.4. Notification registrations are retained until the push subscription becomes invalid, the Creator disables notifications, or the Creator signs out, after which they are deleted.
9.5. Diagnostics are retained by our error reporting provider for a limited period, after which they are deleted or aggregated.
9.6. Technical and operational logs are retained for a limited period for security, troubleshooting, and abuse prevention purposes and are then deleted or aggregated.
9.7. When data is deleted it is removed for the Creator and any authorised Users. Residual copies may persist for a limited time in routine backups and in browser storage on Respondents' devices, and age out in the ordinary course.
9.8. We may retain personal data for longer where required to comply with a legal obligation or to establish, exercise, or defend a legal claim.
10. Your rights under the GDPR and UK GDPR
10. Your rights under the GDPR and UK GDPR
10.1. If the GDPR or the UK GDPR applies to the processing of your personal data, you have the right to:
(a) request access to the personal data we hold about you;
(b) request rectification of inaccurate or incomplete personal data;
(c) request erasure of your personal data;
(d) request restriction of processing;
(e) object to processing that is based on our legitimate interests;
(f) request portability of personal data you provided to us, in a structured, commonly used, machine-readable format; and
(g) withdraw any consent you have given, without affecting the lawfulness of processing carried out before withdrawal.
10.2. If you are a Creator, you can exercise many of these rights directly in the Service: you can edit and delete your forms, view, correct where possible, export, and delete responses, manage notification settings, and export the responses to a form as a data file. For other requests, contact privacy@dozy.site.
10.3. If you are a Respondent, the Creator of the form is the controller of your response data. Direct your request to that Creator. Where the Operator receives such a request, it will refer it to the Creator or ask you to contact the Creator directly, unless the Operator is legally required to act itself. The in Service export feature that a Creator can use satisfies a portability request for the responses to that Creator's form.
10.4. We may need to verify your identity before acting on a request. We will respond within the period required by applicable law.
10.5. You have the right to lodge a complaint with a supervisory authority. In France this is the Commission Nationale de l'Informatique et des Libertes (CNIL), www.cnil.fr. You may also complain to the supervisory authority in your country of residence or place of work.
11. California privacy rights
11. California privacy rights
11.1. This section applies to residents of California and supplements the rest of this Policy. Terms used in this section have the meanings given in the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA").
11.2. Categories of personal information collected in the last 12 months: identifiers (such as account identifier, name, email address, and IP address); internet or other electronic network activity information (such as submission activity, request metadata, and diagnostics); geolocation data (approximate location inferred from IP address); and other information you provide, namely the content of forms a Creator builds and the content of responses a Respondent submits. The sources, purposes, and disclosures for these categories are described in sections 3, 6, 7, and 9. Where a Respondent submits personal information through a form, the Creator of that form is the business responsible for that information, and the Operator acts as that Creator's service provider.
11.3. No sale or sharing. In the last 12 months we have not sold personal information and have not shared personal information for cross-context behavioural advertising. We do not have actual knowledge that we sell or share the personal information of consumers under 16 years of age.
11.4. Your rights. Subject to verification and to exceptions in the CCPA, you have the right to know the personal information collected about you and how it has been used and disclosed, the right to request deletion, the right to request correction of inaccurate personal information, and the right to limit the use of sensitive personal information. We do not use sensitive personal information for purposes that would trigger the right to limit. Where the right relates to information you submitted as a Respondent, we will refer the request to the relevant Creator.
11.5. Non-discrimination. We will not discriminate against you for exercising your CCPA rights.
11.6. How to exercise. Submit a request to privacy@dozy.site. You may use an authorised agent, in which case we may require proof of authorisation and verification of your identity.
12. Children
12. Children
12.1. The Service is intended for users aged 13 and over and is not directed to children under 13.
12.2. A Creator must not create a form directed to children under 13 unless the Creator has obtained verifiable parental consent and complies with the requirements described in the Vota Acceptable Use Policy.
12.3. We do not knowingly collect personal data from a child under 13. If we become aware that we have collected personal data from a child under 13 other than at the direction of a Creator who has met the requirements above, we will delete that data. If you believe a child under 13 has provided personal data to the Service, contact privacy@dozy.site.
13. Security
13. Security
13.1. We use technical and organisational measures designed to protect personal data, including transport encryption, encryption at rest by our infrastructure provider, row level access controls in the database, authentication controls, and restricted administrative access.
13.2. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
13.3. If we become aware of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority and affected persons to the extent and within the time required by applicable law. Where the breach affects Response Data, we will notify the relevant Creator without undue delay so that the Creator can meet its own obligations.
14. Changes to this Policy
14. Changes to this Policy
14.1. We may amend this Policy from time to time. The current version is identified by the effective date at the top.
14.2. If we make a material change, we will provide notice through the Service or by email before the change takes effect, except where an immediate change is required to comply with law or to address a security or safety risk. Your continued use of the Service after a change takes effect constitutes acknowledgement of the updated Policy.
15. Contact
15. Contact
For questions about this policy, to exercise your rights, or to report a privacy concern, please contact us.
Name: David Kelen
Email: privacy@dozy.site
Response time: Within 30 days
Page updated
Google Sites
Report abuse