GeoCloaker

Privacy

This notice describes what GeoCloaker stores and limits the operator's responsibility for data, routing, and outside providers. It works together with the terms of service.

1. Who this notice covers

This notice covers geocloaker.com and the GeoCloaker service. The site operator and administrator is the party responsible for the service. It applies to account holders, to people who visit a routing link, and to anyone who writes to support. It is not a promise that a destination site, a short-link provider, a wallet, or a network will treat data in any particular way.

2. What the service stores

For an account, GeoCloaker stores the name, email address, a password hash or a Google account id, campaign rules, destination addresses, support messages, and billing records that a payment was actually recorded. A crypto checkout stores the deposit address assigned to the account, the plan, the expected amount, and the transaction hash and amount of a detected USDT transfer. Routing logs store the country, the outcome, the destination host, and a short hash of the IP address. The raw IP address is not shown in the product. Daily aggregates are kept for 90 days. A hash is not an anonymous identifier. Support attachments stay on this server and are available only to the ticket owner and a super admin.

3. What a routing link does

When someone opens a published link, the service reads the country from the visitor IP supplied by this server's reverse proxy and redirects to the destination the account holder chose. GeoCloaker does not control what the destination collects after the redirect. The account holder, not the operator, decides the destination, the country rules, and the traffic sent to the link.

4. The account holder is solely responsible

The account holder is solely responsible for the personal data they upload, for the destinations they configure, and for the people they send to those destinations. They are responsible for having a lawful basis to send that traffic, for any notice those people should receive, and for the data practices of every page they link to. The operator is not a party to the relationship between the account holder, visitors, advertising networks, or destination-site owners, and is not their privacy representative.

5. Cookies and sign-in

A signed-in browser stores an httpOnly session cookie named geocloaker. It is used to keep the session and to protect the account. The service does not use that cookie to sell ads. Blocking cookies will stop sign-in. Payment and short-link providers may set their own cookies on their own sites.

6. Outside providers

Short links, hosting, email, Google sign-in, and Ethereum are provided by other parties under their own terms. A USDT transfer is written to a public blockchain. The operator cannot delete it, hide it, or promise that a wallet, an exchange, or a block explorer will keep it private. Country detection can be wrong for VPNs, mobile networks, proxies, and shared addresses. The operator does not promise that a provider will stay available or that a log will be complete.

7. No security warranty

The service is provided as is and as available. The operator does not promise that storage is unbreakable, that a breach will be detected, that a backup exists, or that data will survive a failure. Account holders must keep their password secret and must not put secrets, payment card numbers, or other people's private files into campaigns or support tickets.

8. How long data is kept

Account data stays while the account exists and as long as needed for security, billing, and disputes. Routing aggregates are kept for 90 days. Crypto payment records and billing events are kept as the record that a plan was or was not opened. The operator may delete or keep data when an account is closed, and may refuse a request that would hide abuse, break a billing record, or expose another person.

9. Requests and complaints

A person may ask, through support, what account data is held and may ask for a correction of their name. The operator will answer if the request is about data this service actually holds. The operator does not have to retrieve data from a destination site, a blockchain, or a short-link provider. A complaint about traffic that an account holder sent is a complaint against that account holder.

10. Limitation of liability

To the maximum extent mandatory law allows, the operator, anyone acting for the operator, and anyone involved in running the site will not be liable to an account holder, a visitor, or any other person for any damage, direct or indirect, consequential, special, or punitive, arising out of personal data, a redirect, a wrong country, a lost log, a public blockchain record, a provider, or unauthorized access. If liability is found despite this, it is limited to the amount actually paid to the operator for the service during the three months before the event. If nothing was paid, the cap is zero. This notice does not exclude liability that mandatory law does not allow to be waived, including fraud or willful misconduct.

11. Indemnity

The account holder will indemnify the operator and anyone acting for the operator against any claim, demand, fine, damage, or expense, including reasonable attorney fees, arising from the account holder's links, destinations, traffic, uploaded files, or a claim that the account holder misused personal data.

12. Law and changes

The law of the State of Israel governs this notice. Exclusive jurisdiction is with the competent courts in Israel. The operator may update this notice, and the text published on the site is the controlling text. A material update applies to use that continues after it is published. Last updated 26 October 2026.