free · 0% fees · 60sclaim your page
legal · cookies

last updated

crypt.pe — Cookie Policy

Effective Date: 30 May 2026 Last Updated: 12 September 2026 Operator: 3-102-969985 S.R.L. (Sociedad de Responsabilidad Limitada), registered with the National Registry (Registro Nacional) of Costa Rica. Domicile: Escazú, San José, Costa Rica.

This Cookie Policy explains what cookies and similar technologies the crypt.pe website uses, why we use them, and how you can control them. It is a supplement to our Privacy Policy.

In short: we use one first-party cookie for your theme preference, plus product-analytics cookies and browser storage set by Google Analytics and PostHog, described in full below. We do not use cookies for advertising or cross-site ad targeting.


1. What is a cookie?

A cookie is a small text file that a website places on your browser when you visit. Cookies are widely used to make websites function correctly, to remember user preferences, and (often) to track visitors across sites for advertising.

Closely related technologies include localStorage (a browser-storage mechanism for application data) and session storage (similar, but cleared on tab close). We use localStorage for our dashboard application; we describe it in this Policy in the interest of full transparency, even though it is not technically a "cookie".

2. Cookies we set

NameTypePurposeLifetime
cryptpe_themeFirst-party, functionalRemembers your chosen light / dark / auto theme so it persists across page loads.365 days
_gaGoogle Analytics, analyticsDistinguishes unique visitors for aggregate traffic measurement (Google Analytics 4).2 years
_ga_6N69X4XTWMGoogle Analytics, analyticsPersists session state for our GA4 property.2 years
ph_*_posthogPostHog, analyticsDistinguishes visitors and persists analytics state for PostHog product analytics.Rolling, up to 1 year

The theme cookie contains no personal data and does not track your browsing across sites. The Google Analytics and PostHog identifiers are pseudonymous analytics identifiers set when the site's analytics scripts load; they are used for traffic measurement and product analytics as described in Section 4.

3. Browser storage we use (not cookies)

KeyLocationPurpose
cryptpe_tokenlocalStorageYour JSON Web Token after sign-in, used to authenticate API calls from the dashboard. Cleared on sign-out or token expiry.
cryptpe:profile-themelocalStorageMirror of the theme preference, used by client-side rendering before the cookie is read.
ph_* entrieslocalStorage / sessionStoragePostHog analytics state: event queue, session information and feature-flag cache used by PostHog product analytics (including autocapture and session-recording components where enabled).

The cryptpe_* items sit on your device, are accessible only to the crypt.pe origin, and are not shared with any third party. The PostHog entries support the analytics described in Section 4.

4. Analytics we use

We currently use two analytics providers on the website:

  • Google Analytics 4 (measurement ID G-6N69X4XTWM, provided by Google LLC) — aggregate traffic measurement: page views, referrers, approximate geography and device category.
  • PostHog (PostHog, Inc.) — product analytics: page views, interaction events (autocapture, including dead-click detection), web-vitals performance data, optional surveys and session recordings used to diagnose usability problems.

These scripts load only after you choose "accept" in the on-site cookie consent control (and on later visits while your acceptance remains stored). If you reject or make no choice, the analytics scripts are not loaded. They set the cookies and storage entries listed above and process pseudonymous identifiers, IP-derived approximate location and device/browser metadata under each provider's own terms. Separately, the per-page visitor counter shown to page owners uses server-side IP-hashing that resets daily and stores no identifier on your device (see Privacy Policy §3).

We do not show ads, use advertising or retargeting cookies, embed social-media tracking widgets, or sell analytics data.

5. Cookies set by third parties on certain pages

Some pages of the Service load third-party scripts that may set their own cookies:

  • Cloudflare — when our DNS or DDoS protection is active, Cloudflare may set short-lived security cookies (e.g. __cf_bm) for bot mitigation. These are functional cookies, not tracking cookies.
  • Wallet providers (e.g. WalletConnect, MetaMask SDK) — only when you choose to connect a wallet, the wallet provider may set cookies under its own domain in line with its own privacy policy.

We do not control the cookies set by third-party services, and their use is governed by the privacy policies of those parties.

6. How to control cookies

You are always free to:

  • Use the consent control. A banner with equally prominent accept and reject options appears on your first visit. Analytics load only after you accept. You can change or withdraw your decision at any time via "cookie settings" in the site footer; withdrawing deletes the analytics cookies and storage we can remove and stops further collection.
  • Block or delete cookies through your browser settings. The Service will still work; you will simply not have your theme remembered across sessions.
  • Block the analytics scripts with a content blocker, or opt out of Google Analytics with Google's browser opt-out add-on.
  • Delete the cryptpe_theme cookie at any time from your browser's site-storage controls.
  • Clear localStorage for crypt.pe, which will sign you out of the dashboard, clear your saved theme and remove PostHog's stored state.
  • Email us at legal@crypt.pe to object to analytics processing or request deletion of analytics data linked to you.

Most browsers also allow you to send "do not track" or Global Privacy Control signals; we do not perform cross-site ad tracking, and we are reviewing honouring these signals for analytics.

7. Costa Rica, EU and UK compliance

Costa Rica (Law No. 8968). Our functional theme cookie stores only a preference and contains no personal data. Analytics identifiers set by Google Analytics and PostHog are pseudonymous; we process them for service improvement and traffic measurement as described in the Privacy Policy. The localStorage items described in Section 3 that hold your session data are never shared with third parties.

EU / UK ePrivacy. The theme cookie relies on the "strictly necessary" / functional exception and is set without prior consent. The Google Analytics and PostHog cookies and storage described above are not strictly necessary; they are placed only after you give prior consent through the on-site consent control, which offers equally prominent accept and reject options. You can withdraw consent at any time via "cookie settings" in the footer or by emailing legal@crypt.pe.

8. Changes to this Policy

We may update this Policy to reflect changes in technology or law. Material changes will be highlighted on the Service with at least 14 days' notice. The current version is always available at https://crypt.pe/cookies.

9. Contact

Questions about cookies, or to exercise your data rights: legal@crypt.pe.


© 2026 3-102-969985 S.R.L. · Escazú, San José, Costa Rica.

about crypt.pe

01

non-custodial by design

Payments settle wallet-to-wallet on-chain, straight from the payer to your own wallet. crypt.pe never holds, freezes or forwards funds — there is no platform balance and no withdrawal step, and every payment gets a verifiable on-chain receipt.

02

0% transaction fees

Plans are flat subscriptions with a free tier — compare that with the 1–2% charged by custodial processors. One page accepts 19 supported assets — including Bitcoin, USDT, Ethereum and Solana — across 13 networks, with simple pricing and no payout schedule.

03

tools merchants actually use

Exact-amount invoices with live tracking, product links, printable QR standees, HMAC-signed webhooks, CSV exports and a Stripe-style API — see the merchant guides or create your free page in about a minute.

04

how a payment works

You add wallet addresses you already own, share your crypt.pe link or QR code, and the customer pays from their own wallet. crypt.pe locks the amount at invoice time, watches the chain, matches the transaction and issues a receipt both sides can verify on a block explorer — software around the payment, never in the money flow.

05

available wherever wallet-to-wallet payments are permitted

Because settlement is on-chain to your own wallet, there is no bank partnership gating access and no account that can be closed over geography — local crypto rules still apply. crypt.pe publishes country guides for 60 markets and is available where wallet-to-wallet payments are legally permitted.

06

stablecoin-first, volatility optional

Accept USDT or USDC and a $100 invoice locks to a fixed token amount that targets a $1 peg — value movement between creation and payment stays minimal, though stablecoins can temporarily depeg, and issuer, liquidity and network risks remain. Prefer BTC, ETH or SOL? Token amounts are locked at invoice time either way, and your dashboard records the USD value of every payment for clean bookkeeping. Questions? Start with the FAQ or payment help.