Privacy Policy

Effective 5 October 2026

Revel helps you plan a day out — a show, a fair, a weekend away with the people you go with — and keeps everything about it in one place: what it costs, what is still missing, who is coming and when to leave. It is operated by Memriq Holdings, Inc. ("Memriq", "we"), which is the controller of the personal information described here.

What Revel collects

• Your account — your name and email address, and a password or your Google sign-in. One Memriq account signs you in to every Memriq service; being let in to Revel is decided separately, by invitation. If you join Revel's waiting list, we keep the email address you gave.
• Your outings — what you type or keep about each one: the event and venue, the parts to buy and their prices as you or a page stated them, the dates you are choosing between, the day's plan, your notes, and how it went. A room is kept only as a reference to your trip in Drift.
• The people going — a name, and only if you type them, an age or height (used only to check a venue's age or height rules). When you share an outing with another Memriq member, their member account and the email address you used to share it are kept on the outing.
• What you like — the food, price, pace and kinds of outing you like, and any dietary needs you state. Each item shows where it came from: you said it, or Revel learned it from an outing you kept. Revel never infers anything about your health.
• Found for you — if you connect a mailbox or calendar through Memriq Harbor, or forward a confirmation to your Revel address, Revel reads the message to propose an outing from it. The message is read and not kept: Revel keeps only the facts it proposed, with the message's sender, subject and date, and only what you choose to keep becomes part of an outing.
• Your group's plans — who is invited, who is coming, the decisions you put to the group and its answers, who brings what, and who owes whom. If you tell Revel your own must-haves for an outing — a budget ceiling, foods you avoid, access needs, timing — they are kept under your own key: the organiser sees only what the plan needs ("this option works for everyone"), never your reasons.
• Guests without a Memriq account — if an organiser invites someone by email, Revel keeps that guest's name and email address, encrypted under the organiser's key, and the guest's own answer. The guest's private link is never kept, only a fingerprint of it; it works for that one outing, lets the guest answer and vote and nothing else, and stops working the day after the outing or when the organiser withdraws it.
• Tasks, plans and ideas — the tasks Revel and Helm share for an outing (what was asked, its state, what came back and its sources); the plans you ask Revel for (what you asked for and the options it found, with their prices as read and where from — never the starting area you typed, which is used for that one request); and your someday list of experiences, with who might want to come.
• Files and reminders — tickets, confirmations and photos you attach, the reminders you ask for, and calendar events you ask Revel to add to a calendar you connected. For each ticket, Revel keeps who holds it, how it is used at the gate, and each person's own check that it opens on their phone — never a barcode or a copy of the ticket.
• On the day — the status you press for your group ("I'm here", "Running late"), a meet-up point, the phones you let Revel send alerts to, with your quiet hours, and — only if you save it — where you parked.
• What Revel may do without asking — your own choice, for each kind of action, of whether Revel may go ahead or must ask you first.
• Support and feedback — what you write to Revel's support chat, and reports you send with the feedback button.

What Revel never does

Revel never stores your location, with one exception you choose: if you save where you parked for an outing, that one spot (and any note or photo you add, with its location data removed) is kept encrypted under your own key for that outing's day only, and deleted when the day ends — no history, and a new save replaces it. Otherwise, when you ask for places nearby, your browser's location is rounded to about a kilometre, used for that one search and then discarded. "I'm here" is a word you press, not a position. Revel never holds a payment card and never buys or books anything — tickets, rooms or anything else. It sends an invitation only when the organiser presses Send, through Memriq's one email sender, and sends no other email on your behalf. It does not buy information about you and adds nothing to your outings from anywhere you did not point it at.

How it is protected

Everything you write about an outing, what you like, what Revel found for you, your group's plans, your tasks, plans and someday list, your guests' details and your parking spot are stored encrypted — under the outing owner's key, or, for your own must-haves and your parking spot, under yours. An outing is read only by you and the members you shared it with.

How it is used

• To keep your outings, show what is still missing, lay out the day and remind you of what is due.
• To suggest places and ideas that fit what you like, and to propose outings from messages you pointed it at.
• To send the reminders and alerts you turned on, and to answer your support questions.

We do not sell or share your personal information, and have not in the past twelve months.

Services that process it for us

• Railway — runs Revel's servers.
• MongoDB Atlas — stores Revel's records, in the United States.
• Neo4j Aura — stores what Revel's agents learn while helping you, kept within your account.
• OpenAI — the language model Revel uses to read a to-do or a message you pointed it at and propose an outing's facts.
• Open-Meteo — the forecast: it receives only the venue's location and the outing's date.
• Google — signs you in, if you choose Google; adds events to your Google calendar, if you ask; and finds places nearby, if you ask (it receives the rounded location and what you are looking for).
• Resend — delivers Memriq's emails, through Memriq's one sender.

How long it is kept

Your account and your outings are deleted within 30 days of your account closing. Support messages are kept for 2 years, server logs for 90 days, and billing records, if you ever have any, for 7 years. Backups can hold deleted data for up to 35 days before it is gone from them too.

If someone shared an outing with you, it belongs to them: your name and email stay on their outing until you leave it or they remove you. Leave a shared outing before closing your account if you want them gone from it. A guest's details belong to the organiser's outing and go with it; a guest's link stops working the day after the outing. A saved parking spot is deleted when that outing's day ends.

Deleting it, or getting a copy

Write to privacy@memriq.ai, or ask Revel's support chat to pass you to a person: we acknowledge within 5 business days and finish within 30 days. The same address gives you a copy of what we hold, or corrects it.

If you are in the EU or UK

We rely on the contract with you to run Revel, on our legitimate interests to keep it working and secure, and on your consent for anything else. Your information is processed in the United States under Standard Contractual Clauses. You may complain to your local data protection authority.

Changes and contact

If this policy changes, the new version is published here with its date before it takes effect. Privacy questions: privacy@memriq.ai. Anything else: hi@memriq.ai.