Privacy Policy

Geocodinated is operated by GeoCodinated Indoor Maps, a sole proprietorship registered in Pakistan (“we”, “us”, “our”). We don't currently have a registered office or representative in the EU or UK — we plan to establish an EU entity in the future, and we'll update this policy when we do.

This policy applies to anyone in the European Economic Area or the UK who uses Geocodinated, because data protection law protects you based on where you are, not on where the business offering the service happens to be based.

Two different roles matter here, and it's worth being precise about which one we're in:

• For your account, billing, and the operation of the Service itself, we are the data controller — this policy describes that processing.
• For the maps, floor plans, and points of interest you create, you are the data controller and we act as a processor on your behalf. Your map content is about your venue, not about people — unless you choose to name a real person in a point-of-interest description, in which case keeping that compliant with applicable privacy law is your responsibility, not ours.

Account data. Your email address and password, held by our authentication provider (Supabase). Passwords are hashed and we never see or store them in plain text.

Billing data. If you publish a map publicly or privately, we store your billing-processor customer ID and email address, plus your subscription status, billing interval, and renewal dates. We never store your card number or other payment details — our payment processor, Paddle, handles that entirely.

Your map content. Floor plans, walkable paths, points of interest, and theme choices that you create. This is content about a venue, not personal data about people, unless you choose to include it yourself.

Analytics — no per-visitor tracking, by design. When someone views one of your published maps, we record only aggregate counters: how many visits and directions requests a map got on a given day, a coarse device-type count (mobile, desktop, or kiosk), which floors get viewed most, and which walking routes get used most. We do not keep a log of individual visits, and we do not store IP addresses, browser/user-agent strings, or any other identifier for anonymous visitors of a published map. There is nothing to re-identify a visitor from — it's aggregate counts, not events.

Cookies and local storage. We use a small, fixed set of strictly-necessary and functional cookies — see our Cookie Policy for the complete list.

Contact form. If you message us through our contact page, we receive your name, email, and message by email — this isn't stored in our database at all, so there is no separate database record of it beyond that email.

A honest note on infrastructure logs. Even though our own application never stores visitor IP addresses, the infrastructure we run on — our hosting provider, database provider, and email provider — inherently sees the IP address a request comes from at the network level, as is true of essentially any service on the internet. That's separate from, and doesn't contradict, the fact that our own application code and database never store it.

Under GDPR, we need a valid legal basis for each kind of processing. Here's how that breaks down:

We use a small number of specialist providers to run the Service. This list is complete as of the date at the top of this page, and we'll update it if it changes.

Our database, authentication, and file storage (Supabase), our transactional email (AhaSend), and our application hosting (Railway) are all hosted inside the European Economic Area (Frankfurt and Amsterdam), so there's no cross-border transfer question for any of those.

Where our other providers process data outside the EEA/UK, we rely on their own data processing agreements and appropriate safeguards (such as Standard Contractual Clauses) for that transfer. This applies in particular to Paddle, which operates as a global payment processor, and to Tawk.to when its chat is in use.

We don't show a cookie consent banner, because every cookie Geocodinated sets is strictly necessary or narrowly functional — never advertising or tracking — and doesn't legally require consent under GDPR/ePrivacy rules. See our Cookie Policy for the complete, exhaustive list of every cookie we set, what it does, and how long it lasts.

Under GDPR you have a number of rights over your personal data. Here's what each one means in practice on Geocodinated:

Right to erasure. This is genuinely self-service today, not a request-and-wait process. From Settings, you can delete your account once you have no map currently published (public or private) and no active or past-due subscription — you'll need to unpublish or cancel those first. After typing a confirmation phrase and confirming once more, we immediately and permanently delete your account, which cascades to delete every map, floor plan, point of interest, and analytics record tied to it, and every file you've uploaded. One caveat: this doesn't retroactively delete historical transaction or invoice records that Paddle, as our payment processor, keeps independently for its own legal and tax obligations — that's a standard, narrow exception under GDPR for records a processor is legally required to keep.

Right to access and portability. Settings already shows you your live billing history and every map you've published. For a fuller export of everything we hold about you, email us (below) — that part is a manual process today, not a one-click export.

Right to rectification. You can edit your map content directly in the editor at any time, and reset your password yourself from Settings. Your account email address isn't self-service to change today — email us and we'll update it for you.

Right to restrict processing and right to object. Email us to exercise either of these — objection is most relevant to the legitimate-interest processing described in Section 3 above (aggregate analytics, the functional cookie).

Automated decision-making. We don't use automated decision-making or profiling that produces legal or similarly significant effects on you.

Right to complain. You can lodge a complaint with your local data protection authority at any time — for example, your national supervisory authority if you're in the EU, or the ICO if you're in the UK — regardless of where we're based.

We aim to respond to any rights request within 30 days.

• Account, billing, and map data: kept while your account is active, and deleted immediately (with cascading deletion) when you delete your account.
• Paddle's own transaction and invoice records: retained by Paddle independently, per its own legal and tax obligations.
• Contact-form messages: not stored in our database — retained only as long as the notification email exists in our inbox; email us to have it removed.
• Analytics: tied to the map it belongs to, and deleted with it — never retained independently of the map or account.
• Cookies: see the exact durations in our Cookie Policy.

Geocodinated is for users 18 and older. Paid plans require a credit card and create a binding contract, so we require every user to have the legal capacity to enter into one. We don't knowingly collect personal data from anyone under 18, and if we learn an account belongs to someone under 18, we'll terminate and delete it.

We extend the following practices to California residents in good faith, as a matter of practice rather than a representation that we're formally regulated under the CCPA/CPRA:

• the right to know what personal data we hold about you,
• the right to request deletion of it (the same mechanism as Section 7's right to erasure, above), and
• the right not to be discriminated against — denied service or charged differently — for exercising either right.

We don't sell or share personal data as those terms are defined under California law, so there's deliberately no opt-out-of-sale mechanism to describe — we simply don't do that.

We'll update the date at the top of this page whenever we make a change. If a change is material, we'll email registered users about it. Continuing to use Geocodinated after a change takes effect means you accept the updated policy.

For privacy requests, data-subject rights, or anything else about this policy, email saad [at] geocodinated [dot] com.

For general support, use our contact page — that's a separate inbox from the address above.