Privacy Policy
Last updated: 11 November 2026 · Version 2.21
This privacy policy applies to the website cummly.com, the Cummly app for iOS and Android and the services connected to them. In case of discrepancies between the German and the English version, the German version prevails.
1. Controller
Weber & Deschauer Cummly GbR
c/o flexdienst – #20493
Kurt-Schumacher-Straße 74
67663 Kaiserslautern
Germany
Email: contact@cummly.com
2. General information
Special categories of personal data
Account, device, session and partner data reveal that and when you controlled a device with Cummly. This may allow conclusions about your intimate life (Art. 9(1) GDPR). We therefore process this data only with your explicit consent (Art. 9(2)(a) GDPR), which you give at registration or at your first sign-in. Without it we cannot run an account. You can withdraw the consent at any time by deleting your account (section 10).
Recipients
- Hetzner Online GmbH (Germany): hosting and email delivery in data centres in the EU, as a processor.
- Stripe Payments Europe, Ltd. (Ireland): payment processing (section 6).
- Google Ireland Limited and Apple Distribution International Ltd., if you sign in with your Google or Apple account, as independent controllers.
- Apple Inc.: push service for Live Activities on iOS (section 5).
- TrafficJunky (Aylo group) and ExoClick S.L. (Spain) as independent controllers, only with your consent to the measurement of our ads (section 9).
We have concluded agreements under Art. 28 GDPR with our processors.
Transfers to third countries
Stripe, Google and Apple may also process data in the USA. Transfers are based on the EU-US Data Privacy Framework and, in addition, on the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR). Where data from ad measurement is processed by the Aylo group in Canada, the transfer is based on the adequacy decision for Canada (Art. 45 GDPR).
Retention
We keep data only as long as it is needed for the respective purpose or statutory retention obligations apply. Specific periods are stated with each processing activity.
3. Website
Cookies
The website and the app use strictly necessary cookies only: for your sign-in and session, to protect forms against abuse and, if you choose "Remember me", to keep you signed in. Session and protection cookies expire after two hours of inactivity, the "Remember me" cookie when you sign out and after 30 days at the latest. When you enter and confirm payments, our payment provider Stripe sets its own fraud-prevention cookies, kept for up to one year; they are required for the payment you request. If you reach us through a creator's or a campaign's link, we keep the associated discount code in a cookie for 30 days so that it is pre-filled when you buy a pass; the cookie holds only the code and is removed when you buy. We set no tracking, analytics or advertising cookies. Legal basis: § 25(2) no. 2 TDDDG, Art. 6(1)(b) and (f) GDPR.
Server logs
With every visit to the website and every request from the app, our server stores technical access data: IP address, time, the address requested, referrer, browser or app version and operating system. This data serves secure and error-free operation (Art. 6(1)(f) GDPR) and is overwritten automatically after a short time.
Contact
If you contact us by email or phone, we process your details to handle your request (Art. 6(1)(b) GDPR, otherwise point (f)) and delete them once they are no longer needed for that and no retention obligations apply.
Cancellation form
Through "Cancel contracts here" you can cancel a monthly pass without signing in. We store the details you enter, the IP address, browser identifier and time of receipt, attribute the cancellation to your account and send you a confirmation link by email. Legal basis: Art. 6(1)(b) and (c) GDPR (§ 312k BGB). We keep the cancellation as evidence for three years from the end of the year in which it was received.
Support tickets
Signed-in users can reach us through the ticket system in their account. We store the history of your tickets, notify you of replies by email and delete the tickets together with your account. Legal basis: Art. 6(1)(b) GDPR.
4. Account and sign-in
An account is created by registering or through an invitation from us. We store your username, display name, email address, password (only as a hash), language and currency, and the time and version of your acceptance of the Terms of Service and of your consent. To confirm your email address and for invitations we send time-limited links.
When you set a password we check whether it appears in known data breaches. For this we query the "Pwned Passwords" service (haveibeenpwned.com) with the first five characters of a hash of the password; neither the password itself nor your email address or any other information about you is transmitted. Legal basis: Art. 6(1)(f) GDPR (account security).
You can sign in with a password, a sign-in link sent by email or your Google or Apple account, and you can enable two-factor authentication. When you sign in with Google or Apple we receive from the provider your account ID, your name and your email address (with Apple, a relay address if you choose), and from Google, where available, the link to your profile picture. You can unlink the account in the account settings. Google (https://policies.google.com/privacy) and Apple (https://www.apple.com/legal/privacy/) are themselves responsible for the processing on their side.
In the app you can enable sign-in with your device lock (Face ID, Touch ID, fingerprint or device code). The check takes place exclusively on your device; we never receive biometric data. For this we store a device-bound sign-in key (as a hash only) together with the IP address, device details and the time of last use, until you remove it in the account settings, reset or change your password or it goes unused for 180 days. Legal basis: Art. 6(1)(b) GDPR.
For every signed-in session in the browser or the app we store the IP address, browser or device details and the last activity so that you can see and end your sessions in the account settings.
Legal basis: Art. 6(1)(b) GDPR, for the session overview also point (f) (account security).
5. The Cummly app
Processing on your device
During a session you start, the app uses the operating system's screen capture including the playback audio; on Android only if you grant the audio permission. The analysis takes place exclusively on your phone: the app detects the movement of people in the picture without identifying them and calculates an intensity value from it, which it sends to your device over Bluetooth. Images, videos, audio and content derived from them are neither stored nor transmitted to us or anyone else.
In an audio session the app uses your phone's microphone instead of screen recording, also while the app runs in the background. It only measures the loudness, on your phone only; the sound is neither recorded, stored nor transmitted.
The app stores your sign-in and your settings on your phone, for example for intensity and for tuning to your devices. This is necessary for the functions you use. The sign-in is deleted when you sign out; the settings remain stored on the phone. Legal basis: § 25(2) no. 2 TDDDG, Art. 6(1)(b) GDPR.
Permissions
- Bluetooth: finding, pairing and controlling your devices. Devices that do not pair are controlled through a radio signal that any device nearby can receive; it carries only the intensity level.
- Location (Android 11 and older only): required by the operating system for Bluetooth scanning. We do not collect location data.
- Microphone and audio recording (optional): on Android for the playback audio of other apps during a session; on Android and iOS for the sound feature in play mode and for audio sessions. Audio is neither recorded, stored nor transmitted.
- Display over other apps (Android, optional): only for the floating intensity control during a session. The app does not read any content of other apps.
Your Bluetooth devices
We store paired devices and devices you add in your account (identifier, name, device type, last battery level, last connection) so that you can reconnect quickly; you can delete them in the settings. If you report an unsupported device to us, we store its name and identifier and notify you by email once we support it. Legal basis: Art. 6(1)(b) GDPR. If you withdraw a report, we no longer notify you but keep it to gauge demand for devices until you delete your account (Art. 6(1)(f) GDPR).
Play mode and your own patterns
In play mode the app controls your devices with patterns, without recording the screen. With the sound feature your devices follow the sound your phone's microphone picks up instead. The app only measures the loudness, on your phone only and only while the app is open; the sound is neither recorded, stored nor transmitted. Patterns you create are stored with their name and curve in your account until you delete them or your account. Legal basis: Art. 6(1)(b) GDPR.
Partner remote control
You can link other Cummly users as partners with an invite link. We store who invited whom, when the invite was accepted, and until when an open link is valid; open links expire after 72 hours and are then deleted. Your partner sees your display name, and so does anyone who opens your invite link. When you let a partner control your devices, we store the start, end and duration, to count your plan's daily remote-control time, and delete these after 30 days. Your partner's control commands pass through our own servers in the EU straight to your app and are not stored. The link stays in place until one of you removes it or deletes their account. Legal basis: Art. 6(1)(b) GDPR and your explicit consent (Art. 9(2)(a) GDPR), which you give by creating or accepting an invite and can withdraw by removing the partner.
Sessions and billing
For every session we store the type of session (video or audio), the times, duration, status, the device used, plan and prices, and the amounts billed and the related payments. During the session the app regularly reports technical status data (for example the connection to the device and error codes) so that only active time counts and we can fix errors. We delete this status data after 120 days. Legal basis: Art. 6(1)(b) GDPR.
Free session
To prevent the free session from being used more often than intended, we link it to your device through a randomly generated app identifier and, if you sign in with Google or Apple, also to your account ID there. The identifier is not used for advertising or tracking. After an account is deleted we keep this link, without any connection to your account, for at most twelve months so that signing up again does not unlock another free session. Legal basis: Art. 6(1)(f) GDPR (preventing abuse); storing the identifier on your device is strictly necessary for this (§ 25(2) no. 2 TDDDG).
Live Activities (iOS)
On iOS the app can show the session status on the lock screen. For this we receive a session-specific push token from Apple and send status updates through the Apple Push Notification Service. Legal basis: Art. 6(1)(b) GDPR.
Diagnostic data (only with your consent)
If you enable "Share session diagnostics" in the account settings, the app uploads a numeric log of the measured values (for example motion strength and computed intensity) and of your feedback from the feedback buttons after each session. It contains no images, no audio and no screen content. We use it only to improve motion detection and delete it after 30 days, at the latest together with your account. You can switch the function off at any time and request the deletion of logs already uploaded. You can also choose to attach technical app logs to a support ticket; these contain no image or audio content either and are deleted after 30 days. Legal basis: your explicit consent (Art. 6(1)(a), Art. 9(2)(a) GDPR).
6. Payments
Payments are processed by Stripe Payments Europe, Ltd. (Ireland). You enter card or account details directly into a form provided by Stripe; they never reach our servers. We store your Stripe customer number, the type and last four digits of the payment method, and details of your payments and passes, including when they end. To calculate VAT we pass the country and postcode of your payment method's billing address to Stripe (Art. 6(1)(c) GDPR). Stripe is our processor and is itself responsible for fraud prevention and its own legal obligations (https://stripe.com/privacy). Legal basis: Art. 6(1)(b) GDPR. We keep payment records for up to ten years because of tax law obligations, also after an account is deleted (Art. 6(1)(c) GDPR).
If you redeem a discount code when buying a pass, we store the code together with the purchase. The creator or partner a code belongs to only learns from us how often the code was redeemed and the revenue it generated, not who redeemed it. Legal basis: Art. 6(1)(b) GDPR. After an account is deleted, the redemption is kept without any link to you.
7. Emails
We send you emails that your account needs, such as confirmation and sign-in links, security notices, replies to tickets and notices about devices, payments and changes to prices or terms (Art. 6(1)(b) GDPR). Occasionally we also inform you about new features and changes to the service (Art. 6(1)(f) GDPR); we choose the recipients by plan, language and whether you have used Cummly recently. You can unsubscribe from these informational emails at any time in the account settings or via the unsubscribe link in each of them. For each informational email we record whom it was sent to and whether delivery succeeded; we delete this record after six months, or earlier if you delete your account.
8. Logging
For the security of your account, to prevent abuse and for support, we log security-relevant events, such as sign-ins and failed sign-in attempts, changes to the account, payment method and settings, the purchase and end of passes, the redemption and refusal of discount codes, the start and end of sessions and of play mode, and changes to your patterns, partner links and the start and end of remote control, each with the time, IP address and browser or device details, but without content. Legal basis: Art. 6(1)(f) GDPR. We delete the logs after six months, or earlier if you delete your account (section 10).
9. Our ads on other websites
We advertise Cummly with ads on third-party websites that we book through the ad networks TrafficJunky and ExoClick. cummly.com itself has no ads, no tracking pixels and no scripts from these networks.
Clicking an ad. If you reach us through such an ad, the address contains a click identifier (click ID) from the network and, where applicable, identifiers of the campaign, the ad and the placement. We keep these details only on our server in your session; we set no additional cookie for this, and the details are linked through the session cookie that is set anyway. We count the visit and any sign-up anonymously per network, campaign, ad, placement and day, without any reference to you. If you do not sign up, the details expire with the session; if you sign up, we then delete them from the session. Legal basis: our legitimate interest in measuring how well our advertising works (Art. 6(1)(f) GDPR).
Reporting to the network only with your consent. At sign-up you can voluntarily consent to us reporting your sign-up, your first session and your first pass to the network whose ad brought you here. Only then do we store the click ID and the campaign, ad and placement identifiers with your account. We also attribute your payments to that ad internally to see which advertising pays off; this is only evaluated in aggregate per network, campaign, ad and placement. We transmit the click ID, the type of event and a transaction number. Combined with the data it collected when you clicked the ad, the network can conclude that you use Cummly; we therefore report only with your explicit consent (Art. 6(1)(a), Art. 9(2)(a) GDPR). Consent is not a condition for using Cummly. You can withdraw it at any time in the account settings; we then delete the click ID and stop reporting. The networks are themselves responsible for their further processing.
Retention. We delete the click ID linked to your account after 90 days, and immediately if you withdraw consent or delete your account.
10. Account deletion
You can delete your account at any time in the account settings. It is deactivated immediately and permanently erased with all data connected to it after 30 days; until then you can reverse the deletion through support. Exceptions are payment records (section 6), cancellation declarations (section 3) and the link of the free session (section 5).
11. Your rights
You have the right of access, rectification, erasure, restriction of processing and data portability (Art. 15 to 18 and 20 GDPR). You can get a copy of your account data in a machine-readable format through contact@cummly.com or support in your account. You can withdraw consent at any time with effect for the future; the lawfulness of the processing carried out until then remains unaffected.
You can also lodge a complaint with a data protection supervisory authority, in particular in the Member State of your residence, your place of work or the place of the alleged infringement.
Right to object (Art. 21 GDPR)
Where processing is based on our legitimate interest (Art. 6(1)(f) GDPR), you can object to it at any time on grounds relating to your particular situation. We will then no longer process the data unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. You can object at any time, without giving reasons, to processing for direct marketing, such as our informational emails.