PRIVACY POLICY

RL Now, Inc., a corporation registered in Delaware, USA, is the controller of the personal data described here. Unhinged is published under the name Bad Ideas Club.

The people who run Unhinged at RL Now, Inc. can see account data through an internal tool that only they can sign in to, including the invitation records and crews described below. They use it to answer you, to fix problems and to act on reports.

651 N Broad St, Suite 201 · Middletown, DE 19709 · United States
hey@unfck.it

Your account. Your email address, an account identifier, and when the account was made. You sign in with Google or with a one-time link sent to your email — either way there is no password for us to hold or lose. Signing in with Google also puts the name and profile photo address on your Google account into the sign-in record Firebase keeps for you; Unhinged never reads or shows them. Your account is the same one used by every app RL Now, Inc. runs: if you use another of them with the same sign-in, it is one account, with one username and one list of friends.

Your invitation. Checking a code at the door happens before you have an account; to stop codes being guessed, we keep a one-way hash of your network address and a count of attempts, not the address itself. When you join, we record which code you used, when, and who it came from — the member who invited you, or that it was one we issued. That record is kept so that when something is reported we can see who vouched for whom. You are then given a few codes of your own; for each one we store whether it is unused, used or cancelled, when it was used, and who used it. Unhinged shows you your codes and whether each has been used, never who used one.

Joining. When you confirmed you are 18 or older and when you acknowledged the risk statement (the time of each, recorded by our server, on your membership and on the record of your invitation), where you set the intensity slider, your answers to the questions you are asked when you join and when you answered them — which choices you tapped, never anything typed — the date you joined and your time zone. The other members of your crew never see your answers or your intensity.

Accepting the AI part. That you accepted, when you joined, that your answers go to an AI model to write your crew’s quest: which version of that statement you accepted and when, recorded by our server on your account. If you joined before we asked it when joining, it was asked once in the app, and recorded the same way.

Your crew. Which crew you are in, when you joined it, whether you started it, and your username as it was when you joined. Invitations to a crew, sent or received, with both usernames, when each was sent and how it was answered; one copy is kept with the crew and one with the person invited. For each week: who opened the call for a quest and when, each member’s answer (in, or sitting this one out), and when the 24-hour window opened and closed and who was going.

Your crew link, if you share one. A code that stands for you, and when it was made. Anyone already in Unhinged who opens it joins your crew, and a crew is started for the two of you if you are not in one. Killing the link deletes it. Joining a crew, through someone’s crew link or through the invite code you came in on, makes you friends with everyone in it, recorded like any other friendship below.

The questions asked on the day. When a window opens, each member who is going is asked a few questions: where they are (at home, in town or near some nature), how far they can get, what they can spend, how much time they have, how they feel, and one odd question that changes from week to week. Only the choices you tap are kept, never anything typed, and only if you tap Send. They are kept with your account, one set per window, with when you sent them. Your crew is told how many of those going have answered, not who, and not what.

The quest. For each window, the quest your crew was shown, where it came from (the model, or our own list), how many answered, and when it was written. And, kept by us and never shown to anyone in the crew, a record of every quest the model wrote for your crew, shown or turned down: what the model was sent (see What the AI sees), each draft, the automated check’s verdict on it, the model’s name and how long it took. That record names nobody and carries no account identifier; we keep it to review quests after the fact and to act on reports.

Your crew’s stories, if you add to one. For each window you went on, your part of its story: the line you wrote, up to three photos, whether you ticked “OK to share me”, and when you first wrote it and last changed it. Each photo you add is turned into a pixel picture by our own server, stored with a smaller copy, and kept at a long address that cannot be guessed; the photo you uploaded is deleted as soon as that is done or fails, and one left behind anyway is removed by the daily clean-up within 25 hours. When a story closes we also record which members went and which of them told it.

Your username, picture and friends, if you use them. The username you claim, the people you are friends with, requests waiting in either direction, and the people you block and when. A block also leaves a note under the other person’s account so it can be cleaned up from either side; no one can read that note, including them.

Your profile picture, if you add one. The pixel-art version that comes back, with smaller copies of it made so it loads quickly, and earlier pictures you have replaced, so you can switch back to one. The photo you upload is deleted as soon as its pixel-art version has been saved, or as soon as the transform fails or finds you have used up your allowance; one left behind anyway is removed by a daily clean-up, so no uploaded photo is kept for more than 25 hours. We keep a count of pictures made per month so the allowance holds.

Your answer about the AI features. Whether you allowed Unhinged to send data to Google’s Gemini API, which version of that question you answered, and when — see What the AI sees.

Sign-in emails. To stop someone spamming link requests at an address, we keep a one-way hash of the address and a count.

Bug reports, if you send one. What you wrote, any screenshots you attached, and the technical details of the moment — which app and version, the screens you were on, your device and browser, and any errors the app logged. It is sent on to GitHub, where it becomes a ticket we work from, tagged with your account identifier.

Reports, if you send one or one is sent about you. Who sent it, who it is about, the reason picked, the note if one was written, and a copy of what was reported as it was at that moment, so it can still be judged if it is changed or deleted afterwards. Reports are never sent to GitHub. An email tells us one is waiting and carries none of what was reported.

Reports about a quest, if you send one. Who sent it, which crew and which week, the reason picked, the note if one was written, a copy of the quest as it was, and a pointer to our record of how that quest was written. Your crew is not told who reported it. A veto is not a report: for a veto only the number of rerolls your crew has used that week is kept, not who used them.

Notifications, if you turn them on. Your device’s notification token, whether it is a browser, an iPhone or an Android phone, your time zone, and which app it is for. That is enough to send these notifications and nothing else: someone in your crew opening the lobby, a crewmate poking you while the lobby waits on your answer (each crewmate at most once every six hours, and at most three a day in all), everyone being in and the window opening, a last call a few hours before the lobby resets if you have not answered, the lobby resetting, the next lobby becoming possible, and a new friend request. They name the crewmate, never the quest or anything anyone wrote. They can be switched off; we store whether you did, and a count of today’s pokes with who poked you in the last six hours, so the limits hold.

On your own device. In the browser’s local storage: the invitation code you entered, until you have joined with it; a crew link you opened, until Unhinged has tried it; while a sign-in link is on its way, the address it was sent to; which notification token this device registered, if you turned notifications on; and a few small display settings, such as when Unhinged was last open. None of it leaves your device, and clearing site data removes it.

The members of your crew see your username and picture, that you are in the crew, whether you are in for the week’s quest or sitting it out, and whether you were going when a window opened, how many of those going have answered the questions on the day, the quest, and how many rerolls the crew has used, never who used one or who reported a quest. They do not see your email address, your answers to the questions asked when you joined or on the day, your intensity, or who invited you.

When you open the lobby or poke someone, the crewmates who have notifications on get one that names you by your username. When you are poked, the crewmate who poked you is told whether a notification went out to you, which tells them you have notifications on when one does, and, if none did, whether that was because you had been poked recently.

Your friends can see that you are in Unhinged. When a member of Unhinged pulls people into a crew, they are offered only their friends who have joined, so a friend of yours who is in Unhinged can tell whether you are — including a friend you made in another app RL Now, Inc. runs, since the account and its friends are shared. They see your username, nothing else about your membership. Someone who is not your friend is not told.

Someone who opens your crew link, or comes in on one of your invite codes, is shown your username as the person whose crew they are joining, before they join it.

Your crew’s stories are private to the crew. The members of your crew see every part of every story, yours included: the line, the photos and your username. Nobody outside the crew can read a story, and there is no public feed and no feed for friends. A story leaves the crew only as a share card that one member makes on their own device and sends wherever they choose. That card carries their own part and the part of each member who ticked “OK to share me”, and nobody else’s words or photos. The card is drawn on that device; we never receive or keep it. A photo’s address is shown only inside the crew, but anyone a member passes it to can open it.

Nobody outside a crew can list who is in it. There is no public profile and no way to browse for people; a username can only be looked up by someone who already knows it or your email address.

No advertising identifiers, no profile built for marketing, and no analytics of any kind in Unhinged.

No location. Unhinged does not ask for it and does not store it. The question on the day about where you are is a choice between at home, in town and near some nature, and nothing more precise.

No selling or sharing. We do not sell personal information, and we do not share it for cross-context behavioural advertising, in the sense California law gives those terms or in any other sense.

Nothing is sent until you allow it. The first time you change your profile picture, Unhinged says what that sends and asks. If you say no, nothing is sent. You can withdraw permission at any time on the account screen.

Your profile picture. The photo you chose is sent to Google’s Gemini API, with example pictures of ours, and a pixel-art picture comes back. Nothing else about you goes with it: not your name, not your account identifier.

Your crew’s quest. Permission for this is given when you join: you are told that quests are written by an AI model and that your answers go to it, and you cannot join without accepting that. If you joined before we asked it when joining, Unhingedasks you once before any of your answers are used. The questions on the day still end on Send, and nothing you answer that day is sent unless you tap it. When the quest is written, Google’s Gemini API is sent, for each member going who tapped Send and has accepted, their answers to the questions on the day, their intensity, and their answers to the questions asked when they joined, all as the words of the choices tapped. With them go how many are going and the crew’s recent quests. No names, no usernames and no account identifiers are sent, and nothing about a member who did not tap Send. A second request then sends the finished quest on its own, to be checked against the limits in the terms. The quest is how Unhinged works, so there is no setting to turn this off and stay in; deleting your account stops it.

Your crew’s stories are not sent to any AI. The pixel version of a story photo is made by our own server, and your line stays in the crew.

We use Gemini’s paid tier, where Google’s terms say submitted content is not used to train their models. We do not train any model on your data ourselves.

Everyone else who handles your data for Unhinged, and what each is there for. None of them may use it for their own purposes.

• Google (Firebase) — Sign-in, the database, file storage, notifications and the servers the app runs on. Almost everything described here lives there. Their policy.
• Google (Gemini API) — Turns a photo you upload into a pixel-art profile picture, once you have allowed it, and writes and checks your crew's weekly quest from the answers members chose to send. Their policy.
• Resend — Delivers the sign-in email, when you ask for a link instead of using Google. Their policy.
• GitHub — Receives a bug report when you send one, so it becomes a ticket we can work from. Their policy.

We will hand data to a court or a regulator when we are legally obliged to, and not otherwise.

There are no advertising or analytics cookies. What is stored on your device is the sign-in session that keeps you logged in, the local storage described above, and an offline cache so Unhinged opens without a connection. All of it is necessary for Unhinged to work.

On Google Cloud infrastructure, with our own server code running in the European Union. Google, Resend and GitHub are US companies and process data in the United States and elsewhere; each publishes the transfer safeguards it relies on for data leaving the EU or UK, and those are linked above.

Your account and everything in it stay until you delete them.

Deleting your account removes, immediately and for good: your profile and username (which can then be claimed by somebody else), your answers and intensity, your answers to the questions on the day, and the times you confirmed your age and the risk statement, your pictures and the counts behind their allowance, your notification tokens and settings and the count behind the poke limits, your friendships and blocks, your bug reports and their screenshots, and every report you sent or that was sent about you. Your part of every crew story is removed, lines and photos, and your name is taken off each story’s record; the stories stay for the rest of the crew. You leave your crew, and every crew invitation you sent or received is deleted, both copies; a crew left with nobody in it is deleted. Your crew link is deleted, so it stops working. The codes you were given are deleted, so any you had not used stop working. The record of the code you joined with, and of who invited you, is deleted. The code itself stays marked as used so nobody can use it again, with your account taken off it, and your account is taken off the record of anyone you invited.

Leaving a crew, or being removed from one, takes your part out of its stories in the same way, lines and photos, while the stories stay for the others. If your crew carries on without you, you are taken off its record of the last window and of any open lobby too, and off its members’ record of who poked them. One thing stays, and it is deliberate: if you reported a bug, the ticket it became stays on our side, because it describes a defect in the app; what you wrote stays with it, and the account identifier on it points at an account that no longer exists.

The records of the quests written for your crew stay too, because they are how a quest is reviewed after the fact. They name nobody and carry no account identifier, so nothing in them points back to you once your account is gone; the answers they describe are the crew’s, as the words of the choices tapped.

You can ask for a copy of your data, ask us to correct it, ask us to delete it, ask for it in a portable form, object to a particular use, or ask us to restrict one. Email hey@unfck.it and you will get an answer within 30 days. There is no charge and no penalty for asking.

Deletion needs no email at all — the account screen does it yourself, in full, on the spot.

Where the GDPR applies, we rely on: performing our agreement with you (letting you in, running your crew, and keeping your answers and intensity so quests can fit you), your consent (notifications, photos, and sending data to the AI features), our legitimate interest in keeping the service safe and standing up (the record of who invited whom, rate limits, and acting on reports), and legal obligation where one applies. You can withdraw consent at any time without affecting what came before, and you can complain to your national data protection authority if we get this wrong.

Unhinged is for people 18 and over, and is not directed at children. Nobody can join without confirming they are 18 or older, and answering no saves nothing. If you believe someone under 18 has an account, write to us and it will be removed.

If a breach ever puts your data at risk, we will tell you and the relevant regulator within the deadlines the law sets, and we will say what actually happened rather than issue a statement about how seriously we take security.

The date at the top is when this version took effect. If what we collect ever materially changes, this page changes first. See also the terms of use.