Privacy Policy

PatronVoice is operated by Pavel Sotnikov, an independent developer, as a solo project. For privacy questions and requests, write to support@patronvoice.com.

We are the controller for account data, sign-in data and server logs — the data the Service needs in order to exist.

For the patron data a creator imports from their Patreon campaign, the creator is the controller and we act as their processor: we hold and process that data to run their polls, and we do not use it for our own purposes.

When anyone signs in, Patreon gives us their Patreon user ID, name, email address and avatar URL. For patrons that is all we request — the scopes are identity and identity[email].

When a creator signs in, we additionally request access to their campaign and its members. From that we store the campaign (name, page URL, patron count), its tiers (title, amount, description) and its member list: for each member the Patreon member and user ID, name, email address, patron status, current tier and currently entitled pledge amount in cents.

We store the OAuth access and refresh tokens issued for a creator’s account, encrypted at rest, so that membership data can be refreshed without asking them to sign in again. Tokens are used only against the Patreon API.

Patreon also sends us webhooks when a membership is created, updated or deleted. We store the event payload so that membership changes can be applied, and re-applied if processing fails.

Creators: poll titles and descriptions, uploaded option images, the vote weight assigned to each tier, and poll settings such as the closing date, visibility and whether votes can be changed.

Patrons: the option you vote for. With each vote we record the poll, your account, your Patreon user ID, the tier you were in, its title, the weight applied and the time of the vote.

Anything you send us by email at support@patronvoice.com, for as long as we need it to deal with your request.

A session cookie that keeps you signed in and a CSRF cookie that protects forms against cross-site abuse. Both are strictly necessary for the Service to work; sessions live in a short-lived server-side store.

Standard server logs, containing the IP address, user agent, requested URL and timestamp of each request. We use them for security, abuse prevention and debugging.

We use no analytics, advertising, profiling or third-party tracking scripts on any page of PatronVoice.

To sign you in, to determine whether you may see a poll, and to calculate the weight of your vote — necessary to perform the contract you enter into by using the Service.

To show creators the results of their polls, including who voted for which option, and to produce CSV exports on paid plans — necessary to provide the Service the creator has asked for.

To determine a creator’s plan from their membership of the PatronVoice campaign on Patreon and to enforce the publishing quota — necessary to perform the contract.

To keep the Service secure, prevent abuse and vote manipulation, fix errors and improve how it works — our legitimate interest in running a functioning, non-manipulated service.

To comply with legal obligations where they apply. Where the law requires consent for something, we ask for it, and you can withdraw it.

We do not sell personal data, do not share it for advertising, and do not use it to train machine-learning models.

Polls are not anonymous to the creator who published them. That creator sees each voter’s name, the tier they were in, the weight of their vote and the option they chose, and can export this as CSV on a paid plan. Other patrons see only aggregated results, and only if the creator has made results visible to them.

A creator only ever sees data for their own campaign. Creators cannot see each other’s campaigns, patrons, polls or results.

We disclose data outside the Service only where we must: to comply with a legal obligation or a valid legal request, or to protect the rights and safety of users and of the Service.

Patreon — the source of identity and membership data, and the payment processor for plans. Patreon’s own handling of your data is governed by Patreon’s privacy policy.

Laravel Cloud and its underlying cloud infrastructure host the application, its database, its session and cache store and uploaded images, in the United States (region us-east-1).

This means data is transferred to and stored in the United States. If you are in the EEA or the UK, such transfers rely on the standard contractual clauses and equivalent safeguards offered by those providers.

These providers process data on our instructions and may not use it for their own purposes. We add no advertising or analytics processors.

Account and membership data is kept while the corresponding Patreon connection exists. When a patron leaves a campaign, their membership record is marked inactive and kept so that historical results stay meaningful, until the creator deletes the poll or campaign or asks us to remove it.

Votes are kept for as long as the poll exists; deleting a poll deletes its options, images and votes.

Deleting an account deletes the creator record, campaign, tiers, imported members, polls and votes attached to it. Aggregated statistics that no longer identify anyone may be kept.

Server logs and stored webhook payloads are kept for a short operational period — normally no longer than 90 days — and are then removed or overwritten. Sessions expire automatically.

Depending on where you live, you may have the right to access your personal data, to correct it, to receive a copy in a portable format, to have it deleted, to object to or restrict certain processing, and to withdraw consent where processing is based on it.

To exercise any of these, write to support@patronvoice.com from the email address on your Patreon account, or tell us which account you mean. We reply within the period applicable law allows — at most one month under the GDPR. There is not yet a self-service delete button in the interface; requests by email are handled manually.

If your request concerns patron data inside a creator’s campaign, we may need to pass it on to that creator, since they are the controller of that data. We will tell you when we do.

You can revoke PatronVoice’s access to your Patreon account at any time in Patreon’s settings. That stops further data being read; it does not by itself delete what has already been stored, so send us a deletion request as well if that is what you want.

If you are in the EEA or the UK, you also have the right to complain to your local data protection authority.

All traffic is served over HTTPS. Patreon access and refresh tokens are encrypted at rest, and incoming Patreon webhooks are verified by signature before being processed.

We never receive or store payment card details: all payments happen on Patreon.

Uploaded poll images are stored on public file storage, so anyone holding the direct file URL can open the image without signing in. Poll pages themselves are access-controlled, but do not upload images that must stay confidential.

No system is perfectly secure. If a breach affects your personal data and the law requires notification, we will notify you and the competent authority without undue delay.

PatronVoice is not directed at children and requires a Patreon account, which has its own minimum age requirement. We do not knowingly collect data from children below that age; if we learn that we have, we delete it. Write to support@patronvoice.com if you believe this has happened.

We may update this Policy as the Service develops. The “Last updated” date at the top of this page reflects the current version, and material changes will be announced in the Service before they take effect.

Privacy questions and requests: support@patronvoice.com. See also our Terms of Service, which govern use of the Service.