Privacy at beckenblick
Your aquarium's story stays with you. Tank records, photos, comparisons and care schedules are processed on your device. beckenblick has no account system, cloud service or usage analytics of its own.
Google services are used for ad privacy choices, permitted advertising and Premium purchases. You control sharing, gallery copies and backups. The differences are explained below.
1. Controller and contact
DIY Jan, owned by Jan Höger, is responsible for beckenblick. Contact [email protected]. Our full postal address is in the directly accessible legal notice. Both documents are also available offline in the app, without an access gate.
2. Local app data
The app stores tank names, dimensions, livestock, equipment, care schedules, measurements, notes, photos, image alignment, drawings and widget settings in private app storage. These records enable photo series, before/after comparisons, growth GIFs, care reminders and widgets. The app does not send this content to DIY Jan or advertising providers.
No beckenblick account is needed. There is no app-owned sync server or analytics system, and your photos are not sent to an AI service. Alignment and tank-edge detection run locally. Bundled demo images are generated examples.
Processing needed for the functions you choose is based on Article 6(1)(b) GDPR. Necessary storage and access on your device are based on section 25(2)(2) of Germany's TDDDG. You choose which optional records to enter. Photo features require photos; other features remain available without them.
Android permissions and reminders
The ghost camera requires camera permission. The app does not request microphone, GPS or contacts access. Android's photo and file pickers grant access only to selected content; the app does not request general read access to your photo library. Notifications and, where needed, exact alarms require separate Android permissions. Schedules are processed locally and restored after a device restart. Reminder content may appear on your lock screen or widget; Android settings also control this visibility.
You can revoke permissions in Android settings. Granting a technical permission does not itself mean consenting to advertising.
3. Photos, gallery albums and optional folders
Selected photos are imported as app copies, resized to a maximum of 1,600 pixels on the longest edge and re-encoded. Original EXIF/GPS metadata is not copied. Personal details visible within the picture remain visible. The app does not modify or delete your original files.
Automatic gallery copies
When you add or take a photo, Android MediaStore creates an additional copy in a separate album for that tank under Pictures/Beckenblick. Photos and explicitly saved GIFs have separate albums. The app shows the precise path. Automatic photo copying can be disabled per tank. Finished GIFs are exported only when you choose to save them. Gallery albums and exported files remain after uninstalling.
If your gallery has cloud backup enabled, its provider may upload these copies according to your gallery settings. beckenblick does not upload them itself. Marking a private test tank disables sharing in beckenblick, but does not prevent permitted local gallery copies, an explicitly chosen local GIF export or your gallery's cloud backup.
Connecting an additional folder
You can optionally grant read and write access to a specific folder through Android's folder picker. The app creates photo and GIF subfolders. It syncs new photos with the assigned tank when you connect the folder, open the app, take a photo in the app or choose “Sync now”. Existing app photos are also copied during the first sync. There is no deletion sync or permanent background sync service. Local file records and hashes prevent duplicates and unwanted re-imports.
Folder permission is stored until you disconnect or revoke it and is not included in a backup. Choosing a cloud file provider can cause that provider to transfer content. Private test tanks cannot connect to this additional folder feature. Disconnecting does not delete existing files.
4. Widgets, sharing and backups
The app locally converts a selected GIF or video into a short, silent widget frame sequence. The temporary video copy is removed after conversion; the frame sequence stays in app storage. The latest growth GIF is also kept privately per tank for widget use and replaced when a new one is generated.
Only your share action passes a file to an app you select in Android's share menu. The selected app receives read access to that copy. An interactive comparison file contains exactly two JPEG images. Received comparisons are validated and re-encoded locally; they do not replace tank data or automatically enter an album. Watermarks are added only to export copies. Further processing by a recipient or chosen app follows their own rules.
A manually created backup ZIP contains tank data and photos and is not encrypted. Widget frame sequences, the last internally retained GIF, folder permissions and Google Play purchase receipts are not included. Choose the location and recipient carefully. Android's cloud backup and device transfer of private app data are disabled by the app configuration; your own exports and other apps' settings are separate.
External links open the relevant provider only when you tap them.
5. Advertising and privacy choices
The free version has a separate banner area. External ads use Google AdMob. We request non-personalised ads only, which are not chosen from your past interests. Non-personalised does not mean anonymous: technical data and identifiers may still be processed for delivery, frequency limits, billing, measurement and fraud prevention.
Before an ad is requested
Google's User Messaging Platform (UMP) manages privacy choices. Loading and updating the choice screen can itself transfer connection data, particularly your IP address and app identifier, to Google. Choices and consent status are stored so your decision can be respected. Where the GDPR applies, necessary consent management is based on Article 6(1)(c), together with applicable privacy obligations, and where necessary Article 6(1)(f), reflecting our interest in functional and demonstrable consent management. Strictly necessary device access is based on section 25(2)(2) TDDDG.
After a successful current UMP check, the app checks whether ads may be requested. Where consent is required, it additionally checks permission to store/access information on the device and permission for Google as a vendor. Merely declining personalised ads is not sufficient for these checks. Without the required permission, or if the check fails, no external ad is requested. The app does not automatically fall back to “Limited Ads”.
Consent-dependent advertising is based on Article 6(1)(a) GDPR and section 25(1) TDDDG. In regions where UMP does not require consent, non-personalised ads may start after the technical checks without such a consent screen. Where GDPR applies but consent is not required, the basis is Article 6(1)(f), reflecting our interest in funding the free app. You may object using our business contact.
For the international version, the app also signals Google's restricted data processing (RDP) on ad requests. Google applies this where supported and restricts specified processing purposes. This does not mean that no data is transferred. UMP privacy options remain available where Google requires them, including applicable US state privacy messages.
Advertising data and recipients
Google identifies the following possible data categories for its ads SDK: IP addresses and derived approximate location, app and device information, the App Set ID, potentially other identifiers of a signed-in Google account, interactions such as app starts, ad impressions and clicks, and diagnostic/performance data. Data is encrypted in transit. beckenblick removes Android Advertising ID and Android AdServices permissions and does not request GPS location. This does not prevent the other Google processing described here.
Recipients include Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, affiliated companies and service providers, and ad partners named in the relevant privacy screen. Under applicable advertising terms, Google generally acts as a separate controller; for processing covered by RDP, the relevant restricted-processing terms apply. DIY Jan does not create an advertising profile or receive individual Google identifiers as a user list.
Changing your choice and removing ads
Open More → Ad privacy choices to reopen the options Google provides. You can withdraw consent there for future processing. The app removes the current ad and checks the new decision before further requests. Withdrawal does not invalidate earlier lawful processing or automatically erase data Google already holds. If Google provides no choice screen, the app shows that status.
When no external ad is permitted or available, a local Premium promotion may appear, labelled House ad. It makes no ad network request and uses no profile or click tracking. Premium removes both external banners and house ads. Core functions remain usable if you decline ad consent. There is no banner on legal pages, in the camera or during image editing.
Google's information: ads SDK data disclosures, non-personalised ads, restricted data processing, and advertising responsibilities.
7. Transfers and retention
Apart from the described Google services, there is no app-owned server receiving aquarium data. You choose recipients/providers when exporting, connecting folders, opening links or sending messages. Our email provider GMX processes support messages.
Google services may process data outside the EU/EEA, including in the USA. Depending on the company and processing, Google refers to adequacy decisions, including the EU–US Data Privacy Framework for certified companies, and Standard Contractual Clauses. See Google's international transfer information. Not every recipient or transfer uses the same mechanism.
Local tank records remain until you delete them. Temporary copies are replaced or removed as described above. Shared copies in the app cache may remain until cache clearing, system cleanup or uninstalling. Exported files remain at their destination until deleted. Purchase and contact records are kept according to their purposes and legal requirements.
Google's retention periods depend on the data, service configuration, security/billing purposes, account settings and legal obligations. DIY Jan cannot individually delete all these records or set a single retention period. See Google's retention information and privacy policy.
8. Feedback and contact
Feedback opens an email draft with your message and app version. Tank data and photos are not automatically attached. The message is sent only when you send it in your selected email app. Contract-related requests are handled under Article 6(1)(b) GDPR; other enquiries under Article 6(1)(f), reflecting our interest in answering properly. Messages are deleted once resolved unless necessary evidence or legal retention duties require keeping them.
9. Deletion, withdrawal and your rights
You can remove tasks, photos and livestock/plant entries in the app. An app image file is deleted only when no other entry still uses it. Original gallery photos, gallery copies, GIF exports, backups and shared files are not automatically deleted; remove them from their respective locations if needed. Clearing app data in Android or uninstalling removes private app records. DIY Jan has no remote access to these local records.
Subject to applicable law, you have rights of access, rectification, erasure, restriction and portability. Consent can be withdrawn for future processing. You may object to processing based on legitimate interests for reasons relating to your situation, and to direct marketing at any time. Contact [email protected]. Where Google or another provider acts as a separate controller, you can also contact them directly.
You may complain to a supervisory authority, including the Data Protection Commissioner of Lower Saxony. beckenblick does not make solely automated decisions about you that have legal or similarly significant effects.
Visiting this website
This information page loads no advertising, analytics or consent scripts, external fonts or embedded platform content. Our hosting provider Cloudflare processes technical connection information, including IP address, time and requested URL, to deliver the website securely. Where GDPR applies, this is based on Article 6(1)(f). See our website privacy notice (German) for hosting, recipients and your rights. External links contact the respective provider only when you open them.
Legal notice
DIY JanInhaber: Jan Höger
Sandweg 3a
49143 Bissendorf
Deutschland
Geschäftskontakt: [email protected]