Privacy notice

Last updated October 2026

This is a pre-launch build. This notice describes what personal data Delapsus Resurgam Studios Ltd (“we”, “us”) processes when you use this app, and your rights under the UK GDPR and the Data Protection Act 2018. If you access the app from the EU, the EU GDPR applies in the same way.

Who runs this app

Ramified is run by Delapsus Resurgam Studios Ltd, a UK limited company based in London, United Kingdom, which is the controller of your personal data. Contact: support@ramified.app. Delapsus Resurgam Studios Ltd is a private limited company registered in England and Wales under company number 17519288. Registered office: 66 Paul Street, London, EC2A 4NA, United Kingdom. [REQUIRES REVIEW: add the ICO registration number once the company is registered with the UK Information Commissioner’s Office and has paid the data protection fee.]

What we collect

When you create an account we store: your email address, a securely hashed password (bcrypt), your chosen username and display name, and — if you sign in with Google — your Google account identifier. As you use the app we also store what you put into it: your profile bio, avatar and banner images, avatar customisation, your chosen app theme and dark/light mode, vehicles you add (make, model, year, mileage, colour, optional VRN, photos, notes), garage “Docket” entries, posts, comments, likes, messages, club memberships, marketplace listings and reviews, track diary sessions, and — if you set one — an approximate location (latitude, longitude and a place label) that you choose to share. If you use the shop, we also store the delivery address(es) you enter and any orders you place. If you order merch, we also store the personalisation you choose (the name or pseudonym for the chest, size and colour, and — for vehicle merch — which of your vehicles and which of its photos you picked; for club merch, the club and design), the order’s progress, tracking details, and any messages between you and us about the order. If you turn on the calendar feed, we store a feed version number so you can reset the private link. If you choose to, you can also tell us your age range (for example 25–34) in Settings; this is optional and is only ever used in aggregate.

Memberships and boosts

If you take out a membership or buy club boosts, we store your plan, its renewal date, whether you have turned auto-renew off, and which clubs your boosts are applied to. Your plan type is used to show a membership badge on your profile to other users; your billing details and renewal dates are only shown to you.

Photo spots and photographer listings

If you pin a photo spot we store its name, your note, its map position, the area and region worked out from that position, an optional photo, and that you added it. Other signed-in members can see all of this with your username. If you pin a spot using “I’m here”, the pin is placed at, and stores, where your device is at that moment. To name the area, the pin’s coordinates are sent to postcodes.io; no postcode is stored. If you set up a photographer listing we store your headline, the area and region you work in, your about and prices text, the services you tick, your favourite spots, up to 9 work photos, and your listing status and renewal dates. Signed-in members can see your listing while it is active; your renewal dates and billing details are only shown to you. Messages you exchange about a booking are stored like any other in-app message. Hidden photo spots are deleted 24 months after they are hidden. A draft listing is deleted 24 months after you last edit it, and a lapsed listing 24 months after it lapses, together with its work photos. If you delete your account, your spots and listing are deleted with it.

Ownership tools and Provenance Dossiers

If you use the ownership tools on a vehicle, we store what you enter there: its purchase price, date and mileage, an estimated current value, yearly insurance, tax, breakdown cover and other costs, monthly storage and finance costs and when the finance ends, your expected yearly mileage and fuel figures, MOT, tax and insurance due dates, service intervals, fuel or charging fill-ups, MOT results, and dyno and timed runs. When you buy a Provenance Dossier we build it on our servers from that vehicle’s records and the options you choose, and keep the PDF in our file storage. It is shown on a public web page at a link with a random code (ramified.app/d/ followed by the code), together with the PDF and a selection of your photos. Anyone with the link can open it without an account, and we ask search engines not to list it. Depending on your choices it shows the vehicle’s details and mileage, your username, the history entries and photos you have added (photos can show the number plate), MOT results, running costs, performance runs and track sessions. The registration and the entries you have marked private are only included if you turn them on. We count how many times the page is opened, but we do not record who opened it. We also keep a record of each purchase: which vehicle, when, the price paid (linked to the payment record), the options you chose, the link code, the date it is hosted until and how many times it was viewed or downloaded. The PDF and the details used for its web page are deleted within a day of the link ending: after 6 months, when the vehicle passes to another member through Ramified, when you mark it sold or scrapped, when you delete the vehicle or your account, or when you update the dossier (the older version is replaced). Switching the link off hides it but keeps the PDF so you can switch it back on. The purchase record stays with your account until you delete your account; payment records follow the ‘Payments’ section. Your other ownership-tool records are kept while the vehicle is in your garage and are deleted with the vehicle or when you delete your account. If you sell or transfer a vehicle to another member through Ramified, its MOT results and performance runs go to the new owner with its docket; your running costs and fuel log stay with your own archived copy of the vehicle. When you delete your account, your dossier purchase records are deleted with it.

Payments

Payments are handled by Stripe. When you pay, you enter your card details on Stripe’s own checkout page — we never see or store your card number. To set up a payment we send Stripe your account email address and an internal user ID, plus the item, price and billing interval. We keep a payment record for each purchase: what you bought, the amount and currency, billing interval, status, the Stripe references for the checkout, subscription and payment, the date it was confirmed, and when we sent your confirmation email. We also store the Stripe customer ID linked to your account. We send a confirmation email to your registered email address for every purchase (via our email provider, Resend). We keep payment records for 10 years from the date of purchase, which covers tax and accounting record-keeping requirements, and then delete them automatically. We keep only what those requirements need. If you delete your account before then, your payment records are kept for the rest of that period but are unlinked from your account and stripped of item-specific detail (such as which vehicle a promotion was for), leaving the item type, amount, date, status and Stripe references. Stripe acts as our processor when it takes a payment on our instructions, and as a separate controller for its own purposes, such as preventing fraud, anti-money-laundering and identity checks, and meeting its legal obligations; it keeps its own records of the transaction for those purposes. Stripe’s privacy policy (stripe.com/gb/privacy) explains how it uses your data. Stripe’s data protection terms with UK businesses are with its Irish company, and Stripe Payments UK, Ltd. provides regulated payment services in the UK. Stripe transfers some data to Stripe, LLC in the United States under the UK Extension to the EU–US Data Privacy Framework, with other safeguards such as standard contractual clauses as a fallback. If your billing address is outside the UK, we refund the payment in full and keep the record of it, including the billing country Stripe gives us.

Usage statistics (no cookies)

To understand how the app is used we record a simple page-view log on our own server. Each entry contains: the page path (with IDs removed), the website that referred you (domain only), your approximate country (from our hosting provider’s network edge, or the country on your profile), your device type, operating system and browser family, the time, and a visitor code. We do not record your member ID or anything else that links a page view to your account. The visitor code is a one-way hash of your IP address and browser details combined with a secret that changes every day, so it cannot be reversed and cannot link your visits across days; your IP address itself is never stored. No cookies are used for this, no data is shared with any analytics company, and if your browser sends a Global Privacy Control or Do Not Track signal we do not record anything. You can also switch it off in Settings → Share anonymous usage stats: we then record nothing while you are signed in, and nothing on that device (we remember the choice in your browser). Statistics are shown only to the app’s founders and developers, and any group of fewer than 5 people is hidden. Page-view records are kept for 3 years and then deleted automatically.

Sign-in and account security

Each time someone tries to sign in to an account we record the time, the IP address, the browser and device details, and whether it worked (and if not, why, for example a wrong password). If the email entered doesn’t belong to an account we store only a one-way hash of it, not the address. Each signed-in device also has a record with its IP address, device type and when it was last used, so you can see and sign out your devices in Settings. Sign-in records are deleted after 90 days. The app’s founder and developers can see them to help you with your account and to spot misuse. They can also send you a password reset link, set a temporary password that you must change the next time you sign in, sign you out of every device, or confirm your email address. Password reset links are emailed to you, work once and expire after 20 minutes; we store only a one-way hash of each link. If we ban an account for breaking the Terms or community rules, we keep its username and email addresses, the reason and who placed the ban for as long as the ban is in force, so the same person can’t simply sign up again, and we are told if the username is later taken by a new account. We delete the ban record when the ban is lifted. Our lawful basis for this is our legitimate interests in keeping accounts and the service secure (UK GDPR Art. 6(1)(f)).

Phone and desktop alerts

Phone and desktop alerts are off until you turn them on for a device (Settings → Notifications → Phone & desktop alerts) and allow notifications when your browser or phone asks. When you do, we store for that device: the delivery address and encryption keys your browser gives us, the device and browser description your browser reports (its user-agent), the date you turned alerts on, and which account it belongs to. We use this only to send that device the same notifications you see inside the app, and your notification settings apply to both. You can turn alerts off at any time in Settings or in your browser or phone settings. We delete a device’s record when you turn alerts off, when you sign out on that device, when your browser tells us the address is no longer valid, when you add more than 10 devices (the oldest is removed), when the device has not received an alert for 12 months, or when you delete your account. Our lawful basis is your consent (UK GDPR Art. 6(1)(a)), which you give by turning alerts on and allowing them in your browser or phone. You can withdraw it at any time by turning alerts off.

Why we can do this (legitimate interests)

Our lawful basis for these usage statistics is our legitimate interests (UK GDPR Art. 6(1)(f)): understanding which parts of the app are used so we can fix problems, improve features and keep the service secure and reliable. We have weighed this against your interests: we collect the minimum needed, never store your IP address in these statistics, use a visitor code that resets every day, hide small groups, keep records for no more than 3 years, and do not share them with anyone or use them for advertising or profiling. You have the right to object at any time — switching off ‘Share anonymous usage stats’ in Settings, or turning on Global Privacy Control or Do Not Track in your browser, stops recording immediately, or you can email support@ramified.app to object. Because these statistics are collected only to understand and improve how the app is used, and are not shared with anyone else, they also fall within the exception for statistical purposes in the Privacy and Electronic Communications Regulations 2003 (as amended by the Data (Use and Access) Act 2025), so we do not need to ask for your consent. You can object free of charge at any time in the ways set out above.

How we use it

We use your data to run the app for you: to sign you in, show you your garage, deliver posts to the right people, run community features, and — for shop orders — to arrange fulfilment. We use your email to send account emails (verification, password reset, and other transactional messages). We do not sell your personal data, we do not use it for advertising, and we do not run any behavioural profiling.

Legal bases (UK GDPR)

For running your account and delivering features you sign up for, our legal basis is performance of a contract with you (Art. 6(1)(b)). For account security, abuse prevention, integrity of the platform, and our cookieless usage statistics (see above), our basis is our legitimate interests (Art. 6(1)(f)). For optional things we might add later that need explicit permission (for example marketing emails), we will ask for your consent (Art. 6(1)(a)) and you can withdraw it at any time.

Who else sees your data

We use a small number of processors to run the app. Each is bound by their own data-protection terms:

• Supabase (Supabase Pte. Ltd., Singapore) hosts the database and file storage, in London. Its data processing addendum forms part of our agreement with it. Supabase and its sub-processors can access data from outside the UK, for example to provide support; those transfers are covered by the UK Addendum to the EU Standard Contractual Clauses in that addendum.

• Google Cloud (Google) runs the app’s servers, in Belgium, which handle your data each time you use the app, and stores our monthly backups of the database and uploaded files, in London. Our agreement is with Google Cloud EMEA Limited (Dublin, Ireland), and Google’s Cloud Data Processing Addendum forms part of it, including safeguards for any access from outside the UK.

• Google (Google LLC / Google Ireland Ltd) receives the sign-in request and returns your Google account identifier if you choose Sign in with Google.

• Calendar apps. If you add an event to your calendar or subscribe to your private Ramified calendar link, your calendar app (for example Google Calendar or Apple Calendar) fetches the event details (title, time, place, club name) from us under its own terms. The private link contains a signature instead of your login; anyone with the link can see the events you are going to, so treat it like a password. You can reset it in Settings → Notifications, which stops the old link working.

• Resend (Plus Five Five, Inc., United States) delivers our emails, so it receives your email address and the content of the emails we send you. It stores this data in the United States and keeps email and log data for 30 days. Its data processing addendum was signed when we opened our account, and transfers to the United States are covered by the Standard Contractual Clauses in it.

• Google Maps (Google LLC / Google Ireland Ltd) shows the events map. The map only loads after you tap “Load map”; when it does, your browser contacts Google directly and Google receives standard web-request information (your IP address, browser and device details) under Google’s own privacy policy. We do not send Google your account details. If you use “Near me”, your device location is used only to sort events by distance in that request and is not stored. Postcodes you search are looked up via postcodes.io (a free UK postcode lookup service) and are not stored or linked to your account. The same applies to “Near me” and postcode searches on the Photo spots map. When you drop a photo-spot pin, its coordinates are sent to postcodes.io to find the area name, without your account details. Google acts as a separate controller for the map under its Google Maps controller data protection terms, which cover transfers to the United States through the UK Extension to the EU–US Data Privacy Framework or Standard Contractual Clauses.

• Events-map listings: if you submit an event for the map, we store the details you provide (event, organiser, venue, links) and the contact email you give us so we can review it and, for featured placement, contact you about pricing. When someone taps an organiser’s “Visit website” or “Tickets” button we count the click (listing, button, and whether the person was signed in — no user ID); click counts are deleted after 3 years. Outbound links may carry tracking parameters (for example utm_source=ramified or a partner reference) so the organiser can see the visit came from us; the organiser’s own privacy policy applies on their site.

• Browser push services deliver phone and desktop alerts if you turn them on. Which one is used depends on your browser: Google (Firebase Cloud Messaging) for Chrome, Edge on Android, Samsung Internet and most Android browsers; Apple for Safari and Home Screen apps on iPhone, iPad and Mac; Mozilla for Firefox; and Microsoft for Edge on Windows. The alert’s content (its title and short text, which for a new message includes the sender’s display name and the start of the message) is encrypted on our server before it is sent, so the push service carries it without being able to read it; the push service does see the delivery address, the time of sending and technical delivery information. We have no contract with these services: each is run by your browser’s maker under its own privacy terms, and may handle that delivery information outside the UK.

• DiceBear (api.dicebear.com) serves the default illustrated avatar for new accounts. Your browser fetches those images directly; DiceBear receives standard web-request information (IP, user-agent) but not your account details.

• Google (Gemini API, generativelanguage.googleapis.com) is used to read text from receipts you choose to upload when adding a Docket entry. The image you upload is sent to Gemini for text extraction only; we do not send your account identifier or any other profile data with it. For users in the UK, Google’s terms say it does not use these images or the text it returns to improve its products, and handles them under its data processing addendum for products where Google is a processor. It keeps them briefly to detect misuse, and may process them in any country where Google has facilities.

Cookies and local storage

We use one strictly-necessary cookie (an httpOnly session cookie named __Host-sid) to keep you signed in, plus a small amount of information stored in your browser (a cached copy of your current signed-in profile, your shop cart contents, your tab-bar layout, whether you have chosen to load the map, whether you have switched off usage statistics, and when you last dismissed the “Get these on your phone” prompt). If you turn on phone or desktop alerts, your browser also installs a small background script (a service worker) from this site; it only receives and shows alerts and does not track you or store your browsing so the app feels responsive. We do not use any tracking, analytics, or advertising cookies. Our cookieless usage statistics are described above. See the Cookies notice for the full list.

How long we keep it

We keep your account data for as long as your account is active. If you delete your account (Settings → Delete account) we remove or anonymise it in line with the process described in ‘Your rights’ below. That includes the photos, videos and documents you uploaded, apart from any still used elsewhere in the app, such as the docket of a vehicle you passed on to a new owner. Payment records are kept for 10 years from the date of purchase, then deleted automatically (see ‘Payments’ above). Merch orders, with their delivery details and order messages, are kept while your account is open, for up to 10 years from the order date. If you delete your account we keep them for 6 months, so we can finish any delivery and deal with returns and faults, then delete them automatically. Usage-statistics page views and events-map click counts are deleted after 3 years. Sign-in records are deleted after 90 days, and password reset links a day after they expire. Server logs record the time of each request to the app, the address it asked for, whether it worked, a request number and, if you are signed in, your member ID (never what you typed or uploaded). Google Cloud keeps them for 30 days so we can find and fix faults. Ban records are kept while the ban is in force and deleted when it is lifted. A daily clean-up also deletes, once they are 10 years old, other records we no longer need: notifications, sign-in sessions, expired device-pairing codes, crash reports, internal audit and report logs, event reminder logs, and closed reports and deletion requests. Once a month we back up the database and uploaded files (apart from data-export downloads). Each backup is kept for 3 months and then deleted automatically, and is used only to recover the app after a fault or data loss. If you delete your account, your data stays in backups made before then until they expire, at most 3 months later. If nobody signs in to or uses your account for 2 years, we email you a warning and delete the account 30 days later, in the same way as if you had deleted it yourself, unless you sign in before then. Accounts with a paid membership still running are not deleted this way. Alert registrations for a device that has not received an alert for 12 months are deleted. Hidden photo spots and lapsed or draft photographer listings are deleted after 24 months (see ‘Photo spots and photographer listings’ above).

Where your data is stored

Your data is stored by Supabase in London. The app’s servers run on Google Cloud in Belgium, and our monthly backups are stored on Google Cloud in London. Some providers handle data outside the UK: Supabase support staff, Resend (United States), Gemini (wherever Google has facilities), Stripe (United States), Google Maps, and the push services your browser uses. The safeguard for each is set out under ‘Who else sees your data’ above. Belgium is in the EEA, which UK law treats as giving adequate protection.

Your rights

Under the UK GDPR you have the right to access your data, ask us to correct or delete it, restrict or object to processing, and receive a copy in a portable format. From Settings you can already download a copy of your data (“Download my data”) and delete your account (“Delete account”). For any other request, or to withdraw consent where consent is the basis, email us at support@ramified.app. You also have the right to complain to the UK Information Commissioner’s Office (ico.org.uk).

Merch orders

We keep merch orders, their personalisation, tracking and order messages so we can handle delivery, returns and faults. If you delete your account, your merch orders are unlinked from it and kept for 6 months, then deleted automatically.

Children

This app is not directed to children. You must be at least 13 years old to create an account, and older where local law sets a higher digital age of consent (for example 16 in parts of the EEA). Age is confirmed at sign-up via an explicit tick-box, enforced on the server, and re-checked for Google Sign-In accounts through a one-tap confirmation on first use. Accounts that do not confirm cannot use any signed-in features.

Security

Passwords are hashed with bcrypt and never stored in plain text. Sessions are held in an httpOnly, Secure, SameSite=Lax cookie. Traffic is served over HTTPS. No system is ever perfectly secure; if you believe your account has been compromised, email us at support@ramified.app.

Changes

If we change this notice we will update the “Last updated” date at the top of this page and, for material changes, notify you inside the app.

Open Ramified