Privacy Policy
1. Controller
represented by its managing director Sascha Kaderka
Kolonnenstraße 8
10827 Berlin
Germany
Phone: +49 30 4243 4444
E-mail (privacy and support): support@memolabs.de
Imprint: in the app under Settings → Imprint. We have not appointed a data protection officer because the legal requirements for doing so (Art. 37 GDPR, § 38 BDSG) are not met.
2. Summary
- Your photos, videos and music do not go to the internet. They travel directly from your phone to your TV over your Wi-Fi or your phone's hotspot. memo labs has no server where your media ends up, and you need no account.
- Not everything on your home network is encrypted. The control connection to the memovu app on Fire TV is encrypted (TLS with certificate pinning). The photos and videos themselves are currently fetched by the TV unencrypted, protected by a secret access key (section 4).
- Two Google components may send technical diagnostic data to Google: purchases through Google Play and the Google Cast connection. The QR scanner works without Google (section 5.3). In the website video browser, Google Safe Browsing also checks the addresses you open against Google's list of dangerous sites (section 5). The app contains no ad networks and no components of third-party analytics providers.
- You decide what feedback you send. Reports, wishes and answers only reach us when you tap, reports with a preview. The app only sends usage and error statistics if you agree; you can turn them off at any time. The app downloads notices and the wish list without an identifier (section 11).
- License codes are verified offline. When you redeem one, the app does not contact any server.
- If you buy license codes as a business, we process order and invoice data (section 13).
- We do not learn what you open or save in the website video browser. Saved pages stay on your device, with no account and nothing sent to us (section 8).
3. What stays on your phone and your TV
The app processes the following data only on your device or on your local network. We have no access to it. What of it reaches us when you tap or with your consent is stated in the row and in section 11.
| Data | Purpose | Where | Deletion |
|---|---|---|---|
| Photos, videos, music | Display and playback on your TV | stay in your gallery; the TV loads them from the local network only for display (transfer: see section 4) | the phone app makes no permanent copies: photos converted for transfer sit in the app's cache, which is capped at 300 MB; the app deletes older ones automatically, and "Clear app data" removes all of them (guest photos: section 9). The Fire TV app keeps images in memory only, not on the stick's storage |
| Pairing data (name and network address of the TV, access key, certificate fingerprint; on the TV: the phone's device name and hashes of the keys) | reconnecting without pairing again | encrypted app storage on the phone, app storage on the TV | "Forget device" in settings, clear app data or uninstall the app |
| Settings (e.g. slideshow speed, language, reminder on/off) | convenience | local app storage | clear app data or uninstall the app |
| Purchase and license status (e.g. Pro active, trial end, ID of a redeemed license code) | unlocking Pro features | encrypted app storage | clear app data or uninstall the app; Play purchases can be brought back via "Restore purchases" |
| Pro trial memory and free minutes on the TV (non-reversible checksum of your phone's device ID, start time of the Pro trial, link to the pairing; on Fire TV with Fire OS also, for today, the free seconds shown and whether the daily limit applies to your phone) | so that reinstalling the phone app neither restarts the Pro trial nor the free minutes, and so that the TV can end the free minutes without the phone | app storage of the memovu app on the TV; does not leave your home network; seconds of earlier days are overwritten | clear the TV app's data or uninstall it |
| Memories (mapping of your photos to dates and albums) | the "Memories" feature and its reminder | computed and stored on the phone | clear app data or uninstall the app |
| Guest photos in event mode | live slideshow at an event | in the app's cache on the host's phone until the event ends; approved photos optionally in the gallery album "memovu Event <date>" | see section 9 |
| Saved pages in the website video browser ("Your pages"): address, title, website, date saved and last opened, folder and whether it is locked, your own look (colour, one or two characters, picture shown or hidden) | finding pages again that you saved yourself | only on your device, in the app's private storage; not in device backups (Google, iCloud); no account, no sync, nothing on our side | one by one with "Remove", a folder with "Delete pages too", clearing the app's data or uninstalling the app |
| Picture of a saved page | recognising it in the list | a reduced picture that the page itself names; the app loads it once when you save the page, directly from the address the page gives (without cookies, https only), and keeps it next to the saved pages, also not in device backups | together with the page (after 10 seconds, so "Undo" works); all at once with the switch "Show page pictures" |
| Log of recent events and errors (at most 300 lines; the app removes names of devices and networks, addresses and keys as soon as it records them) | help with problems | two small files in the app storage; the app overwrites older lines | “Delete everything on this device” under Settings → Privacy, clear app data or uninstall; leaves the phone only if you send it yourself (section 11) |
| Usage counters (which feature roughly how often and how long, as totals without times) | optional statistics (section 11.5) | local app storage | expire after 60 days at the latest; “Delete everything on this device”; sent only after your yes |
| How the app was installed (Android only, section 11.6), your statistics choice with time and text version, note of when memovu last asked you something | pairing after the QR code, optional statistics, proof of your choice, not asking too often | local app storage | clear app data or uninstall |
| Reports not yet sent, and your sent reports with report number | sending once the service is reachable; following up | local app storage | waiting reports after 7 days at the latest; “Delete everything on this device” |
| Last downloaded notices and wish list | showing notices and wishes without a connection | local app storage | clear app data or uninstall |
TV identifier (Fire TV with Fire OS): So that your phone recognises your TV even after the memovu app on the TV has been reinstalled, and no duplicate entries appear, the TV app turns the device identifier Fire OS assigns to it (Android ID) into a one-way checksum that serves as the TV's identifier. Only phones you paired using the code on the screen receive it, plus – to keep the free minutes in sync – your other memovu TVs. It stays on these devices within your Wi-Fi and is never sent to us or third parties. "Forget TV" on the phone removes the pairing; leftovers for the free minutes expire after a few days. On the TV it usually only changes after a factory reset.
4. How your media is transferred on your home network
To show a photo or video, the phone app starts a small media server that can only be reached on the local network. The TV fetches the files from there. Here is honestly what is encrypted and what is not:
| TV | Control | Photos, videos, music |
|---|---|---|
| Fire TV with the memovu app | encrypted (TLS); the phone checks the TV's certificate against the QR code (certificate pinning) | unencrypted (HTTP) on the local network, only with a secret access key |
| Fire TV with Vega OS and the memovu app | unencrypted (HTTP) on the local network; every message carries a check value with a key from the pairing, so only the paired device can control the TV | unencrypted (HTTP) on the local network, only retrievable with a secret key |
| Screen mirroring (Fire TV with Fire OS or Vega OS) | Picture and sound run over WebRTC, which always encrypts the transfer. | |
| Chromecast and Google TV | via Google's Cast protocol | unencrypted (HTTP) on the local network, via time-limited signed addresses |
| DLNA TVs (e.g. Samsung, LG) | unencrypted on the local network (this is how DLNA devices work) | unencrypted (HTTP) on the local network, via time-limited signed addresses |
| Guest upload in event mode | – | unencrypted (HTTP) from the guest's phone to the host's phone, via an address with a secret key from the QR code |
What this means for you: someone recording the traffic on the same Wi-Fi could read the transferred images and the access key. On your own password-protected Wi-Fi the risk is low. On open or third-party networks (hotel, venue) we recommend your phone's hotspot. We are working on encrypting the media path to the Fire TV app as well and will update this policy when we do.
5. Google components in the app
These components come from Google and send data to Google themselves. We do not receive this data. Google's processing is governed by Google's privacy policy (https://policies.google.com/privacy). Google may transfer data to countries outside the EU, such as the USA; Google LLC is certified under the EU-US Data Privacy Framework.
5.1 Purchases via Google Play
You buy Pro (monthly or yearly subscription), the Event Pass and Event Studio through Google Play. Google is the contracting party and merchant for these purchases. Payment runs through your Google account; we receive no payment data and run no purchase server of our own. Google Play only tells the app whether a purchase is active; the app stores this locally. You cancel and manage subscriptions in Google Play. On payments: Google Payments privacy notice (https://payments.google.com/payments/apis-secure/get_legal_document?ldo=0&ldt=privacynotice). The app on your phone manages the 48-hour Pro trial, without an account and without payment data. So that reinstalling the app does not restart it, the memovu app on a Fire TV remembers a non-reversible checksum of your phone's device ID and the trial start time; the ID itself never leaves your phone. This data stays on the TV in your home network (section 3). If the app asks you for a rating, Android shows a Google Play window for it; what you enter there goes to Google, not to us.
5.2 Google Cast (Chromecast, Google TV)
For Chromecast and Google TV the app uses the Google Cast SDK. According to Google, it logs device discovery and session events as well as information about the phone and the app, in order to monitor SDK usage and performance and to detect bugs. According to Google, the data is encrypted in transit, not shared with third parties and contains no identifiers that can be traced back to a specific user. According to Google, this cannot be switched off. (Source: Google Cast – Data disclosure (https://developers.google.com/cast/docs/android_sender/data_disclosure).)
By default, the app uses Google's standard receiver on Chromecast devices. If the
memovu receiver is active instead, the Chromecast loads its program files from our web
server (section 12) and the Cast library from Google (www.gstatic.com). Even
then it loads your photos only from your Wi-Fi.
5.3 QR scanner (zxing-cpp, without Google)
The app reads the QR code on the TV with the open-source decoder zxing-cpp (package flutter_zxing) and Android's camera interface. Recognition runs entirely on the phone; the camera image is neither stored nor transmitted, and this component sends no data to Google or any other third party. (Until October 2026 the app used Google ML Kit for this; it has been removed.) If you prefer not to use the camera, you can pair the TV without scanning: the app finds it on your Wi-Fi and you confirm the security code shown on the TV.
5.4 Website video browser (Android WebView with Google Safe Browsing)
The app's website video browser uses the Android WebView, in which Google Safe Browsing is switched on (the Android default, which we keep for security reasons): the addresses you visit are checked against Google's list of dangerous sites so you are warned about scam and malware sites. Google describes how this works at https://developers.google.com/safe-browsing.
6. Permissions of the phone app
The app asks for permissions only when you use the feature:
- Photos and videos (
READ_MEDIA_IMAGES,READ_MEDIA_VIDEO,READ_MEDIA_VISUAL_USER_SELECTED): to show media from your gallery on the TV. From Android 14 you can also grant access to selected photos only. In event mode the app optionally saves approved guest photos to your gallery. - Music (
READ_MEDIA_AUDIO): only when you choose your own music for a slideshow. - Camera (
CAMERA): only for scanning the QR code on the TV. - Microphone (
RECORD_AUDIO): only when you turn on sound while mirroring. Android requires this permission so that device audio (e.g. from a video) can be forwarded. Your surroundings are not recorded. - Notifications (
POST_NOTIFICATIONS): for the Memories reminder and the notice that something is playing on the TV. - Network (
INTERNET,ACCESS_NETWORK_STATE,ACCESS_WIFI_STATE,CHANGE_WIFI_MULTICAST_STATE): for the connection to the TV on the local network and to find it on your Wi-Fi. Only the Google components named in section 5, the website video browser and the feedback feature (section 11) go to the internet. - Run at startup (
RECEIVE_BOOT_COMPLETED): restores the Memories reminder after a reboot. - Foreground services (
FOREGROUND_SERVICE,…_CONNECTED_DEVICE,…_MEDIA_PROJECTION): keep a running slideshow, video or mirroring session alive while the screen is locked. A notification is shown. - Biometrics (
USE_BIOMETRIC): only when you open a locked folder in the website video browser. Android shows its own dialog (face, fingerprint or device credential); the app only learns whether the check succeeded.
The Fire TV app uses only network permissions and a foreground service so that reception stays active behind the screensaver.
7. Memories reminder
The app can remind you of memories (e.g. "One year ago today"). The reminder is scheduled and shown on your phone only; no data is sent for it. You can switch it off in the app settings or in Android's settings.
8. Website videos
When you open a website in the website video browser or send a website video to the TV, your phone or TV connects directly to that website. As with any browser, the website receives your IP address and device information, and its privacy terms apply. We are not involved in this connection and do not learn what you open. The browser opens pages on the internet only encrypted (https); it opens unencrypted pages (http) only from devices in your own home network, such as your NAS or router, and that connection stays on your Wi-Fi. For Safe Browsing see section 5.4. When you send a video to the TV, the page title goes to your TV too. In the playlist the app loads your saved pages one after another like a browser; the same rules apply.
Saved pages, locked folders and browsing data. Only you save pages, with the star in the address bar. They stay on your device, are not synced and are excluded from device backups; we never receive them. The app keeps no history of the pages you visit. You can lock folders with your device's lock (face, fingerprint or device passcode). Your device does the check; the app only learns whether it succeeded and never sees your face, your fingerprint or your passcode. The lock hides a folder's pages inside the app; anyone who knows your device passcode can open it. "Clear browser data" removes sign-ins and everything websites have stored in the app on your device; your saved pages and their pictures stay. We do not need your consent for storing this on your device because you expressly use this feature (Section 25(2) No. 2 TDDDG). On older versions of the Android WebView, some website caches (Cache Storage, service workers) may remain after clearing; "Clear app data" in the system settings then removes everything.
9. Event mode (guest photos at events)
In event mode, guests upload photos from their own phones to the host's live slideshow via a QR code. The following applies:
- The photos go directly to the host's phone over the Wi-Fi or hotspot on site (transfer: see section 4). No memo labs servers are involved; we receive neither photos nor any information about the event or the guests. If you agreed to the optional statistics, they only count how often you use event mode and how many photos arrive, as totals (section 11.5).
- During the event, the host's phone processes the local IP addresses of guest phones to enforce upload limits and, if the host wishes, to block individual guests. This stays in memory and is gone when the event ends.
- The host approves or rejects photos. Approved photos are optionally (default: on) saved to the album "memovu Event <date>" in the host phone's gallery. They stay there until the host deletes them.
- Until the event ends, guest photos are kept in the app's cache on the host's phone. If the connection to the TV drops, they stay there so the event can continue. "End event" deletes photos not yet approved immediately; approved photos that were not saved to the gallery are deleted as soon as the connection to the TV has ended as well. If the app is closed before that, it removes the leftovers at the latest when the next event starts; "Clear app data" removes them at any time.
- The controller under the GDPR for guest photos is the host. For purely private celebrations, the household exemption usually applies (Art. 2(2)(c) GDPR). Commercial hosts (e.g. photographers, event businesses) are themselves responsible for informing their guests under Art. 13 GDPR and for having a legal basis. For this the app has a "Note for guests" field that appears on the guests' upload page. This also applies to the photos in the gallery album: the host decides how long they are kept there and deletes them accordingly. Hosts who do not want to keep guest photos on their own phone switch off "Save approved photos automatically" in the event settings and choose "Don't keep" when ending the event.
10. License codes in the app
You redeem license codes for Event Studio, memovu Business and the event pass in the app. Each code carries a digital signature that the app checks on the device with a built-in key. No server request takes place; the app reports the redemption to no server. If you agreed to the optional statistics, they count a redemption only as a total, without the code (section 11.5). Validity and code ID are stored locally so the same code cannot be activated again on this device.
11. Feedback, error reports and optional statistics
memovu has its own feature for sending us feedback. Everything the app sends us through it is listed in this section. The app never sends us your photos, videos or music, file and album names, web addresses, bookmarks, the names of your devices and networks, your location or identifiers of your device. The only exception is images you attach to a report yourself (11.2). The app does not assign an identifier to your device, your installation or for advertising.
11.1 Our feedback service
Feedback goes to our feedback service at support-api.memolabs.de. It runs on servers of Hetzner Online GmbH in Germany, which works on our behalf (Art. 28 GDPR). Like any server, it receives your IP address when the app sends or downloads something. It does not store it in its database and only uses it briefly in memory to limit abuse. For the downloads (11.4) and the optional statistics (11.5), no server in front of it stores it either. Before the app sends anything, it fetches a small computing task from the service and solves it; the task makes automated mass sending harder; this creates no information about you. During the first 60 seconds after it starts, the app does not contact the service. We may pre-sort reports and wishes automatically; any decision based on them is made by a person.
11.2 Report a problem and suggest a feature
With “Report a problem” and “Suggest a feature” you send us a report or a wish. Nothing is sent until you tap “Send”. Before that, the app shows exactly what goes along under “This is what's sent”. A report contains:
- your text and the area you chose;
- your e-mail address, only if you enter it to get a reply;
- technical details, as long as “Attach technical details” is on (default, can be turned off for each report): app version with build number and distribution channel (for example Google Play), whether you use memovu for free, on the trial or with Pro, model, manufacturer, processor type and system of your phone, language and region from the device settings, time zone, screen size, text size and whether a screen reader is running, type of network connection and whether a VPN is active; for the TV its type, model, manufacturer, system and app version; up to 200 of the app's latest events and error messages, connection measurements, the result of “Check connection” and a short form of the error cause (for example “U-7K2Q9”). The app removes names of devices and networks, addresses and keys as soon as it records them. On Android this includes how the app was installed (11.6), but only if it is known and “Include how you found memovu” is on; it is then shown in the preview and is not sent if you turn off the technical details;
- up to three images, only if you attach them yourself using your device's image picker. The app scales them down and saves them again, so the location and camera details are dropped. memovu never takes a screenshot by itself.
After sending you get a report number; you can use it to follow up or to ask us to delete the report. If the service cannot be reached, the app keeps trying to send the report for up to 7 days while it is open; “Do not send” discards it, and “Send by email instead” sends it through your e-mail program (11.7).
If part of the app has stopped with an error, the app remembers the type of error and the code locations involved (without error text) on your phone for up to 7 days and asks at the next start whether you want to report it. “Report” opens the form with the preview, and the report then also contains the type of error and the code locations; “No” deletes the details.
Purpose: solving your problem, replying if you wish and improving memovu. The legal basis is your consent, which you give by tapping “Send” (Art. 6(1)(a) GDPR; for reading the technical details on your device Section 25(1) TDDDG); where your contract is concerned, also Art. 6(1)(b) GDPR. In your text, the service masks codes, phone numbers and e-mail addresses; it stores the original encrypted (periods in 11.8).
11.3 Answers with one tap
In some places you can answer with one tap: “Was this helpful?” below a help answer, “Did that work now?” after a fixed error, “Me too” on other people's wishes and short surveys with fixed answers. What is sent: your answer, the place, app version and platform, for answers about help and connections your type of TV (for example “Fire TV”, never its name), whether you use memovu for free, on the trial or with Pro, and how far you have got with memovu (for example “TV connected” or “first picture shown”). A small line at that place says what goes along. Each answer is sent on its own, without any link to other messages. Purpose: seeing which help helps, which wishes many people share and how memovu works for free and Pro users. Legal basis: your consent by tapping (Art. 6(1)(a) GDPR, Section 25(1) TDDDG).
11.4 Downloading notices and the wish list
So that the app can warn you about a known problem or an outdated TV app before you run into it, and so that the message “fixed” arrives without an app update, it downloads a notice package from our feedback service at most once a day, and also when you open help, “Check connection” or the form if the last download was more than 6 hours ago. The request only states the platform (Android or iOS), the app version and the distribution channel (for example Google Play or a test version), because the right notices depend on them, and whether the app already has a copy of the file. The app only downloads the list of other people's wishes when you open “Suggest a feature”, at most every 6 hours. Neither download carries an identifier. The notice package is signed by us; the app only accepts genuine packages. Through it we can switch off single features for a while (for example after an error), pause all messages from the app, show notices and texts in different versions and ask you to update an outdated version. Whom a notice is for (for example plan, language, type of TV or age of the installation) is checked by the app on your device; this information is not sent to us for that. From them, the service only counts daily totals per platform, version and channel, split by whether the app already had a copy (roughly: new installations). Legal basis: Section 25(2) no. 2 TDDDG, because the download is strictly necessary for the notices in the app, and Art. 6(1)(f) GDPR (our interest in delivering notices reliably and sizing the service).
11.5 Optional usage and error statistics
On your phone. memovu counts on your phone which features you use and roughly how often and how long, as totals without times and without an identifier. Older values expire after 60 days at the latest, even after a long break. The app also keeps the time of its first start only on your device; it uses it as well to show notices step by step. Only the month of it is sent, and only after your yes. Without your yes, none of it leaves your phone. Under Settings → Privacy you can see the values, reset them with “Reset”, stop counting with “Stop counting” and delete everything with “Delete everything on this device”.
Your choice. Once after setup or after the first picture shown on your TV, memovu asks: “Want to help make memovu better?”, with two equal buttons “No thanks” and “Yes, I'll help”. Never during a slideshow or presentation, in event mode, while mirroring or while a video is playing on the TV. If you close the question without answering, it appears at most three times in total, at least 7 days apart. After “No thanks” the app asks at most one more time, and not before 120 days. You find the same choice in the form and under Settings → Privacy. Without your yes, memovu sends none of this, and the app works the same either way.
What is sent after your yes. About once a week a usage overview (usage statistics): how often and how long you used which features and on how many days, as totals; plus app version with build number, which part of the app sends, platform and system, device class (phone or tablet), distribution channel (for example Google Play), language and country from your phone's region settings (not your location), whether you use memovu for free, on the trial or with Pro, which kind of purchase you have (for example monthly or yearly subscription or license) and how your Pro trial ended, how far you have got with memovu, your answer to “Which TV do you have?”, which types of TV you connect, the month of first use and the approximate age of the installation and, while switched on, how the app was installed (11.6). Also which version of notices, texts and offers you were shown. The first overview also contains what memovu counted on your phone before. If a connection fails (error statistics): the technical cause, the type of TV and the app versions on phone and TV, at most five a day. If we switch it on, the error statistics also report caught program errors by themselves: only the type of error, up to three code locations, app version and platform, without error text and without a log, at most three a day.
Nothing that identifies you. These messages carry no identifier, as time only the start of the calendar week, plus the version of the consent text. They are sent on their own, never together with a report, and we do not link them to reports or e-mail addresses. When and with which text you agreed is stored only on your phone.
Turning it off. Under Settings → Privacy you switch “Send usage statistics”, “Send error statistics” and “Include how you found memovu” on and off separately; after your yes all three are on. Turning them off applies at once to all future messages. We cannot match anything already sent to you because it carries no identifier; it is deleted after the periods in 11.8.
Purpose: seeing where memovu gets stuck, which errors recur with which TVs and what we should build next; for the installation source see 11.6. Legal basis: your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG), which you can withdraw at any time with effect for the future (Art. 7(3) GDPR).
11.6 How the app was installed (Android only)
If you install memovu through a link with campaign details, for example from our website, from a recommendation in a video or from an ad, Google Play passes these details to the app at installation (Install Referrer). The app only takes source, medium and campaign plus our own value “src”, each only as a short word of lower-case letters and digits (otherwise “other”), and stores them on your phone. It never takes click identifiers of ad networks. These details always describe a group, for example “via a recommendation on YouTube”, never a single person; we never assign campaign details to individual people. If you come via the QR code on the TV, the app also uses the value to take you straight to pairing after installation.
How the app was installed is only sent with your consent: in the optional statistics, as long as “Include how you found memovu” is on, and, while that switch is on, in a report with technical details (11.2). Purpose: seeing which recommendation or ad brings people to memovu and whether they then use and buy memovu (measuring the effect of our advertising). Legal basis: your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). On iPhone and iPad the app does not read any installation source.
11.7 By e-mail
When you write to us by e-mail, including via “Send by email instead”, we process your e-mail address, your name (if given) and the content of your message to answer the request. The app opens your e-mail program and inserts the report as the preview shows it. You see the text before sending and can change or delete it. Our e-mail runs on Google Workspace (section 13.5). The legal basis is Art. 6(1)(b) GDPR where your contract is concerned, otherwise Art. 6(1)(f) GDPR (our interest in answering requests). We delete requests once they are settled, at the latest after two years, unless statutory retention duties apply.
11.8 Retention
| What | How long |
|---|---|
| Reports, wishes and one-tap answers | 12 months |
| Technical details of a report and crash details | 90 days |
| Images from reports | 30 days, at most 90 days while a case is open; the unchecked original file at most 24 hours |
| Your e-mail address | 90 days, encrypted; after that only an unreadable check value we use to match access and deletion requests, kept no longer than the report |
| Original of your text | 30 days, encrypted; after that only the version with masked codes, phone numbers and e-mail addresses |
| Optional statistics | 90 days individually, after that only as totals from which no single message can be read |
| Downloads of the notice package and wish list | daily totals only |
| On your phone: counters, log, waiting reports | counters at most 60 days, waiting reports at most 7 days; a “No thanks” to the statistics question is kept when you delete, as are some security details that do not relate to you (blocked keys, start of a shutdown); everything at once with “Delete everything on this device”, clearing app data or uninstalling |
12. This website
This website is hosted by Hetzner Online GmbH (Industriestraße 25, 91710 Gunzenhausen, Germany) on servers in Germany. Hetzner processes data on our behalf (data processing agreement under Art. 28 GDPR).
- When you visit, the server necessarily processes your IP address, date and time, the page requested, the browser type and the amount of data transferred. Without this the page cannot be delivered. Access logs are deleted after 7 days at the latest. Legal basis: Art. 6(1)(f) GDPR (secure and stable operation of the website).
- Statistics from server logs: To learn which pages people look for and where something breaks, we count page views from our server's logs. The result is daily totals only, for example “120 views of the home page, 30 of them from Instagram”. Your IP address and your browser's identifier are not part of these totals. To estimate visits roughly, our server derives a short value from both using a secret key that changes every day, in memory only; key and values are discarded at midnight. We do not recognise you on another day. We delete the logs themselves after 7 days at the latest. Nothing is stored on or read from your device for this. Legal basis: Art. 6(1)(f) GDPR, our interest in improving the website and finding errors. Only we see the totals.
- Redirects from the app: links in the app that open a page in the browser (for example help, privacy or the TV app in the store) go through fixed addresses on this website (memovu.app/go/…). The server redirects straight to the target, without a cookie and without a script. The address only contains the target and the platform (Android or iOS); the language of the target page follows the language of the app or of your browser. At most we evaluate how often each target was opened per day and platform, without IP addresses. Legal basis: Art. 6(1)(f) GDPR (our interest in keeping links up to date without changing the app and in seeing which help is needed).
- Buttons to Google Play: the address carries a campaign value for the button (for example “startseite-kopf”). This lets the Play Console show us which button leads to installations. The value describes the button, not you; if you install memovu through it, section 11.6 applies.
- No cookies, no analytics services, no third-party content: the pages set no cookies, use no analytics or tracking services and load no fonts, scripts or images from third-party servers. The buy buttons lead to Stripe pages (section 13.2).
13. Buying license codes (businesses and organisations only)
13.1 Purchase via Stripe
You buy license codes (Event Studio, 5-pack of event passes, memovu Business) online in the Stripe checkout. The seller is memo labs. Payment and VAT are handled by Link, LLC, a Stripe group company, as merchant of record; payments are processed by Stripe Payments Europe, Limited and Stripe Technology Europe, Limited in Ireland (together "Stripe"). Stripe acts as an independent controller for name, e-mail address, country and address, payment data, VAT ID where given, IP address (also as tax evidence) and fraud prevention data. The Stripe privacy policy (https://stripe.com/privacy) and the Link privacy policy (https://link.com/privacy) apply. For transfers to the USA, Stripe relies on the EU-U.S. Data Privacy Framework and the EU Commission's standard contractual clauses. We never see card numbers or bank details.
13.2 Checkout
The buy buttons on our website are plain links. Only when you click one does the checkout open on a Stripe page; only then does your browser connect to Stripe, which may store data in your browser that is needed for payment and fraud prevention. This is strictly necessary for the purchase you requested (§ 25(2) no. 2 TDDDG); the legal basis for the processing is Art. 6(1)(b) GDPR. The pages of this website themselves load nothing from Stripe. For a Link account and managing your orders on link.com, Link's information applies.
13.3 What we receive from Stripe and why
After the purchase we receive from Stripe: e-mail address, name, name of the business or organisation, country, VAT ID where given, your confirmation that you buy for a business or organisation, product, quantity, price, order number and time, and later any refunds and chargebacks. From this our delivery service automatically creates your license code and e-mails it to you. The delivery service runs on our server at Hetzner Online GmbH in Germany (processor, Art. 28 GDPR) and stores, per order, the order number, e-mail address and the ID, term and code of the licenses issued; the business name is part of the code. We also use the data for support, renewals and bookkeeping. Proof of non-profit status for the non-profit price, which you send us by e-mail, is checked and kept as a record. Legal bases: Art. 6(1)(b) GDPR where you are the contracting party yourself (e.g. as a sole trader); Art. 6(1)(f) GDPR for contact persons at businesses and organisations, our legitimate interest being handling the purchase and communicating with our customers; Art. 6(1)(c) GDPR for tax and commercial law obligations (§ 147 AO, § 257 HGB).
13.4 Reminder before expiry
About four weeks before an Event Studio license or a memovu Business license expires, we send you a renewal reminder (Art. 6(1)(f) GDPR, § 7(3) UWG). You can object at any time, e.g. by e-mail to support@memolabs.de, at no cost other than transmission costs at basic rates.
13.5 Delivery by e-mail (Google Workspace)
We send license codes, discount codes and replies to enquiries by e-mail; the delivery service also sends through our e-mail account. Our e-mails run through Google Workspace of Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) as processor (Art. 28 GDPR). A transfer to the USA cannot be ruled out; it is based on the EU-US Data Privacy Framework and the EU Commission's standard contractual clauses.
13.6 Retention
Enquiries that do not lead to a purchase are deleted after six months. We keep business letters for six years, accounting records (e.g. Stripe statements) for eight years, books and annual accounts for ten years (§ 147 AO, § 257 HGB). License code data is stored for the term and afterwards as long as we need it for renewals and support, at most until the end of the retention period. Then we delete it.
14. Recipients at a glance
| Recipient | Purpose | Role | Country |
|---|---|---|---|
| Google (Play, Cast SDK, Safe Browsing) | purchases via Play, diagnostics of the Google components, protection against dangerous sites | independent controller | EU/USA |
| Link, LLC; Stripe Payments Europe, Limited; Stripe Technology Europe, Limited | payment, receipt, invoice and tax when buying license codes | independent controller | Ireland, USA |
| Hetzner Online GmbH | hosting this website, the Cast receiver, the license code delivery service and the feedback service (section 11) | processor | Germany |
| Google Ireland Limited (Workspace) | e-mail (support, license delivery) | processor | EU, possibly USA |
Beyond that, we only pass on data where we are legally obliged to, e.g. to tax authorities.
15. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on Art. 6(1)(f) GDPR (Art. 21). Write to us at support@memolabs.de. Data in the app is on your device; you can delete it yourself at any time (clear app data, uninstall or “Delete everything on this device” under Settings → Privacy). For a report, give us the report number or the e-mail address you entered. You can withdraw consent at any time with effect for the future (Art. 7(3) GDPR), the statistics with the switches under Settings → Privacy. We cannot match messages without an identifier to you; access and erasure are therefore not possible for them (Art. 11 GDPR). For data held by Google Play or Stripe, you can also contact these providers directly.
You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59–61, 10555 Berlin, Germany, https://www.datenschutz-berlin.de.
16. Obligation to provide data
You do not have to give us any data to use the app; reports, answers and the statistics are voluntary. To buy a license code, Stripe needs the details marked as mandatory in the payment window. Without them no purchase is possible. We do not use automated decision-making, including profiling (Art. 22 GDPR).
17. Children
The app and the license codes are not aimed at children. We sell license codes to businesses and organisations only.
18. Changes
We update this policy when the app, the website or the law changes. The current version is on this page; the app links to it under Settings → Privacy.