Privacy Policy
maklly is developed by Eduard Uffelmann (“we”, “us”). This policy explains what data the maklly iOS app collects, how it is used, and who it is shared with.
The short version
Your recordings, photos, and location tags stay on your device. They only ever leave it if you explicitly export or send them somewhere — to a transcription service to get a transcript, or to a destination you connect yourself (Notion, Todoist, Slack, onOffice, Files, or the share sheet). We don’t run ads, we don’t use analytics or tracking SDKs, and we don’t sell data.
Audio recordings
maklly uses your microphone to record voice memos when you tap record. Recordings are saved as audio files in the app’s local storage on your device. To get a transcript, the recording is sent to a transcription provider, in one of two ways:
- Your own API key. If you’ve added your own OpenAI API key in Settings, the recording is sent directly from your device to OpenAI’s Whisper transcription service using your key, under OpenAI’s own privacy and data-handling terms.
- maklly’s built-in transcription. If you use the built-in option instead, the recording is sent to our backend (hosted on Supabase, in the EU), which forwards it to our transcription provider (AssemblyAI) and returns the text to your device. The audio is a pass-through — it is not stored on our servers before, during, or after transcription. We keep a record of how many seconds of audio were transcribed, tied to an anonymous device identifier (see “Subscriptions” below), so we can track usage and enforce plan limits. We do not keep the audio itself or the resulting text.
Photos
maklly uses your camera to photograph rooms and details during a walkthrough. Photos are saved to the app’s local storage on your device and are never uploaded to our servers.
Location
With your permission, maklly uses your device’s location (only while the app is in use) to tag each recording with where it was made. This location data is stored locally on your device and is not transmitted to us.
Properties, areas, and transcripts
Property names, area names, notes, and transcripts you create are stored locally in the app’s database on your device. They are not synced to any server we operate. If you use Apple’s Files app or iCloud Drive to save or back up app data, that happens through your own iCloud account, under Apple’s privacy terms — we have no access to it.
Exporting and sending your data elsewhere
When you finish a walkthrough, you can export a report (a PDF, the transcript text, and your photos) and save it to Files or share it through iOS’s share sheet — to Mail, AirDrop, WhatsApp, or anywhere else you choose. That destination is entirely up to you and is not something we have access to.
You can also connect the following destinations and send a transcript directly to them. Each requires you to provide your own access token, webhook URL, or account credentials for that service, and delivery happens directly from your device to the destination — it does not pass through our servers:
- Notion, Todoist, Slack — you paste in a token or webhook URL from your own account; the transcript text is sent straight to that service using your credentials.
- onOffice — for agents using the onOffice real estate CRM, you provide an API token and secret from your onOffice account; the transcript text and recording length are sent directly to your onOffice account as a log entry. The audio recording itself is never uploaded.
We never see the content you send through these destinations, and we don’t store your access tokens anywhere but your device’s Keychain.
Subscriptions and purchases
In-app purchases are processed by Apple through the App Store. Subscription status is tracked using RevenueCat, associated with a random identifier generated on your device and stored in your device’s Keychain. This identifier is not linked to your name, Apple ID, or email address, and we don’t receive your payment details — Apple handles those directly.
What we don’t do
- No advertising or ad networks
- No analytics, crash-reporting, or tracking SDKs of any kind
- No selling or sharing of your data with third parties for their own purposes
Where data is processed
Our backend (used only for built-in transcription and subscription entitlement checks) runs on Supabase infrastructure located in the EU (Frankfurt, Germany). If you use your own OpenAI API key or connect a third-party destination, that data is processed by that provider under its own privacy policy and may be processed outside the EU.
Data deletion
Deleting a recording, photo, property, or area in the app deletes it from your device immediately. Because we don’t store audio, transcripts, photos, or your organizational data on our servers, there is nothing further for us to delete on our end beyond the anonymous usage counters described above. To have those usage counters removed, contact us at the address below.
Children
maklly is not directed at children and we do not knowingly collect data from anyone under 13.
Changes to this policy
If this policy changes, we’ll update the effective date above. Material changes will be reflected here before they take effect.
Contact
Questions about this policy or your data: e@uffelmann.me