Skip to content

As of: 16 November 2026

Privacy

Glenby processes as little about you as possible. Anything you share with others is end-to-end encrypted - we cannot read it. This is a translation for convenience. The German version is legally binding.

Controller

The controller responsible for data processing within the meaning of the DSGVO is Ebrahim Seyfi (Geschäftsbezeichnung „Senorit"), Seeschwalbentwiete 23, 22119 Hamburg, glenby@senorit.app. Full provider details can be found in the Legal notice.

End-to-end encryption

Content you share with friends (photos, notes, messages, your answer to the daily prompt) is encrypted on your device before it reaches our servers. Only the recipients you choose can decrypt it. We store exclusively the encrypted content and hold no key to it.

What stays visible: metadata

End-to-end encryption makes the content of your messages and photos unreadable to us, but not the fact that communication is happening at all. To deliver messages we necessarily process metadata: who sends to whom, timestamps, and delivery/read status. The legal basis is Art. 6 Abs. 1 lit. b DSGVO (performance of the usage contract); the retention period follows the lifetime of your account, see the Retention period section. In addition to the DSGVO, the telecommunications secrecy under § 3 TDDDG protects both the content and the closer circumstances of your communication and binds us as a provider of an interpersonal telecommunications service.

What data we process

Account
Glenby can only be used with an account; there is no local-only mode. It covers your email address, display name, friend code and progress (XP, level, streak, answered daily prompts). To keep streak protection consistent across devices, we also store protection credits earned and spent, and protected days. You send your password to our server over an encrypted connection when you sign in, and we store it there only as a bcrypt hash, not in plain text. To restore your chat history we also keep a copy of your key encrypted with your password or your recovery code. While your password or code reaches our server, nothing technically stops us from opening that copy. We do not do so. Accounts created before version 0.56.0 are converted only once the conversion is switched on; that is not the case at the moment. Until the conversion, when you sign in with an older app version, and on the first sign-in on a newly installed device, your password may still be transmitted to our server (over an encrypted connection only, stored only as a bcrypt hash). This transition ends no later than 13 April 2027. If you sign in with Google, an identifier for your Google account takes the place of the password; in the iOS app the same applies to Sign in with Apple (see "Sign in with Apple"). If you choose "Hide My Email" there, we store Apple's relay address instead of your real address. At sign-up we store, with a timestamp, your declaration that you are at least 18. Your date of birth stays on your device.
Username
The name you chose, when it was last changed, and whether you want to be findable by it. With that setting off, nobody can find you by name.
Profile details
Optional answers on pace, terrain, distance, experience and availability, plus an avatar motif, a short intro and answers to the profile prompts. They exist to suggest something you and a friend would both enjoy.
Daily prompt
Your answer consists of a photo, the time it was taken, the label from on-device image recognition and a coarse place name (the nearest city, never a precise location). Our server receives the day, the time, the label and your progress values (XP, streak), never the place name and never the coordinates. We back the photo up only in encrypted form, with a key only you hold.
Location
For the place name on your answer to the daily prompt the app reads at most a recently known location and never asks for the permission by itself; the coordinates are not stored. Outside live sharing there is no background tracking and no movement profile. If you share your location live, the app collects it for as long as the share runs and the app is open. The app sends it end to end encrypted to the friends you chose. Our server relays it and does not store it. A location pin from a chat is something you send yourself, also end-to-end encrypted.
Safe-return check-in
If you arm one, we store until it expires the time you chose, the contact you chose and your last position, that position only end-to-end encrypted for that one person and unreadable to us. The legal basis is your consent. The feature is not an emergency service.
Emergency card and SOS
Blood group, allergies, conditions and emergency contacts are health data under Art. 9 GDPR. They are stored encrypted on your device alone, never reach our servers and are in no backup. The legal basis is your explicit consent under Art. 9(2)(a) GDPR. An SOS sends the same encrypted location report as an expired check-in, only immediately; impact detection reads the motion sensors on the device only. Neither is an emergency service.
Shared content
Photos, voice notes, notes and messages you share with friends, including your answer to the daily prompt, stored exclusively end-to-end encrypted. We hold no key to it.
Video calls
1:1 video calls are transmitted directly between devices (WebRTC, encrypted) and are not recorded. Cloudflare acts solely as a TURN relay to broker the connection.
Billing
For a paid subscription you pay through Google Play (Android) or Apple's App Store (iOS), which process the payment data. We ourselves store only the identifier needed for contract administration and the plan status.
Friends and notifications
Friend code, connections, and, if you enable reminders, a push token (on iPhone, also a separate token for call signals). If you arrive through an invite link, also who invited you and whether that referral has already been rewarded.
Technical data
Minimal data for operation and security, such as session and device identifiers and synchronization timestamps. Plus the period you chose after which an unused account is deleted automatically. In the iOS app, the result of the device and app check is added (see "Device and app check").

Location

For the place name on your answer to the daily prompt the app reads at most a recently known location and never asks for the permission by itself; the coordinates are not stored (see “Daily prompt”). Outside live sharing there is no background tracking and no movement profile. If you share your location live, the app collects it for as long as the share runs and the app is open. The app sends it end to end encrypted to the friends you chose. Our server relays it and does not store it. A single location pin from a chat's attach menu is something you send yourself, as an end-to-end encrypted message. Your location is therefore not a special category of personal data within the meaning of Art. 9 DSGVO; the processing is based on Art. 6 Abs. 1 lit. b and lit. f DSGVO.

Services we use (processors)

Encrypted content and account data are processed by the following services:

Processors and recipients that Glenby uses to operate the app and website
ServicePurposeLocation / transfer basis
Cloudflare Inc. (USA)Database and application logic (D1, Workers): accounts, chat metadata, entitlements. Storage of end-to-end encrypted photos and voice notes (R2), chat delivery (Durable Objects), call connection brokering (TURN). Hosting of this website (glenby.de), delivered through the Cloudflare network, with access logs. Transactional email delivery through Cloudflare Email Service (email address, display name, message content), no marketing emails.Database location hint: Western Europe, with no read replicas in other regions (no contractually guaranteed EU jurisdiction); requests are processed at the nearest Cloudflare data centre. Shared content reaches Cloudflare only as ciphertext. Transfer based on the EU-US Data Privacy Framework and the Cloudflare Customer DPA with Standard Contractual Clauses.
Cloudflare Web Analytics (Cloudflare, Inc., USA)Anonymous measurement of load times and page views on glenby.de, only with your consent (cookie banner). Processes browser performance data, the visited and referring page, and the browser type. No cookies, nothing stored on your device.According to Cloudflare, the IP address is discarded at the nearest data centre and not stored. Transfer based on the EU-US Data Privacy Framework and the Cloudflare Customer DPA with Standard Contractual Clauses.
Cloudflare Turnstile (Cloudflare, Inc., USA)Protection of the forms on glenby.de against spam and automated attacks. Processes technical data such as IP address, browser and device information and interaction signals, no form contents.Transfer based on the EU-US Data Privacy Framework and the Cloudflare Customer DPA with Standard Contractual Clauses.
Google LLC (USA)Google account sign-in (Google Sign-In: email address, name, profile picture), push notification delivery on Android (Firebase Cloud Messaging, device token), map rendering of the live-location view (Google Maps SDK, direct device connection), app integrity checks on Android (Play Integrity), crash reports (Firebase Crashlytics, Android and iOS app, only after opt-in in the app, off by default), reporting of transactions to Google Play for purchases through the external payment link in the Android app (amounts, tax, currency, time, country, transaction identifier and purchase token; no name, no email address). Optional chat backup into the hidden app folder (appDataFolder) of the user’s own Google account: off by default, the “drive.appdata” permission only, contents end-to-end encrypted before upload.Transfer based on the EU-US Data Privacy Framework.
Google Ireland Limited (Ireland)Mail hosting (Google Workspace) for the mailbox glenby@senorit.app: emails written to Glenby, including messages from the contact form (name, email address, subject, message content).The contracting party is Google Ireland Limited in the EU. Any processing by the Google group in the USA relies on the EU-US Data Privacy Framework.
Norwegian Meteorological Institute (MET Norway)Official severe weather warnings for your location in Norway (api.met.no, MetAlerts), if you switch them on.Device IP address and location coarsened to roughly 1 km are sent directly from the device, not through our servers. Data licensed under NLOD 2.0 and CC BY 4.0.
Deutscher Wetterdienst (Germany)Official severe weather warnings for your location in Germany (maps.dwd.de), if you switch them on.No third-country transfer. Device IP address and coarsened location are sent directly from the device. Data under the German GeoNutzV ordinance and CC BY 4.0, source: Deutscher Wetterdienst.
National Weather Service / NOAA (USA)Official severe weather warnings for your location in the USA (api.weather.gov), if you switch them on.Device IP address and coarsened location are sent directly from the device, and only while you are there. Data free to use for any purpose.
Hugging Face, Inc. (USA)One-time download of the offline speech model for voice notes as text and for voice commands where the system has no offline recogniser.No content or account data is transmitted.
Apple Distribution International Limited (Ireland) and Apple Inc. (USA), independent controlleriOS app only: Sign in with Apple (checking the sign-in token, revocation when an account is deleted), notifications and call signals (Apple Push Notification service, device token), handling and status checks of App Store purchases (App Store Server API and notifications, transaction identifier) and device and app check (App Attest).Apple processes under its own responsibility and not on our behalf; no agreement under Art. 28 GDPR therefore exists. According to Apple's privacy policy, Apple bases the transfer from the EEA to the USA on standard contractual clauses. Details in the section "iOS app and Apple".

We have the necessary agreements under Art. 28 DSGVO in place with our processors. Apple processes under its own responsibility and is not our processor.

Data sources

The map of the live-location view comes from Google Maps. The photos of adventures come from Wikimedia Commons; author and licence are on the Commons page of each image (commons.wikimedia.org). Your device does not fetch them from Wikimedia. If you switch them on, the app gets official severe weather warnings from the responsible national weather service (see "Services we use"). Glenby queries no third-party database for place, path or species data.

Transfers to third countries

Some of the services we use are based, or process data, outside the EU/EEA. Our database runs with Cloudflare. Cloudflare and Google are based (also) in the USA and are certified under the EU-US Data Privacy Framework, which the EU Commission has recognized as providing an adequate level of protection (Art. 45 DSGVO). This does not apply to Apple: Apple states that it relies on standard contractual clauses (see "iOS app and Apple"). All transfers to third countries take place exclusively on one of the bases provided for in Art. 44 ff. DSGVO. The full, continuously updated list is above under "Services we use".

Content you share with others (photos, voice notes, notes) leaves your device only end-to-end encrypted. Even though the encrypted ciphertext sits on servers outside the EU, nobody except the recipients you chose can read the content, not us and not the respective hosting provider.

Screening for harmful content on the device

Before a photo is encrypted and shared, the app screens it directly on your device for clearly harmful content. This screening runs locally - no images are uploaded for it. More on this on the Security & Transparency page.

Voice commands and voice notes as text, on the device

Voice commands ("Sag es Glenby") and turning voice notes into text run entirely on your device. Speech recognition is done by your Android system's offline recogniser (Google, Android 12 and later) or, where that is missing, by a local speech model inside the app; understanding the command is done by a small model inside the app. Audio, recognised text and command never leave your device and are not stored by us. A command that touches safe-return, SOS or your location always waits for your confirmation. If the offline recogniser is missing or you request transcription, the app downloads a speech model (about 57 MB) once from Hugging Face, Inc. (USA), only after you agree; your IP address is transmitted, no content or account data (see "Services we use"). Legal basis: Art. 6(1)(b) GDPR.

Crash reports

Purpose
Error analysis and stability improvement of the app.
Data
App version, operating system version, device model and device state (free storage, for example), the crash report (stack trace), and a random Crashlytics installation ID. No link to your Glenby account. Google necessarily processes your device IP address on receipt; it does not become part of the report. Messages, photos and voice notes are never included.
Legal basis
Art. 6 Abs. 1 lit. a DSGVO (consent). The feature is disabled by default (opt-in); you enable it yourself in settings and can disable it again there at any time using the same toggle, with effect for the future.
Recipients
Google LLC (Firebase Crashlytics, USA).
Storage
A crash report is first created only on your device and is only transmitted the next time the app starts. On the server, crash reports are kept for a maximum of 90 days; we store a maximum of 5,000 reports in total, with older ones automatically overwritten.

Statutory reporting duty

If there is reasonable suspicion of a serious crime - in particular depictions of the sexual abuse of children - we are required under Art. 18 of Regulation (EU) 2022/2065 (Digital Services Act) to inform the competent law enforcement authority. The central reporting body in Germany is the Bundeskriminalamt as the central office under § 13 DDG in conjunction with § 2 BKAG. Only the content concerned is, in this case, excluded from end-to-end encryption and secured with a separate key that only the automated, official reporting channel can open. No one at Senorit sees this content in plain text.

Cancellation and withdrawal function

Purpose
Receiving and automatically carrying out statutory declarations under § 312k BGB (cancellation) and § 356a BGB (withdrawal).
Data
Name, email address, contract details, and the time of the declaration.
Legal basis
Art. 6 Abs. 1 lit. b and lit. c DSGVO.
Recipients
Payment processing (Google Play), database and email delivery (Cloudflare).
Storage
We keep the declarations as evidence for six years after receipt and then delete them.

iOS app and Apple

If you use Glenby on iPhone, Apple processes part of the data under its own responsibility and not on our behalf. For people in the European Economic Area that is, according to Apple's privacy policy, Apple Distribution International Limited in Ireland; data is generally stored at Apple Inc. in the USA. For transfers out of the EEA, Apple's privacy policy relies on standard contractual clauses (Art. 46(2)(c) GDPR). What Apple does with the data is set out in that policy at apple.com/legal/privacy.

We pass Apple only the data the following features need. We never receive your Apple password or your payment details.

Sign in with Apple

Purpose
Registration and sign-in in the iOS app with your Apple account, without a password of your own.
Data
An identifier Apple issues for Glenby, your email address together with whether it is an Apple relay address, and your name if you share it at first sign-in (Apple sends it only that once). Also an Apple token that we need only to sign Glenby out at Apple when you delete your account. If you choose "Hide My Email", we know only the random address from Apple (privaterelay.appleid.com). Our emails to you then travel through Apple to your real address; Apple sees that they come from us. If you switch the forwarding off at Apple, our emails no longer reach you.
Legal basis
Art. 6(1)(b) GDPR (usage contract). Sign in with Apple is an option; you can also sign in with email and password.
Recipients
Apple. Our servers verify the sign-in there, exchange the sign-in code for the token and revoke it when you delete your account.
Storage
Identifier, email address, relay flag and token stay as long as your account exists. On deletion we revoke the token at Apple and delete the data. If the revocation at Apple fails, we record that internally; it does not hold up the deletion of your account.

Purchases and subscriptions through the App Store

Purpose
Handling Glenby+ (monthly, yearly, Duo) that you subscribe to in the iOS app through the App Store: unlocking, status checks and linking to your account.
Data
We do not receive payment details, Apple account or billing address; payment, invoice and receipt run through Apple. We store the original transaction identifier of your subscription, the chosen product, its status, expiry time, whether it renews, whether the purchase ran in the production or the test environment (sandbox) and when we last checked the status. Also a random linking identifier that we generate and the app hands to Apple at purchase, so that notifications from Apple find your account.
Legal basis
Art. 6(1)(b) GDPR (performance of the subscription contract). We need to know whether your subscription exists.
Recipients
Apple (App Store Server API and server notifications). We ask Apple for the status using the transaction identifier; Apple tells us about renewals, cancellations, refunds and expiries.
Storage
As long as your account exists. When you delete the account we remove the link to the purchase and the linking identifier. That does not end a subscription running at Apple. Cancel it with Apple first (iPhone: Settings > [your name] > Subscriptions), or Apple keeps charging you.

Notifications and call signals (Apple Push Notification service)

Purpose
Delivery of notifications (new messages, reminders, safe-return alerts) and of signals for incoming calls, so your iPhone rings even when the app is closed.
Data
Two device tokens issued by Apple: one for notifications and a separate one for call signals (VoIP/PushKit), plus an identifier of the installation and the time of the last update. A notification contains a generic text template, technical identifiers (for the chat, for example) and, where present, an encrypted envelope that only your device opens. Messages never appear in it in plain text; the app builds the text on your device.
Legal basis
Notifications about messages and reminders: Art. 6(1)(a) GDPR. You allow them in the iOS system prompt and can withdraw the permission in iPhone settings at any time with effect for the future. Call signals: Art. 6(1)(b) GDPR, because otherwise calls would not reach you. Alerts about a safe-return check-in: on the basis of your consent, as described for the feature itself.
Recipients
Apple (Apple Push Notification service). Apple sees the token, the time and the content of the notification, meaning the template, the identifiers and the encrypted envelope, and passes it on to your device.
Storage
We delete a token as soon as Apple reports it invalid, and together with your account. At Apple, an undeliverable notification is generally held for 24 hours at most and a call signal for 60 seconds.

Device and app check (App Attest)

Purpose
Protection against automated sign-ups and counterfeit apps. When you register or sign in, we check whether the request comes from a genuine installation of the Glenby app on a genuine Apple device. For now we only evaluate the result and decide nothing on it.
Data
A key identifier and the public key that Apple creates on the device for Glenby alone, and the result of the check. The result is stored in the security log together with the IP address and the device and software identifier (user agent) of the request. We do not read a serial number or advertising identifier from it.
Legal basis
Art. 6(1)(f) GDPR. Our legitimate interest is protecting Glenby and its users from automated abuse. The check uses no data from your account. You can object under Art. 21 GDPR (see Your rights).
Recipients
Apple (App Attest) confirms the key to the device. We verify that confirmation ourselves; our servers do not call Apple for it.
Storage
We delete the check result in the security log after 12 months. We delete the key entry at the latest together with the account it is linked to; while it is linked to no account, we keep it only as long as we need it to protect against abuse.

Chats and messages

Chats and messages

Disappearing messages

Messages, photos and voice notes in one-to-one chats are end-to-end encrypted. We cannot read them. We keep the encrypted content only as long as delivery requires. Once all of your signed-in devices have safely stored a message, we delete our copy after 7 days at the latest. A message we cannot deliver, for example because your device has been offline for a long time, we delete 30 days after it reached us at the latest. The same applies to the related photo and voice files. After that, your chat history exists only on your devices and, if you turn it on, in your own Google Drive backup. If you set up a new device or reinstall the app, older history can therefore only be restored from that backup. We clear short-lived technical buffers sooner: real-time delivery on our servers after 3 days, push notifications at Google after 24 hours at most, at Apple generally after 24 hours. If you report a message, we keep it until the report is closed, 30 days at the longest. Technical backups of our database expire after 30 days. Deleted content can remain there for up to 30 more days. For messages that were already with us before these time limits took effect, a transition period of 60 days from the day we switched on the deletion replaces the 30 days.

Decrypted media on your device

We keep decrypted photos and voice notes in your device's app-private cache so they display quickly. There is no fixed retention period. When the cache exceeds a size limit, the app removes the files unused for the longest time. The app deletes them when you switch accounts, and the operating system (Android or iOS) removes them when you uninstall. Android backups do not include this storage.

Reports

When you report a single message, we store the report with the reason, category, your account and the reported account. Our team receives the content of the message only if you yourself attach it as evidence (at most 4,000 characters; the text for text messages, only basic details for voice messages; for photos, including an answer to the daily prompt, the basic details and a small preview of the photo of at most 24 KB, which your device creates). Without evidence, we store no readable message content with the report. We do not automatically notify the reported person. For one-to-one chats we also keep the message in encrypted form, which we cannot read, until the report is closed, for 30 days at most, and then delete it. This also applies if the sender then deletes the message for everyone or a view-once photo expires. We keep the report and your evidence, including the preview of a photo, as a record: closed reports for up to 24 months after receipt, open ones until they are closed; we delete the preview of a photo 12 months after receipt at the latest, even if the report is still open, and otherwise together with the report.

Data export

The data export contains your saved season-ring places, call diagnostic logs (latest 200) and your registered devices list. It also contains the reports you filed, with reason, category, status, timestamps and the evidence you attached. Under Settings > Your data you can also export your chats as a readable file (JSON). Your device builds it from the local history. The server holds only encrypted messages.

Daily prompt

Every day the app shows one prompt, the same for everyone. Your device works out which from the date alone. If you answer, the answer consists of a photo, the time it was taken, the label from on-device image recognition and a coarse place name: the name of the nearest city from a list inside the app, never a precise location. The coordinates are not stored and not transmitted for this. Our server receives the day, the time, the label and your progress values (XP, streak), and the photo only in encrypted form (see “Photos”), but not the place name. From this we count anonymously, per day, how many people answered; the app shows the number only from three answers on. Friends see your answer only if you share it; it then goes to them end-to-end encrypted, with the place name as part of the message. So that experience points are credited only for a day on which you were online, your app gets a day ticket from the server each day, a code the server calculates from your account identifier and the date; your answer sends it along. Without a ticket the answer stays in your album but earns no XP and no streak. The legal basis is Art. 6(1)(b) GDPR (providing the feature) and Art. 6(1)(f) GDPR (protection against abuse).

Photos

Your photo for the daily prompt is kept on your device. To restore it after a reinstall we back it up only in encrypted form, with a key only you hold; we cannot read it. Image recognition on your device suggests a label (Google ML Kit, general image labelling); nothing is transmitted for this. If you share a photo with friends, it is first checked on-device for harmful content, stripped of location metadata (EXIF/GPS) and transmitted end-to-end encrypted. We store only the encrypted content and cannot read it.

Calls and bonus XP

For 1:1 calls each device tells the server when the connection is up and when the call ends. Per call and account we store the call identifier, the account identifier of the other person and these two timestamps, so also the duration of the call, for at most three days and without any content. The server uses them to check that the call took place and was long enough before it credits bonus XP. The bonus XP entry (call identifier, XP) belongs to your progress and stays as long as your account exists. The legal basis is Art. 6(1)(b) GDPR (providing the feature) and Art. 6(1)(f) GDPR (protection against abuse).

Adventures and invitations

When you start an adventure, we store its content, checked steps and start, update and completion times in your account. Checking a step is your own report, not GPS verification. Your device can keep encrypted offline copies of the last six opened adventures with progress. Companion invitations connect an adventure with the inviting account and, if accepted, the accepting account. Their links are valid for 14 days; expired invitations are deleted by the daily cleanup. Share an invitation link only with your intended companion. Public previews show none of your account or location data. Optional discovery notes, selected details and photos stay on your device and are removed on sign-out or account change. They are not part of the server export or cloud backup. You can export notes through the share menu. A memory card can include a photo you select, its title, date and public adventure link; notes and precise coordinates are excluded. Photos can contain visible location landmarks. The adventure and invitation records stored in your account provide the requested feature (Art. 6(1)(b) GDPR), are included in your export and are deleted with your account.

Usage and payment overview

For internal totals on usage and payment, we count existing task, session and adventure records. Starting an adventure can also store the general source of its link, such as “first-discovery” or a campaign name, without an advertising identifier. We keep an updated summary of the first and latest payment confirmed by Stripe, payments during the last 28 complete days after refunds, and the trial period and contract status. Granted access does not automatically count as a purchase. The purpose is to understand use of the service and its economics; the legal basis is our legitimate interest under Art. 6(1)(f) GDPR. You can object to this analysis by contacting glenby@senorit.app. It adds no advertising cookies, movement profiles or access to private messages. Account summaries are exportable and removed on account deletion; legally required payment records at the payment provider are unaffected.

iOS waitlist

Purpose
If you sign up on the download page for the iOS launch, we send you a confirmation email and then exactly one message once the app is available for iPhone. Nothing else happens with your address: no newsletter, no advertising, no sharing.
Data
Email address, the time of sign-up and of confirmation, a random confirmation code, and the note that the sign-up came through the website. Your IP address is evaluated in memory only, for the abuse limit, and is not stored.
Legal basis
Art. 6(1)(a) GDPR (consent). The sign-up only takes effect once you click the link in the confirmation email (double opt-in). You can withdraw your consent at any time with effect for the future - an informal message to glenby@senorit.app is enough and we delete the entry.
Recipients
Cloudflare (database, email delivery and website hosting). How each is classified, and the basis for the transfer, is set out above under "Services we use".
Retention
If you do not confirm the sign-up, the confirmation link stays valid and we delete the entry automatically at the latest twelve months after sign-up. We send no reminder in the meantime. Confirmed sign-ups are deleted after the launch message, or immediately on withdrawal.

Contact form

Purpose
If you write to us through the contact form, we use your details only to answer your request. There is no advertising and no newsletter, and we do not pass your details on for other purposes.
Data
Name, email address, the subject you chose, your message and the language of the page. Your IP address is evaluated in memory only, for the abuse limit, and is not stored. For the security check, see "Cloudflare Turnstile".
Legal basis
Art. 6(1)(f) GDPR (legitimate interest in answering requests). If your request concerns a contract with us or its preparation, Art. 6(1)(b) GDPR applies. You do not need to give consent for this. You can object to the processing at any time, an informal message is enough.
Recipients
Cloudflare (website hosting, security check and email delivery) and Google Ireland Limited (Google Workspace, the mailbox your message arrives in). How each is classified, and the basis for the transfer, is set out above under "Services we use".
Retention
We delete your message and our reply at the latest six months after the request is closed. We keep them longer only if a statutory retention duty applies.

Legal bases

  • Art. 6 Abs. 1 lit. b DSGVO - provision of the app, its features, and the paid contracts.
  • Art. 6 Abs. 1 lit. a DSGVO - consent for push notifications and for optional crash reports; revocable at any time.
  • Art. 9 Abs. 2 lit. a DSGVO - express consent for the meet-people feature, to the extent it may involve special categories of personal data.
  • Art. 6 Abs. 1 lit. f DSGVO - operation, security, and abuse prevention.
  • Art. 6 Abs. 1 lit. c DSGVO - statutory reporting and cooperation duties.

Retention period

Content and account data are stored for as long as your account exists; upon deletion they are removed (see account and data deletion). We keep termination and withdrawal declarations for six years after receipt and then delete them. If a statutory report under Art. 18 DSA has been triggered for a piece of content, that content remains excluded from deletion for the duration of the official proceedings; the legal basis for this is Art. 17 Abs. 3 lit. b DSGVO. Diagnostic data about failed exports (app version, network status, error codes) and about chat-list performance (app version, device model, counts and timings, no content) is kept for 90 days and then deleted. The connection data for 1:1 calls (see “Calls and bonus XP”) is deleted after three days at most.

Your rights

You have the right to access (Art. 15 DSGVO, first copy free of charge), rectification, erasure (Art. 17 DSGVO), restriction of processing, data portability, and objection (Art. 15-21 DSGVO), as well as the right to withdraw any consent given at any time with effect for the future. The app offers an export and a deletion function directly in the settings; see account and data deletion. Requests at any time to glenby@senorit.app.

Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority, generally the authority of the German federal state (Bundesland) where you reside.

Technical error reports on this website

Purpose
Detecting and fixing technical errors on glenby.de, maintaining safe and stable operation.
Data
Automatically captured JavaScript error messages and violations of our Content Security Policy (CSP reports). No cookies, no user identifier; IP addresses are not stored.
Legal basis
Art. 6 Abs. 1 lit. f DSGVO (legitimate interest in a secure and error-free operation of the website). Since no cookies are set and no recognition takes place, no consent under § 25 TDDDG is required for this.
Recipients
Internal operations system, database (Cloudflare).
Storage
For abuse-prevention reasons we accept a maximum of 500 reports within 24 hours. The retention period is 90 days, after which reports are automatically deleted.

Cookies and local storage

To run this site we use only technically necessary storage within the meaning of § 25 Abs. 2 TDDDG; no consent is required for this, a disclosure is sufficient. In addition, with your consent, we use Google Tag Manager, Google Analytics 4 and Cloudflare Web Analytics for traffic measurement (see the sections below). These services, and any related storage, only load once you actively consent via our cookie banner; until then, no connection to Google or Cloudflare Web Analytics is made. The legal basis is your consent under § 25 Abs. 1 TDDDG in conjunction with Art. 6 Abs. 1 lit. a DSGVO. You can withdraw your consent at any time with effect for the future, via the "Cookie settings" link in the footer.

Google Tag Manager and Google Analytics 4

With your consent we use Google Tag Manager and Google Analytics 4, services of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Your browser loads a script from www.googletagmanager.com for this; the Tag Manager starts Google Analytics 4. It measures the pages viewed, browser and device details, and clicks on the Google Play button and the iOS waitlist request. Form entries and invitation codes are not transmitted. Google Analytics 4 may set cookies and read information on your device; your IP address is transmitted to Google for technical reasons.

Before you consent, no connection to Google is made. The legal basis is your consent under Art. 6(1)(a) GDPR and § 25(1) TDDDG. You can withdraw it at any time with effect for the future via "Cookie settings" in the footer.

The data may be transferred to Google LLC in the USA. Google is certified under the EU-US Data Privacy Framework (adequacy decision under Art. 45 GDPR). More information: https://policies.google.com/privacy

Cloudflare Web Analytics

With your consent we use Cloudflare Web Analytics, a service of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. It shows us how fast our pages load and which pages are viewed. For this, your browser loads a script from static.cloudflareinsights.com. It reads performance data through the browser's Performance API, such as load times, the visited and the referring page and the browser type, and sends it to Cloudflare.

No cookies are set and no data is stored on your device. Cloudflare builds no user profiles and does not track you across websites. Your IP address is transmitted for technical reasons. According to Cloudflare it is discarded at the nearest data centre and not stored.

The legal basis is your consent under Art. 6(1)(a) GDPR and § 25(1) TDDDG. You can withdraw your consent at any time with effect for the future through the cookie settings.

Cloudflare is certified under the EU-US Data Privacy Framework (adequacy decision under Art. 45 GDPR). A data processing agreement with Standard Contractual Clauses is also in place. More information: https://www.cloudflare.com/privacypolicy/

Cloudflare Turnstile

To protect our forms against spam and automated attacks we use Cloudflare Turnstile, a service of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. When you open a form, Turnstile checks in the background whether the request comes from a human. This processes technical data such as IP address, browser and device information and interaction signals. Turnstile does not read form contents and uses the data solely for this security check.

The legal basis is our legitimate interest in preventing abuse and spam under Art. 6(1)(f) GDPR. The access to information on your device this requires is strictly necessary for the secure operation of the form (§ 25(2) no. 2 TDDDG).

Cloudflare is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). A data processing agreement with Standard Contractual Clauses is also in place. More information: https://www.cloudflare.com/turnstile-privacy-policy/

Notice for users in the United States

Glenby is operated from Germany and follows the GDPR. We grant the rights described here to everyone, wherever they live. For California, additionally: we do not sell or share personal information within the meaning of the CCPA, and we receive nothing in return for it. You can review, export or delete your data yourself at any time in the app under “Your data” or through our deletion page; questions go to glenby@senorit.app.

Do Not Track: we collect no information about what you do on other websites or in other apps, neither ourselves nor through any third party via Glenby. Because we do not carry out that collection at all, there is nothing a browser “Do Not Track” signal could change.