Privacy Policy & Cookies

1. Who handles your information

Vootter (vootter.com) is currently operated by JS Vis FZ-LLC, based in the United Arab Emirates. Business correspondence address: Rakez. Contact: support@vootter.com.

The operator is responsible for how personal information is used for Vootter. This policy applies to the website and its account, hosting, voting and reporting features. External services have their own policies.

2. Information we collect

• Account information: Google account identifier, verified email address and available profile-picture URL; your chosen display name, gender and birth year; profile image and public link; account status, join date and last sign-in time. The database stores a supplied birth year as 1 January of that year; this is a placeholder, not a claim about your actual birthday. Vootter does not receive your Google password.
• Community activity: assets, challenges, images, descriptions, comments, reports, ownership claims and moderation messages you submit. Administrators can also create member profiles using information supplied to them.
• Votes: your user identifier, chosen challenge and asset, vote time, and snapshots of gender, birth-year/date information, city and country used for voting statistics. Historical rating values may be retained even when new ratings are disabled.
• Location and referral information: IP address and approximate city/country obtained from it, plus referral information from the page’s URL query. This does not use your device’s GPS. IP location can be inaccurate. Do not put sensitive personal information into referral links.
• Purchases and support: package, price, currency, coupon information, payment/order identifiers and status, support correspondence and notification delivery information. PayPal handles payment credentials; Vootter’s payment integration records payment references rather than full card details.
• Technical information: session identifiers, security information and server logs needed to deliver and protect the website. Hosting and external-resource providers receive connection information such as IP address when your browser contacts them.

3. What other people can see

Your profile is public. It can show your display name, photograph, email address, city, country, join date, public link, total votes cast and live hosted challenges. Challenges, asset descriptions, comments and listing contact details can also be public.

Recent-vote lists can link your name and profile to an asset you voted for and show the vote time. Votes are therefore not anonymous. Challenge statistics show grouped gender, age, country and city results; small groups can still make it possible to infer information. Do not submit content you are not comfortable making public. Public content may be indexed by search engines or copied by others.

Deleting or blocking location cookies does not remove information already saved in an account or past vote. Vote statistics may use the city/country already in your account. Contact us to request correction or deletion.

4. Why information is used

We use account and activity information to provide the services you request, maintain voting rules, host content, process purchases and send service or moderation messages. We use reports and security records to investigate abuse and protect the service. Grouped voting information helps people understand participation; location information helps show local challenges.

Where UK/EU data-protection rules apply, processing necessary to deliver a requested account or purchase may rely on performance of a contract; necessary fraud prevention, security and proportionate moderation may rely on legitimate interests; legally required records may rely on legal obligations. Where optional cookie storage requires consent, that consent must be obtained through a suitable mechanism; this notice does not itself obtain it. Any use of demographic statistics or public personal information must have an appropriate basis and safeguards; a cookie choice is not blanket consent to unrelated processing. Other applicable laws, including UAE data-protection requirements, may require different or additional conditions.

5. Cookies and browser storage

Cookies are small values stored by your browser. Vootter uses the following cookies and similar storage:

Current cookie behaviour: Vootter sets the location and source cookies automatically on a first visit when a source cookie is not already present. This page describes that behaviour; it does not introduce a consent banner or a cookie-preference control.

We use your IP address server-side to obtain approximate city/country information, consulting the ip_data cache first and ipgeolocation.io if needed. IP-cache records are separate from browser cookies. Location and referral values can be copied into your account when you sign up, and location may be used in vote records.

You can block or delete cookies through your browser settings. Blocking all cookies may prevent sign-in and other session features. Deleting a cookie does not delete historical account, vote, referral or IP-cache records. Contact support for data requests. Google sign-in, PayPal and external content may involve their own cookies and privacy notices.

Reading this policy or continuing to browse is not a substitute for consent where applicable law requires it. A separate consent approach for optional cookies remains to be implemented and reviewed.

6. Service providers and external content

Vootter uses Hostinger for hosting and email services, Cloudflare R2 for uploaded images, Google for sign-in and Google-hosted profile images, ipgeolocation.io for IP-based location, and PayPal for payments. Browser requests for external images, libraries and fonts may also reach their hosting/CDN providers. These parties receive the information needed for the requested function and may process it under their own policies and contractual arrangements.

Relevant notices: Hostinger, Cloudflare, Google, ipgeolocation.io and PayPal.

Information may be processed outside your country. Applicable transfer safeguards depend on the provider, processing location and law involved. Contact support for information about the arrangements relevant to your data. We may also disclose information where required by law or needed to handle a legal claim or protect people’s rights.

7. Retention and security

Cookie expiry periods above apply to the browser copies only. Account, vote, content, report, payment, notification and IP-cache database records do not automatically expire when cookies do. Retention is assessed according to the ongoing service purpose, account status, disputes, fraud prevention and applicable accounting/legal obligations. Requests to delete or correct records are handled through support; there is no automatic account-deletion control on the website.

Access controls, protected sessions and server-side validation help protect information, but no service can guarantee complete security. Do not send passwords, full payment-card details or identity documents in a first support message. If verification is needed, we will explain what is necessary.

8. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction or a copy of your data, object to certain processing, and withdraw consent where consent is used. Withdrawal does not change the lawfulness of earlier processing. Some records may need to be retained for legal obligations or claims; we will explain when a request cannot be fully met.

Email support@vootter.com from your account email where possible and explain your request. You can also complain to the relevant data-protection authority. For UK matters, contact the Information Commissioner’s Office; EU/EEA residents may contact their local supervisory authority. UAE rights and complaint routes depend on the law and jurisdiction applicable to the operator.

If you are a parent or guardian concerned about a child’s account or published information, contact support. We will review the concern and applicable age and authorisation requirements.

9. Policy changes

We update this page when relevant practices change. The revision date appears at the top. A change of operator will be reflected here, with additional notice where required. Any purpose requiring consent must have the appropriate choice mechanism before it starts.