Cookie Policy
Last updated 7 October 2026
Rampy.money uses a deliberately small number of cookies and similar technologies. One of them is an advertising pixel, and it runs only if you allow it. We do not sell data to advertisers.
1. What we set
| Name | Type | Purpose | Expires |
|---|---|---|---|
rampy_session | Strictly necessary | Keeps you signed in. Signed, HTTP-only and, in production, Secure, so it cannot be read by scripts. | 30 days |
rampy.wallet | Strictly necessary (local storage) | Remembers which wallet address you connected so you do not reconnect on every page. | Until cleared |
rampy.theme | Preference (local storage) | Written only when you pick light or dark yourself. Until then we follow your device setting and store nothing. | Until cleared |
_ga, _ga_* | Analytics (only if you allow it) | Google Analytics, to count visits and see which pages are read. Set only after you allow analytics, never on your account pages, and deleted when you withdraw. | Up to 2 years |
rampy.consent | Strictly necessary | Your answer to this banner, kept both in your browser and in a cookie so that anything done on your behalf later — such as reporting a completed order to X, hours after you have closed the page — can honour it too. It holds the decision and nothing else: no identifier. | 1 year |
rampy.twclid | Marketing (only if you allow it) | The click identifier X puts on its own adverts, kept only if you arrived through one and allowed marketing. It is what lets us tell X that an advert led to a completed order once the money finally settles, which can be days later when no page of ours is open. Deleted the moment you withdraw. | 30 days |
_tw* and cookies set by x.com | Marketing (only if you allow it) | The X (Twitter) advertising pixel, to tell whether an advert led anywhere useful. Nothing is requested from X until you allow it — refuse and its script is never fetched. Never used on your account pages. Withdraw and we remove the script, delete what it set on our own domain, and send X nothing further. | Up to 13 months |
| Privy cookies and storage | Strictly necessary | Set by our authentication provider to keep your login session valid. Loaded only on the sign-in page and the signed-in app, never on the pages you can read without an account. | Per their policy |
Everything except the analytics and marketing rows is strictly necessary for a service you have asked for, so those need no consent. Those two are different: both are optional, both are off until you say otherwise, and we ask before either runs.
Until you answer the banner, the public pages store nothing. The home page, this legal section, the blog and the support page set no cookies and write nothing to your browser. Your answer itself is remembered — the rampy.consent record above — so the banner does not ask again; that is strictly necessary and holds no identifier. Sign-in storage begins only when you go to sign in.
We use Google Analytics, and only with your permission. Google’s tag is not loaded until you allow analytics: before you choose, and if you refuse, nothing at all is sent to Google. If you allow it, the tag loads and sets its cookies; if you later change your mind, it is switched off at once and its cookies are deleted. The X advertising pixel works the same way and only with marketing allowed.
We never measure anything inside your account. Both analytics and the advertising pixel stop at the sign-in page, because a signed-in address like a transaction page identifies a real payment and that is not something to hand to a third party — allowing marketing does not change that. We do not sell or share personal information.
One part of this happens without your browser. When an order settles, our server tells X that an advert led to it — the pixel cannot do that, because settlement arrives hours or days after the page was closed. It happens only if you allowed marketing and only if you arrived through one of our adverts, and the only thing identifying it is that advert’s own click identifier. We do not send your email address, your phone number or your IP address, and we never send anything at all for a customer who did not come from an advert.
2. Third parties
Our authentication provider sets its own cookies and storage on their domain. Identity verification, when you go through it, is hosted by our verification partner and is governed by their policies. Google Analytics, if you allow it, is provided by Google and governed by their policies, as is the X advertising pixel by X. Cookies those companies set on their own domains are theirs, not ours: withdrawing stops us sending them anything further and clears what was set on our domain, but we cannot delete a cookie held on someone else’s. See the links in our Privacy Policy.
3. Your choice
When you first arrive we ask whether to allow analytics or marketing. Both start switched off, refusing takes the same single click as accepting, and refusing is remembered so we do not ask again. You can change your mind at any time:
4. Controlling cookies
You can block or delete cookies in your browser settings. Blocking the session cookie will stop you from signing in, because the service cannot recognise you between pages. Clearing local storage simply means reconnecting your wallet.
4. Contact
Questions: privacy@rampy.money.