Privacy Notice
Last updated: 8 June 2026 · Version 1.1
🌿 The short version
- We collect the minimum. Your email + a password (for login), and whatever trips, gear, and lists you create yourself.
- Body metrics never leave your browser. Age, weight, height, fitness level for the calorie calculator are stored only in your browser's local storage. We can't see them.
- Your data stays in the EU. Our servers and backups are in Germany and Finland. No US-based services.
- Backups are encrypted. Nightly, with a key that only the developer holds. No third party can read them.
- No tracking, no ads, no analytics services. We count page views and form outcomes as anonymous totals; we don't profile you.
- You can leave whenever. Settings → Delete Account removes everything immediately. Backups age out within ~38 days.
Who runs Trekstasy
Trekstasy is a trip planner and gear organizer, developed and run by Ørneklo — product designers making outdoor gear and apps for hiking, camping, and fishing.
Under EU data protection law (GDPR), the data controller for everything you submit is Claus Erichsen, developer at Ørneklo. If Ørneklo is later registered as a formal legal entity, this notice will be updated accordingly.
Contact for data matters: privacy@trekstasy.com. For general enquiries and other ways to reach us, see our Contact page.
What data we collect, and why
When you sign up
We store your email (for login + password reset),
a username + optional display name, and a bcrypt-hashed password (we never see your plaintext password).
You can opt in to hearing about Ørneklo's own products — both in-app suggestions and marketing emails — via the "Product News from Ørneklo" switch in Settings; it's OFF by default.
Why: to give you an account that works across sessions and devices.
When you create items, lists, packs, or trips
We store everything you type or select: item names, weights, volumes,
packing-list contents, trip names + dates + notes, waypoint coordinates,
and the route map image (if you draw one). All of this is keyed to your
account and only visible to you (unless you choose to share).
Why: this is the service you signed up for.
When you contribute to the public gear catalog
Logged-in users can offer custom items to the shared catalog; approved Reviewer accounts can include a rating, a written
review, and a product photo. An admin checks each submission before anything is published.
A published review is shown with your username; when you
delete your account it stays in the catalog without your
name unless you tick "also remove" in the deletion dialog. A published photo is donated to the catalog anonymously (it
carries no metadata — location data is stripped on upload) and stays in the catalog even if you delete your account;
your private copy remains your own. Both points are also shown at the moment you submit.
Why: published reviews and photos are the feature — attribution
makes reviews trustworthy, and donated photos keep the catalog complete.
Applying to become a Reviewer (Settings) stores your
application with your account: your motivation text, your answer to the brand-affiliation
question, and your selected interests. An admin reads it personally to decide. It's included
in your data export and deleted with your account.
Why: we hand-pick reviewers, and the affiliation answer keeps
published reviews trustworthy.
When you publish to the Trekstasy community
Selected account types (Reviewers, Authors, admins) can publish content — such as trip
reports with photos — to the community, visible to signed-in members. Publishing is an
explicit, consented act: it creates a separate copy of the content, shown with your username, and
featured items may also appear on our public pages. Photos never carry location metadata
(it is stripped on upload). You can unpublish a copy at any
time while the original exists. If you delete your
account, published copies remain but are anonymized — your name is removed at
that moment (like donated catalog photos). The deletion screen reminds you if you still
have published posts; unpublish them first — or email us — if you want them gone entirely.
Your published posts are included in your data export while your name is on them. An
optional author profile (avatar, experience level,
short bio) is self-entered, shown beside your published content, exported with your data,
and deleted with your account.
Why: the community only works if shared content is durable —
a shared trip report shouldn't vanish and leave holes; anonymization protects you while
keeping the community whole. Consent basis: your explicit publish action (Art. 6(1)(a)).
When you share with friends or join a group trip
Friend connections, share links, and trip-group messages are stored so
the people you shared with can see what you shared. If you join a shared
trip and attach one of your packs, the trip's organizer can see your
packing status — whether you've packed and which essentials (food, water,
shelter, fuel) are present — so they can coordinate the group. Your body
profile is never involved: it stays on your own device and is never sent
to us, so no one else can see it.
Why: to make sharing possible. We don't show your shares to anyone you didn't share with.
When you use the calorie / readiness calculator
Your body-metric inputs — gender, age, weight, height, fitness level — are stored only in your browser's local storage.
They are never sent to our server. The calculator runs entirely in your browser.
Clearing your browser data clears these inputs. They don't live anywhere else.
Why: these are sensitive enough that we'd rather not handle them at all.
When you save a list anonymously (no account)
If you use the "save anonymously" feature, we store the list + a hash of your
IP address (so we can apply rate limits and prevent abuse). We do NOT store your
IP itself, just a one-way hash. Anonymous lists are automatically deleted after
12 months of inactivity.
Why: to let you share a list without creating an account.
When you visit any page
We record an aggregate page view: which URL, which date, plus a one-day
hash of your browser fingerprint (used to count unique visitors per day,
not across days). This is not linked to your account.
Why: to know roughly how many people use the service and which pages get traffic. It helps us decide what to build next.
When you use a form (e.g. sign up or log in)
We keep aggregate, non-identifying counts of form outcomes — for example,
how many sign-up or log-in attempts are submitted, succeed, or fail (with a
generic reason such as "email already in use"), together with a broad device
class (mobile or desktop) and the interface language. These are plain tallies:
they carry no IP address, account id, or anything that
identifies you, and we do not track your journey from one page to the next.
Why: much of our raw page traffic is automated bots. Counting real form attempts lets us tell genuine usage apart from bot noise and notice if sign-up is actually broken for people on a particular device or language.
For a failed sign-up or log-in, we additionally keep a short-lived
security/diagnostic record for up to 90 days containing a one-way hash of
your IP (not the IP itself), the type of failure, and simple yes/no results
of automatic checks — for example "was an account already registered for that
email?" or "was that username taken?". We store the yes/no answer, never the
email address, username, or password you typed.
Why: to tell an existing user who is locked out apart from a typo or an automated credential-guessing bot, and to spot sign-up steps that trip people up — without keeping anything that identifies you.
What we don't collect
- No third-party analytics (no Google Analytics, no Mixpanel, no Heap, nothing).
- No advertising trackers, no fingerprinting libraries.
- No payment data — the app is free.
- No biometric data on our server.
- No location data automatically — only the waypoints you add yourself.
Where your data lives
Live application + database: Hetzner Online GmbH, datacenter in Falkenstein, Germany (EU).
Backups: Hetzner Storage Box, datacenter in Falkenstein, Germany (EU). Backups are encrypted with a key that lives only on the developer's machine + paper copies in physically separated locations. Even if a backup were stolen, it would be unreadable.
Honesty note on encryption at rest: the live database on our Hetzner Cloud Server is not encrypted at the disk level — Hetzner doesn't provide that by default and we haven't enabled LUKS on top of it (it would add real operational pain for a relatively small risk at our scale). Hetzner's datacenter has independent physical security audits, and our backups are properly encrypted. We'd rather state this clearly than imply protection we don't have.
Email delivery: Domeneshop AS, Norway (EU) — only for the verification email and password-reset email that the app sends to you.
All processing stays in the EEA. No US-based vendors, no transfers to third countries. We've signed standard Data Processing Agreements with Hetzner and Domeneshop.
How long we keep your data
| Data | How long |
|---|---|
| Your account + everything you created | For the lifetime of the account. Deleted immediately when you delete the account. |
| Login sessions | 30 days (sliding) |
| Email verification + password reset tokens | 24h / 1h respectively |
| Anonymous lists (no account) | 12 months from last access, then auto-deleted |
| Aggregated page-view counts | 24 months |
| Encrypted backups | 28 days rolling, plus up to ~10 days in immutable Hetzner snapshots |
If you delete your account: your data is gone from our live database instantly. It will continue to exist in encrypted backups for up to ~38 days, after which it's gone from all storage. This is the usual GDPR "without undue delay" trade-off given that real backups are required for disaster recovery.
Your rights under GDPR
Under EU and Norwegian law, you have the right to:
- See your data — Settings → Download all my data gives you a complete JSON export of everything tied to your account (profile, items, packs, lists, trips, friends, messages, reminders and more). For anything else, email privacy@trekstasy.com and we'll respond within 30 days.
- Correct your data — Settings lets you edit every editable field. For anything only we can change, email contact@trekstasy.com.
- Delete your account — Settings → Delete Account removes everything immediately. Backups age out within ~38 days.
- Portability — exports are in JSON, a standard machine-readable format. You can take your data to any other service that accepts JSON imports.
- Object to processing — Ørneklo marketing (in-app product suggestions and emails) is opt-in only (default OFF), controlled by the "Product News" switch in Settings. For the pseudonymous page-view counting, email us and we'll discuss.
- Complain to Datatilsynet — Norway's data protection authority. datatilsynet.no. You can do this if you believe we've mishandled your data; we encourage you to email us first so we can fix it.
Response time: we aim to respond to data-rights requests within 30 days, usually faster.
Cookies & local storage
Session cookie: when you log in we set one cookie containing a random session ID. It expires after 30 days. This is strictly necessary for the login system to work, so no separate consent is required under ePrivacy / GDPR.
Local storage: the calorie calculator keeps your body-metric inputs in your browser's local storage so you don't have to re-enter them. This data never leaves your browser. You can clear it via your browser settings.
No advertising or tracking cookies. Ever.
Who else sees your data
Hetzner (our hosting provider) and Domeneshop (our domain + email provider) technically have access to the disks/servers where your data lives — they host the infrastructure. They have signed contracts (Data Processing Agreements) prohibiting them from accessing the data for any purpose other than operating the infrastructure for us.
Other users: can see only what you've explicitly shared with them (a trip you invited them to, a list you sent them, etc.).
Nobody else. We don't sell or trade data. We don't provide it to analytics or advertising networks. We've never received a government request for user data; if we did, we'd push back where lawful and notify you where lawful.
Ørneklo's own products
As Ørneklo grows, you may start to see our own outdoor gear featured inside the app — camping, hiking, wildlife, fishing, and hunting equipment only. To be clear about what this is and isn't:
- It's first-party — Ørneklo showing its own products, not paid placements from outside advertisers.
- It involves no third-party ad networks, no trackers, and no profiling.
- It never means sharing your data with anyone — the same promise as the rest of this notice.
- It's off by default — the "Product News from Ørneklo" switch in Settings controls it (the same switch as marketing emails). Nothing appears in the app, and no emails are sent, unless you turn it on.
Our first products are still in development.
Free-text content (notes, list names, messages)
You can type free text into many fields (item notes, trip notes, packing list names, messages to friends, etc.). We do not automatically scan or analyse any of this content. No AI moderation, no keyword scanning, no automated profiling.
Publicly shared lists carry an in-app Report button. For abusive or illegal content anywhere else — a trip you were invited to, a message, anything shared with you — email contact@trekstasy.com. A human reviews every report manually, and we can remove content or suspend accounts that break our Terms of Service.
When you use the contact form
The contact form sends your name, email, and message to us by email so we can reply. We keep that correspondence only as long as needed to handle your request.
The app itself stores only non-identifying ticket metadata — a reference number, the subject you chose, any catalog item tags, the date, and whether it's open or closed. It does not store your name, email, or message. The ticket number is just so you can quote it in any follow-up.
Children
Trekstasy is intended for adults planning their own trips. We do not knowingly collect data from children under 13. If you're a parent and believe your child has created an account, email contact@trekstasy.com and we'll delete it.
If the service is sold or transferred
If Trekstasy — or Ørneklo's business or its assets — is ever acquired, merged, or sold, your data may be transferred to the new owner as part of that transaction.
If that happens, the new owner will be bound to honour a privacy notice at least as protective as this one, or will notify you of any changes before they take effect. We will tell you in advance (in-app and by email) so you have time to export your data or delete your account first if you'd prefer not to move with it. A change of ownership does not remove your GDPR rights — the new owner inherits the same legal obligations.
Changes to this notice
When we make material changes (new processors, new data types, changed retention), we'll update the "Last updated" date at the top and notify logged-in users via in-app message. Cosmetic updates (typo fixes, clarifications) don't trigger notifications.
Get in touch
For privacy and data-rights requests, email privacy@trekstasy.com — we respond within 30 days. For all other channels, see our Contact page.