# Privacy Policy This page explains what data we process when you use our website and the glancy app. Last updated: 17 October 2026 ## General information ### Controller and contact [...]
[...]
[...] [...]
[...]
Represented by: [...]
Email for privacy requests: support (at) getglancy.com We have not appointed a data protection officer. This policy covers our website at `getglancy.com` and the glancy app for iOS and Android. ### Your rights You may request access to, correction or deletion of your personal data, or restriction of its processing. Where the legal requirements are met, you may request data portability or object to processing based on legitimate interests. You may withdraw consent at any time for the future. Contact us at support (at) getglancy.com. You may also lodge a complaint with a supervisory authority, in particular the [Baden-Württemberg data protection authority](https://www.baden-wuerttemberg.datenschutz.de/). ## Privacy on the website ### Hosting and access logs The static website files are stored in a private Amazon S3 bucket in the AWS Frankfurt region (`eu-central-1`). Amazon CloudFront delivers the website through a globally distributed network. Necessary connection data is processed, including IP address, time, requested URL, browser details and response status. CloudFront access logs are stored in a separate S3 bucket and deleted after 90 days. We use them for operation, troubleshooting and security. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is secure website operation. The provider is Amazon Web Services EMEA SARL, Luxembourg. Processing outside the EU cannot be ruled out because of CloudFront's global network. ### Matomo and browser storage We use Matomo to measure website reach. We host Matomo ourselves with ALL-INKL.COM – Neue Medien Münnich in Germany. Matomo is loaded only after you agree in the consent dialog. It processes, in particular, visited pages, time, technical browser information and an IP address shortened by two bytes. Raw Matomo data is stored for 365 days. Matomo may set analytics cookies. We also save your consent choice in your browser's `localStorage` to respect it on later visits. The legal basis for analytics is your consent under Article 6(1)(a) GDPR. Section 25(1) of the German TDDDG applies to storing and accessing information on your device. You can change your choice at any time through “Analytics settings” in the footer. On withdrawal, Matomo cookies on our domain are removed and Matomo is not started on the next load. You can use the website without agreeing. ### Email contact The website has no contact form. If you email us, we process your address and message to respond. We use ALL-INKL.COM – Neue Medien Münnich in Germany for email hosting and delivery. Depending on the matter, the legal basis is Article 6(1)(b) or (f) GDPR. We delete messages when they are no longer needed for the matter, unless a statutory retention obligation applies. ## Privacy in the app ### Account, sign-in and profile To create a glancy account, you need either an email address and password or sign-in through Apple or Google. When you use one of these providers, we receive the information needed for your account, in particular a provider identifier and, if supplied, your email address. We do not receive your Apple or Google password. You choose a nickname. We also process account identifiers, sign-in and security data. The legal basis is Article 6(1)(b) GDPR and, for security measures, Article 6(1)(f) GDPR. We record which version of the Terms you accepted and which version of this Privacy Policy you acknowledged, when you did so, and the language displayed. These records are kept while your account exists and removed when you delete it. ### Location sharing and connections We store latitude, longitude, horizontal accuracy, altitude, speed and heading together in an AES-256-GCM encrypted payload. Our server decrypts it only after authenticating the account owner or checking the requesting person’s sharing permission. This is encryption at rest, not end-to-end encryption. The account association and capture time remain stored separately as metadata. If you grant location permission and use sharing, the app updates your location in the foreground and background and sends it to our API. We do not keep a location history; we store the last location sent and when it was captured. People you authorize can see that location according to your settings, with its date and time and the nickname they assigned to you. You choose who can see your location, at what precision and for how long. You can pause or stop sharing and revoke location permission in your device settings. Location sharing cannot work without that permission. We process the accounts involved, settings and relevant times for connections, groups and sharing permissions. We keep an access log showing who viewed your location and when. The legal basis is Article 6(1)(b) GDPR. ### Motion detection To keep your location current while you are on the move and save battery while you are still, the app can use your device's motion detection. The permission is called "Motion & Fitness" on iOS and "Physical activity" on Android. The app only asks for it after an explanation; granting it is optional. The operating system, on Android through Google Play services, tells the app on the device whether you are currently moving, for example on foot, by bike or in a vehicle, or standing still. The app uses this solely to control location updates. It does not read step counts or health data. Motion information does not leave your device: we do not receive it, and the app does not pass it on to third parties. The device only keeps a short technical log of recent location events for troubleshooting, which may include switches between moving and standing still with their time. Without this permission location sharing still works, but may notice a change of place later. You can revoke the permission at any time in your device settings. The legal basis is Article 6(1)(b) GDPR for the requested app feature; device permission is requested through the operating system. ### Device information and push notifications We process device identifiers, platform, app version, technical status and push tokens to identify devices and deliver notifications. For iOS push we use Apple Push Notification service (APNs); for Android we use Google's Firebase Cloud Messaging (FCM). We send the device token and message content to those services, for example “*Nickname* viewed your location” or “*Nickname* wants to connect with you”. A notification can therefore reveal information about your contacts and use of location sharing. You can disable notifications in your device settings. The legal basis is Article 6(1)(b) GDPR for the requested app feature; device permission is requested through the operating system. ### Hosting and error reports Our API and database run with HOSTIM.DEV UG (haftungsbeschränkt) on Hetzner Online GmbH infrastructure. [Hostim.dev states](https://hostim.dev/docs/faq/#where-are-the-servers-located) that all current production workloads run on EU bare metal in Falkenstein, Germany. API access creates technical connection and security data, such as IP address, request time and device information. The legal bases are Article 6(1)(b) GDPR for providing the app and Article 6(1)(f) GDPR for stability and security. We use Sentry for error diagnosis. Our Sentry organization uses the EU data storage region and has “Enhanced Privacy” enabled. Error reports may contain technical data, IP address, device and app information, and other personal data in the error context. We use them to detect and fix errors under Article 6(1)(f) GDPR. ### Optional glancy+ subscription The app's basic features are available without a subscription. You purchase and pay for an optional glancy+ subscription directly through the Apple App Store or Google Play. Apple or Google processes payment details. We receive the subscription status and transaction details needed to activate and manage the subscription, but not your full payment card details. The legal basis for activation is Article 6(1)(b) GDPR and for statutory accounting and retention obligations Article 6(1)(c) GDPR. The relevant store's privacy policy also applies to purchases. So that a purchase can be matched to your glancy account, the app passes the store a pseudonymous identifier of your account when you buy. It contains neither your name nor your email address. Apple or Google return it to us with every message about your subscription. Through their interfaces and server notifications, the stores send us the product, term, renewal, cancellation and refund status, a transaction identifier and whether the purchase is a test purchase. We keep this information for as long as your account exists. If you delete your account, we detach the subscription from it, because it keeps running with the store until you cancel it there. Ended subscriptions that no longer belong to an account are deleted 90 days after they end. To improve the glancy+ page, we use Sentry to count how often it is opened, from which part of the app, and how often a purchase is started, cancelled or completed. We do not send account identifiers, prices or payment details; as with error reports, Sentry receives technical details such as the IP address and device and app information. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is presenting the offer clearly. ### glancy+ family With glancy+ family, the person who buys the family subscription (the owner) can invite up to five other people, who can then also use glancy+. To invite someone, the owner enters that person's email address. We store the address together with the invitation's status and expiry time and send the person an email containing the owner's nickname and a personal invitation link that is valid for 7 days. If the person already has a glancy account with that address, they also receive a notice in the app's inbox and, where enabled, a push notification. When the person accepts, we store the membership with the time they joined and, once it ends, the end time and reason, for example leaving, removal by the owner, the end of the family subscription or account deletion. The owner sees the members' nicknames and email addresses, whether they have glancy+ and since when they have been members, as well as the email addresses of open invitations. Members see the owner's nickname. We inform those involved about joining, leaving and the end of a membership in the app's inbox and, where enabled, by push notification. A membership does not share any location: who may see whose location is still decided only by each person's own sharing settings. The legal basis is Article 6(1)(b) GDPR for the owner and the invited person; for sending the invitation to a person who does not yet have an account, Article 6(1)(f) GDPR, our legitimate interest being the invitation the owner asked us to send. We delete expired, revoked and accepted invitations 90 days after their last change. Memberships are kept for as long as the accounts involved exist, so that Plus access and the retention periods of the activity feed are calculated correctly. When an account is deleted, its memberships and open invitations end immediately, and the name and email address are removed from the account. ## Information applying to both services ### Transfers outside the EEA According to the available information, our app backend with hostim.dev and Hetzner, and Matomo and email with ALL-INKL.COM, run in the EU. With CloudFront, Apple, Google and Sentry, data may be processed outside the European Economic Area or accessible from there. Where no adequacy decision applies, appropriate safeguards, in particular standard contractual clauses under Article 46 GDPR, may apply. An EU storage region alone does not rule out access from other countries. ### Retention and deletion We keep data only as long as needed for its purpose or a legal obligation. Website access logs are kept for 90 days and raw Matomo data for 365 days. The app stores only the last location. A location that has not been updated for 30 days will be deleted. We keep location access logs and activity feed entries for 3 days with Free and 90 days with glancy+. When Plus access ends, the activity feed immediately shows only entries from the last 3 days. After 7 days, we delete older activity feed entries and location access logs. If Plus access is restored during that period, the older entries are retained. This also applies to invited accounts whose Plus access ends because they are removed from a glancy+ family group. Completed location requests are deleted after 90 days. Connection requests that remain unanswered for 90 days are deleted. The in-app inbox shows only requests and notices that need a response. Open requests stay there until they are answered, withdrawn or expire. We delete completed entries after 30 days, notices 30 days after they are read and unread notices 30 days after they arrive. The technical records we use to deliver other push notifications, such as one about a location view, are deleted after 24 hours. When an account is deleted, we remove data unless statutory retention duties, particularly accounting requirements, apply. Data created by other people, such as their own nicknames for connections, may remain associated with their accounts. ### Required data and decisions If you do not provide required account data or device permission needed for a feature, you cannot use that feature. You can use the website without Matomo consent. We do not make automated decisions with legal or similarly significant effects under Article 22 GDPR.