Privacy policy

Who we are

Revnote is a small product built in Montreal, Quebec, Canada. We are responsible for the personal information described here under Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and Quebec's privacy legislation.

Questions, requests and complaints go to contact@revnote.app. A person reads that address.

What we collect today

If you join the waitlist

• Your email address. Required, because it is the entire point of a waitlist.
• Your car's make, model and year, if you chose to give them. Optional.
• Technical details our form processor records when it receives a submission, typically your IP address and a timestamp, used for spam filtering.

We use the email address for one thing: writing to you when there is something to buy, and occasionally when there is real news before then. The vehicle fields decide which cars we test for compatibility first. They are research, not segmentation, and we do not build a marketing profile out of them.

You gave consent by submitting the form. You can withdraw it at any time, and every email we send will have a way to do that in one click.

If you only read this website

We do not use analytics, advertising pixels, or cookies for tracking. We do not know that you were here.

Two things still happen automatically, and you should know about both. Vercel, which hosts this website, keeps standard request logs that include IP addresses, for security and troubleshooting. And this site loads its typefaces from Google Fonts, which means Google receives your IP address and browser user agent when the fonts are fetched. That request is governed by Google's own privacy policy.

What the app collects

The app is in closed testing: a small group of people have it on their phones, recording real drives. This section describes what it does today. It is still pre-release, so if the design changes this page changes with it.

What stays on your phone

• Trip records: start and end time, distance, duration, fuel used.
• GPS route traces, recorded by your phone during a trip.
• Vehicle readings from the OBD-II port: engine speed, road speed, coolant temperature, fuel trims, throttle position, battery voltage at start, diagnostic trouble codes and their freeze-frame data.
• Performance runs and dyno estimates you record.
• Your vehicle profile: make, model, year, and the mass and gearing figures the estimates need.

All of it is stored locally on the device. We do not upload your trip history or your routes wholesale, and there is no web dashboard holding a copy. The practical consequence is worth stating plainly: if you lose the phone or uninstall the app, that history goes with it. Export it if it matters to you.

What leaves your phone

Computed statistics, for insights. When the app generates an insight, it sends derived figures rather than your raw log. That means values like an average long-term fuel trim over a period, fuel consumption per 100 km, the direction and size of a trend, or a fault code together with the conditions recorded when it set. It does not mean your route, your addresses, or a second-by-second dump of the drive. Our server passes those figures to the model and does not store them; what it does keep is described under how long we keep things.

Bounding boxes, for maps. To draw a map behind a trip, the app needs map tiles. It asks Mapbox for the tiles covering a rectangle that contains the route, not for the route itself. Mapbox receives the corners of that rectangle and nothing about the path taken inside it. Mapbox's own telemetry collection is switched off in our integration.

Your question, for an AI answer. When you ask the app something, the question and the relevant computed statistics are sent to Anthropic, whose model writes the answer. We do not send your email address or your name with it. Anthropic's commercial API terms state that inputs sent through the API are not used to train their models.

A device check, alongside that question. Before our server answers, it confirms the request came from a genuine, unmodified install of the app rather than a script pointed at our endpoint. The app asks Google Play Integrity for a signed token and our server verifies it. Google receives an attestation request tied to your device and this app install. It does not receive your question or anything about your car.

Crash reports, when the app falls over. If the app crashes, a report goes to Sentry: the stack trace, the device model, the operating system version and the app version. Identifiers are scrubbed before it leaves the phone. No VIN, no GPS coordinates, no email address. It is meant to tell us where the code broke, not where you were when it did.

Permissions, and why each one is needed

• Bluetooth, to talk to the adapter. There is no other way to reach it.
• Location, for the route on a trip. On Android 11 and earlier the system also required location permission before an app could scan for Bluetooth devices at all. From Android 12 that is no longer true, and we do not ask for location on that basis.
• Background location, so that a drive records itself without you remembering to open the app. Revnote collects location data to detect and record trips automatically, even when the app is closed or not in use. That is the feature. Without it you would have to start and stop every trip by hand.

You can refuse any of these. Refusing Bluetooth leaves the app with nothing to read. Refusing location leaves you with trips that have no route on a map. Refusing background location means the app only records while you have it open on screen.

Who else touches your information

We use a small number of service providers. They process information on our instructions, for the purposes below, and for nothing else of their own.

We do not sell personal information, and we do not share it for advertising. If we are ever legally compelled to hand something over, we will comply only to the extent the law actually requires, and we will tell you unless we are forbidden to.

Information held outside Canada

Most of the providers above operate in the United States, so your information may be stored or processed outside Canada. While it is there, it is subject to the laws of that country, including lawful access requests by foreign courts and authorities. Canadian privacy law requires us to say so, and there is no way to use services like these without it being true.

How long we keep things

• Waitlist entries: until launch, and for twelve months after it, or until you ask us to delete yours, whichever comes first.
• If you unsubscribe: we delete the record. If you ask never to be contacted again, we keep your email address alone on a do-not-contact list, because the only way to honour that request is to remember it.
• App data on your device: for as long as you keep it. You control it and can delete it in the app or by uninstalling.
• Usage records on our server: a hashed device token, the type of request and the number of tokens it used. Not your question, not your vehicle statistics, not the answer. They exist to stop abuse and to keep track of what the service costs to run, and are kept for a limited period.
• The statistics sent for an AI answer: not kept by us at all. They pass through our server to the model and are gone.
• Questions sent for AI answers: held briefly by Anthropic under their standard API retention, then deleted.
• Crash reports: kept by Sentry for a limited period, then deleted.
• Server logs: a short rolling window kept by Vercel and Cloudflare for security purposes.

Your rights, and how to use them

Under PIPEDA and Quebec law you can ask us to tell you what we hold about you, give you a copy of it, correct it if it is wrong, or delete it. You can also withdraw your consent, which for a waitlist means the same thing as deletion.

Email contact@revnote.app. Write from the address you signed up with, or tell us which address to look for. We will answer within thirty days, which is the limit the law sets, and it costs nothing. If a request were ever so repetitive or broad that it carried a real cost, we would tell you before doing anything, not bill you afterwards.

Deleting a waitlist entry is immediate and total. There is no archive copy, because we never made one.

If our answer does not satisfy you, you can complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca, or, in Quebec, to the Commission d'accès à l'information du Québec. You do not need our permission to do that.

How it is protected

Traffic to this site and to our server is encrypted in transit. Data on your phone is protected by the phone's own storage protections, which is another way of saying that a device passcode is doing real work. The device token in our usage records is hashed, so a record cannot be walked back to a phone. Access to the waitlist is limited to the people who need it, which today is a very small number of people.

No system is perfect and anyone who tells you otherwise is selling something. If a breach ever creates a real risk of significant harm to you, we will notify you and the regulator, as the law requires.

Children

Revnote is meant for people who drive. It is not directed at children, and we do not knowingly collect information from anyone under thirteen. If you believe a child has given us something, write to us and we will delete it.

Changes to this policy

This page will change as the product does, particularly as the app moves from a closed test to a public release. The date at the top always shows the last revision. If a change materially affects what we do with information we already hold, we will email the waitlist and the testers rather than quietly editing the page.

Contact

Revnote, Montreal, Quebec, Canada.
contact@revnote.app