Privacy Policy

Version 1.0 · 10 August 2026 · Applies to nightrewind.com and the NightRewind mobile app

The short version. NightRewind builds your recap on your phone. Your location history, your photos, your contacts and your payment notifications are read on the device and stay there. We do not receive them, we cannot see them, and we do not sell or share them with advertisers. If you turn on cloud sync or the AI digest, a strictly limited set of information leaves your phone — and this policy says exactly what.

1. Who we are

NightRewind is operated by Quickin Limited, a company registered in England and Wales (company number 06567159), registered office 13 Alexander Road, Birmingham, England, B27 6ER. Quickin Limited is the data controller for the limited information described in this policy.

Questions, requests or complaints: hello@nightrewind.com.

Quickin Limited is the trading company. Some of the development tooling used to build NightRewind is provided to Quickin by Window Insulation Ltd as an internal service. Window Insulation Ltd is not a controller of your NightRewind data and does not use it for its own purposes. Because it administers the cloud infrastructure that hosts the app, including the Google Cloud organisation containing its Firebase project, its system administrators do hold technical access to it, so it acts as a processor on Quickin’s instructions. We would rather state that plainly than claim a separation the infrastructure does not have.

2. Current status of the product

NightRewind has not yet been released. As of the date above, this website is a pre-launch page and the app is in private development. That means:

No app user data exists yet, because there are no app users yet.
Cloud sync is not switched on. There is no live backend holding recaps.
The AI digest is not live — nothing has ever been sent to a language model.

Sections 4 onwards describe how the app will behave at launch, so you can read it before you install anything. This policy will be reissued, with a new version number, on the day the app is published.

3. The website

This site is deliberately plain. It serves static pages and does not set advertising or cross-site tracking cookies. If you give us an email address to join the waitlist, we use it only to tell you when NightRewind launches, and you can ask us to delete it at any time.

Our host records standard server logs (IP address, timestamp, page requested, user agent) for security and to keep the site running. Our lawful basis is legitimate interests.

4. What the app reads on your phone

A recap covers a single night: from 5 PM to the moment you open it. A night is filed under the evening it began, so 2:30 AM belongs to the night before rather than the morning you are reading about it.

To reconstruct that window the app reads the following, only with permissions you grant individually, and only on the device:

Source	What is read	What is deliberately not read
Location	Periodic location samples, grouped into the places you stopped and how long you stayed. Background location is needed because a night has to be reconstructed after it happened.	We do not stream your live position anywhere, and there is no continuous tracking log sent off the device.
Photos	The timestamps only, so photos can be grouped by the place you were at.	The app does not read the image data. Your pictures are never opened, uploaded or analysed.
Contacts	Whether any new contacts were saved during the window, so the recap can say "you met 3 people".	Contact names never leave the device, and never appear on a shareable card. See section 6.
Payment notifications (Android)	Bank and card notifications that arrived during the window, parsed on the device for amount and merchant, to total your spending.	We have no connection to your bank, no access to your accounts, and cannot see balances, statements or anything outside those notifications.

Every one of these is optional. Each is requested separately, with a reason, at the moment it is first needed — never all at once on first launch. If you decline one, the app still works; you get a less complete recap, and nothing breaks.

Our lawful basis for reading any of this is your consent, which you can withdraw at any time in your device settings.

5. Where your recap is stored

Your recaps are held on your phone. Deleting the app deletes them.

If you sign in and enable cloud sync — a paid feature, and off by default — your recaps are stored in your own private area of our database, keyed to your account and readable only by you. Signing in is never required to get a recap.

6. What actually leaves your phone

This is the part worth reading closely. There are only four routes off the device.

a. Cloud sync (optional, paid, off by default)

Your recap data, written to your own private path in Google Cloud Firestore. Nobody else's account can read it.

b. The AI digest (optional, paid)

The digest is the short paragraph at the top of your recap. To write it, a prompt is sent to Google's Gemini model containing aggregates and venue names only: counts, totals, times and how long you stayed somewhere.

Contact names, photos and photo content are never included in that prompt. This is enforced in the code, not just promised in a document: an automated test fails the build if a contact name can reach the prompt. The same rule applies, more strictly, to the holiday digest, because a trip aggregates weeks of your life.

c. Anything you choose to share

The Recap Card and the Trip Card are images you can post. They carry aggregates only — counts and totals. No addresses, no contact names, no photos. The Trip Card is stricter still: it drops even the number of people you met, because that is a fact about other people and a trip card tends to get posted publicly.

d. Crash reports and basic analytics

If the app crashes we receive a diagnostic report through Firebase Crashlytics, and we collect aggregate usage statistics such as which screens are opened. These contain no location history, no photos, no contacts and no spending detail. Lawful basis: legitimate interests in keeping the app working.

7. Advertising

The free tier may show advertising. Where it does, we hold ourselves to three rules: never on a shareable card, never above the main content, and never at all for paying subscribers. We do not pass your recap data to advertising networks, and we do not sell personal data.

8. Payments

Subscriptions and the Trip Pass are billed by Google Play, not by us. We never see or hold your card details. Google tells us only whether an entitlement is active.

9. Who else is involved

Provider	What for
Google (Firebase, Firestore, Crashlytics, Analytics)	Optional cloud sync, crash diagnostics, aggregate usage statistics
Google (Gemini)	The optional AI digest, on the limited payload in section 6b
Google Play	Billing for subscriptions and the Trip Pass
Hostinger	Hosting this website

Some of these providers operate outside the UK. Where personal data is transferred abroad it is protected by the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.

10. How long we keep things

On your phone: until you delete the recap or uninstall the app.
Cloud sync: until you delete the recap or close your account, after which it is removed.
Waitlist email: until launch, or until you ask us to remove it.
Crash reports: in line with Firebase's retention defaults.

11. Your rights

Under UK data protection law you have the right to access, correct, delete or port your personal data, to object to or restrict our processing, and to withdraw consent at any time.

Because most of what NightRewind touches never leaves your phone, you already hold it directly: uninstalling the app erases it, and device settings let you revoke any permission immediately. For anything we hold, email hello@nightrewind.com and we will respond within one month.

You can also complain to the Information Commissioner's Office at ico.org.uk, though we would rather you gave us the chance to put it right first.

12. Children

NightRewind is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has used the app, contact us and we will delete anything we hold.

13. Changes

We will update this policy as the product develops, and the version number and date at the top will change with it. If a change materially affects how your data is handled we will tell you in the app before it takes effect — not quietly, and not afterwards.