Privacy Policy

Last updated: October 1, 2026

InOrOut (“we”, “us”, or “our”) operates the InOrOut mobile application. This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our app.

Data Controller

The data controller responsible for your personal data is:

• Screaming in Digital
• c/o Thomas Steen-Larsen, Meierlia 15, 3744 Skien, Norway
• Email: support@inorout.no

The full company details are on the Legal Notice page.

Data We Collect

• Account information: email address, first name, surname, optional phone number
• Authentication data: hashed password (email accounts), and the identifier your Google or Apple account has for InOrOut when you sign in with one — never a Google or Apple password or token
• Group and event data: groups you create or join, events, attendance records
• Device tokens: for push notifications (Firebase Cloud Messaging)
• Chat messages: messages sent in group chats
• Message reports: when you report a chat message to a group’s admins, we store your reason, any note you write, and a copy of the reported message
• Forum posts: the title and text of questions and suggestions you submit to a team’s Forum
• Content reports: when you report a Forum post, we store your reason, any note you write, and a copy of the post’s title and text as it stood when you reported it. That copy is kept even if the post is later deleted, so the report can still be judged. Deleting your account takes your own reports with it; a report about someone whose account is deleted stays, without their name, until the retention period below ends
• Blocked members: when you block another member, we store that you did and when, so their chat messages and Forum posts can be left out of what you see. The person you blocked is not told and cannot see it, and the list is deleted with your account — or with theirs
• Uploaded images: your profile picture, images you add to a poll question, and a team’s profile image and Discover banner. These are held in a private Neon Object Storage bucket in Europe and served through signed links that expire within a week
• Usage data: participation history, preferences, time zone, language preference
• Location data: only when you use a location feature — the location picker, or Discover, which searches from your device’s position for teams and events near you. Nothing is tracked in the background
• Contacts: only when you choose “invite from contacts”. Your phone’s own contact picker opens and returns the single contact you pick; the app holds no contacts permission and never reads or stores your address book, and only the invite you then send is kept
• Device calendar: only if you turn on calendar sync. The app writes your events’ titles, times and venues into the calendar you chose on your phone and keeps them updated; nothing is read back except to keep those entries in step
• Managed members and guests: a team admin can add a member without an account (name, optional email and phone number) or record guests a member brings. That data belongs to the team and is subject to the same rights below, and the admin is responsible for having permission to enter it. A managed member cannot sign in, so those rights are exercised through the team’s admins, who can correct or delete the member, or by contacting us. Deleting a team deletes its managed members
• Device information: platform (Android/iOS) for push notification delivery
• Technical data: the IP address and device type of each request reach our server logs, and after failed sign-ins the network they came from is kept for up to a day, to stop password guessing
• Acceptance record: the version of the terms and this privacy policy you accepted, and when. Accounts created before this record existed have none, and it is never inferred

Legal Basis for Processing

We process your personal data under the following legal bases (GDPR Article 6):

• Contract performance — processing necessary to provide the service you signed up for (account management, group coordination, event scheduling, chat)
• Consent — push notifications and optional features (you can withdraw consent at any time via app settings)
• Legitimate interest — service security, fraud prevention, service improvement, and crash reporting. A crash report carries no name, email address or account identifier; it is on by default and can be switched off per device under Profile → Security → Diagnostics

How We Use Your Data

• Provide and maintain the service
• Send push notifications about events, reminders, and messages
• Authenticate your identity
• Enable group coordination and scheduling features
• Process subscription payments (via RevenueCat)
• Translate user-written content into the languages you have chosen to read, where the team’s plan includes it (see Third-Party Services below)

Data Storage & Security

Your data is stored on servers located in Europe. We use PostgreSQL databases with encryption in transit (TLS). Passwords are hashed with bcrypt and never stored in plain text. Authentication tokens are stored securely on your device using platform-native secure storage (iOS Keychain / Android Keystore).

Data Sharing

We do not sell your personal data. We share data only with:

• Firebase (Google) — for push notifications, crash reporting, remote configuration and app attestation (checking that requests come from a genuine copy of the app). Crash reporting can be switched off per device under Profile → Security → Diagnostics. Push notifications travel through Google’s and Apple’s push services: a chat notification shows who wrote and the start of the message, unless you switch off Show message previews for that device, in which case it names only the team and how many messages are waiting
• Brevo — for sending sign-up confirmation, password reset and account emails, invitations to a team, and feedback you send us
• Neon — for database hosting and storage of uploaded images, in Europe
• Your group members — your name, attendance status, and chat messages are visible to members of groups you join, subject to your privacy settings and the group’s own settings. You can choose, per kind of group, to withhold your contact details from fellow members or to be left out of member and participant lists entirely; group admins always see their members. People who can invite to a team — its admins, and members of a team that lets members invite — can find you by name or by your exact email address to invite you, unless you turn off being findable in member search
• Moderators — a report about you, or one you file, reaches the team’s admins and the InOrOut team, who can see reported content from any team in order to act on it

Third-Party Services

We use the following third-party services that may process your data:

About automatic translation

Where a team’s plan includes it, the text members write can be translated automatically into the languages a reader has chosen under Profile → Culture: announcements, events and their individual occurrences, the team’s own description and the captions on its links, activity plannings and their date options, polls with their questions and answer options, and Forum topics and posts. To do that, the text of that content is sent to the Anthropic Claude API. Only the text being translated is sent, with the languages involved — the language to translate into, and the languages its author reads, which help recognise what it was written in — not your name, email address or account identifiers. How Anthropic handles that text is governed by their own terms and privacy policy, linked in the table above.

Turning off See translations under Profile → Culture stops machine translation for you completely: no text is sent on your behalf, and you always see what the author wrote. Listing a language under Languages you read does the same for anything written in that language. Both settings describe you as a reader and are never tier-gated. Note that they govern what is translated for you — text you write in a team whose plan includes translation may still be translated for other members who have translations switched on.

International Data Transfers

Your data is primarily stored and processed in Europe. Some third-party services (Firebase, Google, RevenueCat, Anthropic) may process data in the United States. These transfers are protected by EU Standard Contractual Clauses (SCCs) and the EU-U.S. Data Privacy Framework where applicable.

Cookies & Tracking

The InOrOut mobile app does not use cookies. We do not use analytics tracking, fingerprinting, advertising identifiers, or any hidden identifiers. The app shows no ads of any kind.

Children’s Privacy

InOrOut is not directed at children under 13 years of age. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with personal data, please contact us and we will promptly delete it.

Your Rights (GDPR)

Under the General Data Protection Regulation, you have the right to:

• Access — request a copy of your personal data, or export it yourself at any time (Profile → Security → Your Data)
• Rectification — correct inaccurate data via your profile settings
• Erasure — delete your account and your personal data. What you created for your teams and groups stays with them, without your name (see Data Retention below)
• Data portability — export your data in JSON format (Profile → Security → Your Data)
• Restrict processing — request that we limit how we use your data
• Object — object to processing based on legitimate interest
• Withdraw consent — disable notifications at any time via app settings

To exercise your rights, use the in-app features or contact us at the email below. We will respond within 30 days.

Data Retention

We retain your data for as long as your account is active. When you delete your account, it is removed from the live service immediately and all personal data is permanently gone from every copy within 30 days.

Deleting your account erases what is about you: your profile and sign-ins, your team and group memberships, your RSVPs, attendance and check-ins, your votes and poll answers, your prize draw wins, your Forum upvotes, your chat messages and the reports you made. A closed poll or planning, or a past prize draw, loses your part in it, and a prize-draw result the team announced names you as a former member instead. Invitations sent to your email address are deleted too.

Two things about you outlive your account, because a team needs them to stay safe. Reports made about you stay, without your name or picture, for 12 months after the deletion. And if a team blocked you, the block stays for 12 months, kept under a one-way code made from your email address with a secret key — not the address itself — so that signing up again with the same address does not undo it.

What you created for your teams and groups stays with them, without your name: events, activity plannings and the rules that schedule them, polls, announcements, calendar subscriptions, prize draws, and the Forum posts members could already read, which then show as from a former member. Your Forum submissions that were still waiting for review, were declined or were removed are deleted with your account.

The periods below apply while your account exists:

• Chat messages: deleted 12 months after they are sent, on every plan — a plan’s chat-history setting decides how far back you can read, not how long we keep them. A message report that an admin has decided is deleted on the same schedule, counted from the decision; a report still awaiting a decision is kept until it is answered. A report about someone whose account is deleted is kept, without their name, for 12 months after the deletion, whether or not it was answered
• Translations: cached so the same text is not sent for translation twice; the cache is cleared when the underlying content is deleted
• Password reset codes: 15 minutes
• Email confirmation codes: 24 hours
• QR sign-in requests: 3 minutes
• Sign-in sessions: up to 7 days without use, after which you must sign in again
• Push notification tokens: removed after 90 days in which none of our notifications reached the device, and in any case a year after the app was last opened on it
• Settings saved for one device (its theme, notification choices and calendar sync): removed a year after the app was last opened on that device
• Server logs: 30 days. They record the address a request came from, but not what was asked in it — no search terms, email addresses or positions
• Invitations: deleted 30 days after they were accepted, declined or expired
• Billing webhook receipts: 90 days
• The log of administrative actions taken by us: kept after the account it concerns, or the account of the admin who acted, is deleted, but it then names neither. The link to the account is removed, and the log never copies a name or an email address. Deleted after 24 months
• Database backups: kept for up to 30 days, which is why a deleted account can take up to 30 days to disappear from every copy

Data Breach Notification

In the event of a data breach that poses a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours and affected users without undue delay, in accordance with GDPR Articles 33 and 34.

Changes to This Policy

We may update this privacy policy from time to time. When we make significant changes, we will notify users via a system announcement in the app. The “last updated” date at the top of this page indicates when the policy was last revised. Continued use of the app after changes constitutes acceptance.

Contact

For privacy inquiries, contact us at: support@inorout.no