Privacy policy
WHAT MAKEIT IS
makeit lets you save, import and find places, lists and content again (articles, recipes, videos). This policy covers the makeit app for iOS and Android and the backend behind it at https://mkit.offline.rehab.
CONTROLLER
Florian Theil
Email: meetme@offline.rehab
WHAT DATA IS PROCESSED
Account data
Your email address and a password. The password is sent to the backend and stored there only as a bcrypt hash, never in clear text. Sign-in tokens (refresh tokens) are stored as well, also only as a hash, so that you can stay signed in. Purpose: creating your account, securing it and keeping you signed in.
Content you create
Saved places, lists, recipes, articles, videos, notes, the visited status, and the links you import. Purpose: the core function of the app, which is keeping things and finding them again.
Which suggestions you have seen
When the app suggests a place or a piece of content, it records which suggestion that was and what you did with it (seen, dismissed or accepted), with a timestamp. Purpose: not repeating the same suggestion in quick succession, and learning what suits you.
This belongs to your account and is deleted with it. It is not used for advertising, not for reach measurement and not for any analysis across users, and it does not leave the server.
Location data
- In the foreground (only with your permission): when you use a location feature, your current position is read in order to find places near you. The approximate (coarse) position is preferred; the precise position is used if you grant it.
- In the background (separate, explicit consent): only if you turn on „In der Nähe benachrichtigen“ (notify nearby) does the app use geofencing to notify you when you approach a saved place. Your location can then be read while the app is closed. You can switch this off at any time with the toggle in the app or in your device settings.
- There is no continuous, high-precision tracking. Location data is not used for advertising.
Photos
If you pick a photo from your photo library so that a place or a recipe can be read from it, exactly that one image you picked is sent to the backend and from there to a third party for image analysis (see „Recipients“). The app does not read the rest of your photo library and transfers no other images.
If that image carries capture coordinates (many camera apps store them in the image), they are sent along and used only to look for the depicted place near those coordinates instead of anywhere in the world. They are not passed on to the image analysis and are stored only as the location of the recognised entry. If you do not want that, remove the location in your photo library before picking the image, or enter the place by hand instead.
Shared content
When you send a link or a text to makeit through your device's share menu, that link or text is sent to the backend and passed to a third party for automatic recognition of a place, a recipe or an article (see „Recipients“). Linked pages are fetched by the backend; that fetch is limited to publicly reachable web addresses.
For an Instagram post, the app additionally fetches the post's public page directly from your device when you share it, without signing in and without credentials, and sends an excerpt of it (caption, preview image addresses, location tag) to the backend together with the link. As when viewing the post, Instagram learns your device's internet address. The excerpt is used only for your import and is not shared with other users.
Shared videos: audio and still frames
If you share a video (an Instagram reel or a TikTok, say), the backend fetches it publicly, without signing in and without credentials; if the video is not publicly reachable, nothing is fetched. Two things are taken from the video:
- The audio track is sent to a transcription service and turned into text (see „Recipients“). The place, recipe or mentioned titles are then read from that text. Until September 2026 this happened only for cooking videos; it now applies to shared videos generally, because place names and recommendations are often only spoken.
- A few still frames are sent for image analysis in order to read text shown in the video, a list of recommended albums or films for instance.
The transcript text is stored on our server so that the same video does not have to be fetched and processed again every time it is shared. What is stored is the platform, the video id and the text, not the video and not the audio. This storage is not tied to your account: it belongs to the video, not to you.
Social features
If you use the friends feature: your username, existing friendships, invitations and activities (for example that you added a place to a shared list). This data is visible to the people you are connected with.
Camera
The camera is used only to scan friendship QR codes. No audio is recorded and no camera images are stored or transferred.
Notifications
Permission for notifications is only requested once you turn on a feature that needs it. The notification history is stored on the device only. There are two kinds:
- Created locally: hints when you approach a saved place, and suggestions at a fitting time. They are created on the device and do not leave it.
- Delivered as a push: only the result of an import you shared, because that keeps running in the background after you have left the app. For this the app registers a device id (push token) with the backend, and the text of the notification, which names the recognised place or the title of the content, travels through Expo's delivery service and from there through Apple or Google to your device (see „Recipients“).
The push token is an address for your device, not an identifier of you as a person. It is removed as soon as you withdraw notification permission, and at the latest when the account is deleted.
For the locally created notifications you can choose a sparse display in the settings („Details auf dem Sperrbildschirm“, detail on the lock screen): the place name is then replaced by neutral text. This does not affect the import result, because its text is created on the server.
Error reports
If the app crashes or something goes wrong, a technical error report is sent to the service Sentry (see „Recipients“). The report contains the error message and call stack, device and app version. Before it is sent it is cleaned automatically: web addresses are shortened to the host, email addresses and access tokens are removed, user and request data is dropped from the report. Screenshots, view hierarchies, session replay and performance measurement are explicitly switched off. The sole purpose is finding and fixing errors; there is no usage tracking.
Feedback
If you send feedback via „Feedback geben“ / „Give feedback“ or „Falsch erkannt?“ / „Wrongly recognised?“, we store your text, the kind you chose (bug, idea, praise, wrongly recognised), a screenshot if you attach one, and technical details about the app: app version, operating system and its version, language, and the screen you sent it from. For „wrongly recognised“ the affected entry (name and source) is included. The form shows what will be sent before you send it.
The feedback is delivered to the operator by email, plus a short notice as a notification on the operator's phone (via our own server, no third party). Your email address is only included if you allow a reply. Purpose: fixing bugs and improving the app.
WHAT IS EXPLICITLY NOT COLLECTED
- No advertising id and no processing for advertising purposes.
- No analytics SDK and no usage tracking. The only report that leaves the app is the error report on a crash, and that describes the error, not your usage.
- No location history. Your position is used for the request at hand and not stored as a movement profile.
- No sale of your data and no sharing for advertising purposes.
RECIPIENTS (PROCESSORS AND THIRD PARTIES)
For the app to work, data is sent to the following services. Each transfer happens only when you use the corresponding feature.
| Recipient | Data transferred | Purpose |
|---|---|---|
| Google Places and Google Maps (Google LLC / Google Ireland Ltd.) | Location coordinates, search terms, coordinates of saved places | Finding places nearby, resolving place details, photos and opening hours, rendering a map section as the place image |
| OpenStreetMap / Nominatim, Overpass | Location coordinates, search terms, addresses | Resolving addresses and places |
| Google Gemini (Google LLC / Google Ireland Ltd.) | Links and texts you shared, photos you picked, still frames of shared videos, and as a fallback their audio track | Automatic recognition of a place, recipe, article or mentioned titles from the shared content |
| Groq (Groq, Inc.) | Audio track of shared videos | Turning speech into text (transcription). If Groq does not answer, Google Gemini takes over the same task. |
| Anthropic (Anthropic PBC) | Links and texts you shared, photos you picked | The same recognition as a fallback when Gemini does not answer or returns no result |
| Email delivery | Your email address; for feedback, its content including any screenshot | Resetting your password; delivering your feedback to the operator |
| Expo (650 Industries, Inc.) as well as Apple (APNs) or Google (FCM) | Your device's push token, the text of the notification (name of the recognised place or title of the content) | Delivering the result of a shared import |
| Sentry (Functional Software, Inc.) | Cleaned error report: error message, call stack, device and app version | Finding and fixing crashes and errors |
Error reports are stored in Sentry's EU data centre. Push notifications are delivered through servers in the USA; this happens only if you share an import and have allowed notifications.
The analysis services (Google Gemini, Anthropic, Groq) process the transferred content in order to derive structured data from it. With these providers, processing may take place outside the EU, in particular in the USA.
Do not send content that you would not want passed to these services. Photos and shared texts are only ever transferred when you actively pick or actively share them.
LEGAL BASES
- Performance of a contract (Art. 6(1)(b) GDPR): account, sign-in, storing and showing your content, social features.
- Consent (Art. 6(1)(a) GDPR): access to location, photo library, camera and notifications. You give it through the respective system dialogue and can withdraw it at any time in your device settings.
- Legitimate interest (Art. 6(1)(f) GDPR): operational security, in particular protection against abuse through rate limits, as well as error reports for the stability of the app.
RETENTION AND DELETION
Account data and the content you create are stored until you delete your account. You can delete your account directly in the app (Account, Danger zone, „Konto und alle Daten löschen“, confirmed with your password). Your account and its content are then removed from the backend and the local app state on the device is cleaned up (sign-in tokens, caches, geofence data, notification history); background location use is stopped.
Feedback, including any screenshot, is stored until you delete your account, or earlier on request to the address below.
Sign-in tokens (refresh tokens) are invalidated when you sign out. The record of which places were suggested to you (so that suggestions do not repeat) and the list of your sharing jobs (with the shared link) are deleted after 90 days. To measure whether makeit keeps being used, we record for each account the days on which the app was used (the date only, no time, no content); this is not shared with third parties and is deleted after 400 days. Password reset codes can be used once, are time-limited and are stored only as a hash. Push tokens are removed as soon as you withdraw permission, at the latest together with the account. Error reports sit with the provider and are deleted there according to its retention periods.
Stored transcripts of shared videos are not tied to any account and are therefore unaffected by deleting an account. They contain the publicly spoken word of a publicly available video, no information about you. On request to the address below, an individual transcript will be removed.
Instructions for deletion are at https://mkit.offline.rehab/account-deletion. An informal message to meetme@offline.rehab is enough as well.
SECURITY
Transfers are encrypted over HTTPS only. Passwords are hashed with bcrypt. Sign-in tokens are kept on the device in secure system storage (iOS Keychain or Android Keystore), not in ordinary app storage. The import endpoints are rate-limited per account.
YOUR RIGHTS
Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw a given consent at any time with effect for the future. Write to meetme@offline.rehab.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).
CHILDREN
makeit is not directed at children under 16. Data of children under 16 is not knowingly processed.
CHANGES
This policy is adjusted when the app changes. The current version is at https://mkit.offline.rehab/privacy; the date above states when it was last updated.
CONTACT
Florian Theil · meetme@offline.rehab