Privacy policy

Aurotind AS (in formation) is the controller for the personal data in Rambleto. Write to support@rambleto.com about anything in this policy, or to use your rights.

• Your account: email address, name and profile picture. The picture comes from Google if you sign in with Google, or from an upload; Sign in with Apple shares no picture. We use these to sign you in and to show the people you travel with who is who.
• Sign-in methods: which providers you have linked, the public part of any passkey, and your login sessions. Rambleto stores no passwords.
• What you add to a trip: trips, days, stops and notes, places, flights, bookings and links, packing lists, files, comments, ratings, costs and payments, alternatives and votes, and who is on the trip with which role.
• Your Saved places: the places you keep on your account for later, with any note and list you give them. Only you see them. A map link you paste or share to Rambleto is read by our server to find the place; Rambleto reads your clipboard only when you tap Paste a copied map link, or where your browser already allows it, and only a map link found there is sent.
• Your Vipps number, if you add one, so the people who owe you can pay you. It is shown only to a person who pays you, on their own settle-up row.
• Your settings: language, theme, units, currency, walking pace and similar choices.
• Technical data: when you use Rambleto, our hosting provider records technical logs such as IP address, time, the address requested and the browser. We use them to run the service, find errors and stop abuse. To limit sign-in emails we keep short-lived counters per IP address and per hashed email address.
• Statistics: we count page visits with Vercel Web Analytics. It sets no cookies and does not follow you across sites.

When you use the locate button, directions or Behind schedule, your position is used in your browser only. It is never sent to Rambleto's servers and never stored. When the app measures a bus or train route, it sends HERE the positions of two stops on your plan and a time, never where you are.

Tickets you add under Tickets (boarding passes, entry tickets, Wallet passes) are encrypted in your browser before they are uploaded. Rambleto's servers and file storage hold only the encrypted file, an encrypted title, type and name, and keys that are themselves encrypted. We cannot read them, and we cannot recover them for you.

Each ticket can be opened only by the person who added it and the travellers they chose. Your key is protected by your passkey and by a recovery key that only you have. If you lose both, nobody can open your tickets again. Without the key the server still knows that a ticket exists, which trip and stop or flight it belongs to, who added it, who it is shared with, its size and when it was added.

An honest limit: Rambleto is a web app, so the code that encrypts your tickets is sent by our server each time you open it. If that server were ever compromised, the code could be changed. Native apps share this risk through their updates; we keep the code small and checked.

So you can show a ticket offline, the encrypted copies are also kept on your device. If you choose "Stay unlocked on this device", your key is stored in that browser in a form that can be used there but not copied out. Signing out removes all of it from the device. Tickets are deleted when the person who added them deletes them or their account, or when the trip is deleted. Your data export includes your tickets, still encrypted, with instructions for opening them with your recovery key.

• Contract (GDPR art. 6(1)(b)): your account, your trips, sharing, costs and everything else you ask Rambleto to do.
• Legitimate interest (art. 6(1)(f)): security, technical logs, limits against abuse, anonymous visit statistics, and keeping the money records of a deleted account on trips other people share, so their balances stay right.
• Consent (art. 6(1)(a)): cookies from Stay22 and Booking.com on the stay page. You can say no and still see hotels, and you can withdraw consent at any time.

We use these providers. Each gets only what its part of the service needs.

The people on a trip see what is shared on it: the plan, comments, costs, files and who is on the trip. Only the trip's owner sees members' email addresses. If you share a public inspiration link, the page shows a cleaned copy of the trip without people, costs, files, comments, flights or dates.

We don't sell personal data and there are no ads in Rambleto.

Our database, files and server functions run in Frankfurt, in the EU. Some providers are based outside the EU/EEA, for example in the United States. Where data leaves the EU/EEA, we rely on the safeguards the GDPR requires, such as the EU–US Data Privacy Framework or the EU's standard contractual clauses.

Rambleto uses only the cookies it needs to work. Stay22 and Booking.com cookies load only after you accept them on the stay page.

On your device Rambleto also keeps copies of up to 20 trips for offline reading, unsaved timeline changes, and small choices such as a dismissed hint or your answer on the stay page. Offline copies are wiped when you log out or delete your account.

• Your account and settings: until you delete your account.
• Trips: until the owner deletes the trip. When you delete your account, trips only you are in are deleted, and shared trips pass to someone else on them.
• On trips other people share, a deleted account's costs, payments and files stay, shown as Deleted account with the name removed. Its comments are deleted.
• Sign-in links expire after 24 hours. Sessions end after 30 days without use, or when you log out.
• Read notifications are deleted after 90 days. Unfinished uploads are removed daily.
• Technical logs are kept for a short time by our hosting provider.

• Access and portability: Download my data in Account settings gives you everything we hold about you as one JSON file.
• Deletion: Delete my account in Account settings removes your account at once.
• Rectification: change your name and picture in Account settings. For anything else, write to us.
• Restriction and objection: you can ask us to limit or stop processing based on legitimate interest.
• Withdrawing consent: clear Rambleto's site data in your browser and the stay page asks again; Stay22's and Booking.com's own cookies are removed in your browser's settings. You can also write to us.

Write to support@rambleto.com and we will answer within a month. If you think we handle your data wrongly, you can complain to Datatilsynet, the Norwegian Data Protection Authority (datatilsynet.no).

Rambleto is not meant for children under 13 to use on their own. A trip can count children as travellers without them having an account.

When we change how we handle personal data, we update this page and the date at the top. If a change matters for you, we will also tell you in the app.