Skip to content

Legal

Privacy policy

Last updated 21 October 2026

Draft for review

This text is a starting point written for the MVP. It has not been reviewed by a lawyer and must be checked before Planitory takes real payments.

This policy explains what personal data Planitory collects, why, who we share it with, and the choices you have.

What we collect

  • Account details: name, email address, username and a hashed password (we never store your password itself).
  • Profile details you choose to add: photo, bio, location, website and social handles.
  • Activity in your account: guides you save, buy, review, create and follow.
  • Payments: the amount, status and date of each purchase. Card details go directly to Stripe and never reach Planitory.
  • Payout setup: for creators, a Stripe account reference and its status. Bank details are held by Stripe.
  • Basic usage events: for example that a guide page was viewed or a guide was saved, stored in our own database to show creators their statistics. We don't use advertising trackers.

The waitlist

Before launch, you can join the Planitory waitlist. We store your email address and, if you give them, your first name, country or city, whether you mainly want to explore or create, and whether you'd like to test early features. We also store when you signed up, where the signup came from (for example a link from Instagram), and the choices you ticked.

  • We use these details to tell you about early access and the launch, and to invite you to test if you asked to.
  • News and product updates are a separate, optional choice. We only send them if you ticked that box.
  • Only the Planitory team can see the list. We don't sell or share it, apart from the service providers that store it and send our emails.
  • We keep your details until Planitory launches and early access is over, or until you ask us to remove them, whichever comes first.

On the early-access page we also count visits, clicks on the “Join the waitlist” buttons and how many people start the form, to see how the page works. This uses no cookies and stores nothing on your device. We don't store your IP address: each visit is counted with a code made from it and your browser type together with a random value that is replaced every day, so the code can't be traced back to you and you can't be recognised from one day to the next. We also note the site that linked to the page or the tag in the link (for example “instagram”).

Cookies

We use one essential cookie to keep you signed in. Your browser may also store your preferred map style locally. We don't set advertising or analytics cookies.

Why we use it

  • To run your account and give you access to what you bought.
  • To process payments, pay creators and keep accounting records.
  • To send emails you need: confirmations, receipts, password resets, payout notices.
  • To keep the platform safe, handle reports and prevent fraud.

Who we share it with

  • Creators see that a sale happened, the guide, the amount and the buyer's first name and initial. They don't see your email.
  • Service providers that run parts of Planitory for us: hosting, the database, Stripe (payments and payouts), our email provider, and map services (map tiles and place search such as OpenStreetMap, OpenFreeMap and, when enabled, Google Maps Platform). When you search for a place, the search text is sent to the search provider.
  • Authorities, when the law requires it.

We don't sell personal data.

What is public

Your creator page (unless you hide it), published guides, reviews you write (with your first name) and places you mark as gems on the Gem Map are public.

How long we keep it

We keep your data while your account is open. When you delete your account, we remove your personal details. Purchase and payout records are kept, without your name or email, for as long as accounting law requires.

Your rights

You can see and edit most of your data in Profile & settings, and delete your account there. You can also ask us for a copy of your data, to correct it, to restrict or object to how we use it, and you can complain to your data protection authority.

Contact

For privacy questions or requests: contact us.