Privacy Policy

1. Controller

2. Scope of this policy

This policy describes how personal data is processed in the sahmo mobile app and when you access sahmo.io. sahmo processes voice memos to create transcripts, deterministic metrics and, where available, an AI-based analysis.

3. Data in the mobile app

Guest Session and account

No account is needed for the first memo. A random, memo-specific ownership proof remains in plain text on your device; the backend stores only its cryptographic hash. If you create an account, Supabase Auth processes your account ID, email address or the identifier of the Apple or Google sign-in method you choose, as well as session data. A Guest Session can later assign its memo to that account.

Memo content

Depending on how you use sahmo, we process:

• recorded or imported audio and technical file data,
• the transcript with memo-local speaker assignments,
• deterministic transcript metrics,
• an optional AI-based analysis and the transcript or transcript excerpts used for it,
• processing states, attempts, raw provider responses, failure states and opaque technical IDs.

The audio you record or import determines which personal or sensitive information is included. Upload only content that you are lawfully permitted to have processed.

Notifications

If you agree after the explanation in the processing flow, sahmo processes an Expo push token and the current app language for that memo. The notification contains only the typed completion status and memo ID, not audio, transcript or result content. Push delivery is best effort and may use Apple or Google services.

Technical telemetry

Sentry receives technical error data for the mobile app and backend. sahmo limits this data to approved technical metadata and opaque IDs. Audio, transcripts, memo results, prompts, model inputs and outputs, request bodies, signed URLs and tokens are not sent to Sentry. Mobile replays are captured only for errors; text, images and vectors are fully masked. IP-based location data is suppressed.

Marketing attribution

Adjust measures app installations, sessions and, at most once per installation, the events “first memo submitted”, “first memo result viewed” and “account created”. For this purpose, Adjust may process pseudonymous device and advertising identifiers, the IP address, operating system, device and app version, connection data, timestamps and campaign attribution. Adjust does not receive a sahmo account ID, memo ID, audio content, transcripts or memo result items. Events are associated through the installation.

Adjust does not start if a marketing refusal is already stored. Otherwise, measurement may start in the Guest Session before you make a separate marketing choice. On iOS, the separate ATT system decision controls whether the IDFA may be used. A later refusal disables the SDK and future events but does not delete data already collected by Adjust.

4. Purposes and legal bases

We process data in particular:

• to provide the app functions and account you choose under Article 6(1)(b) GDPR,
• to operate the service securely and reliably under Article 6(1)(f) GDPR,
• on the basis of consent under Article 6(1)(a) GDPR where sahmo expressly asks for it,
• to comply with legal obligations under Article 6(1)(c) GDPR.

The specific legal basis for data contained in a memo also depends on that content and your relationship to recorded people. Your use of sahmo does not replace any consent or other permission you may need from them.

5. Recipients and data regions

sahmo uses the following services for the functions currently planned:

• Supabase for authentication, database and private audio storage in Frankfurt,
• Railway for the website, API and worker in Amsterdam,
• AssemblyAI to transcribe audio,
• Anthropic, Google or OpenAI for the AI analysis of a transcript configured in Labs,
• Sentry for the technical telemetry described above,
• Adjust for the marketing attribution described above,
• Expo and Apple or Google for completion notifications.

The primary data layer is in the EU. This does not determine the data regions of external AI, telemetry, push or marketing providers. Depending on the provider, data may also be processed outside the European Economic Area. Where required, such transfers take place under the legal requirements for international data transfers.

6. Storage and deletion

During upload and processing, the complete audio remains locally on the device. After confirmed completion, the app removes the local audio that is no longer required. The server-side original remains stored for playback until you delete the memo.

After confirmed memo deletion, the memo is no longer accessible. The memo, audio, transcript, memo result and technical processing data may remain internally until a later cleanup; no fixed period is currently promised. Confirmed account deletion also ends access permanently. In the current product iteration, remote memos and their related data remain physically stored. Data already collected by Adjust is currently not deleted when an account is deleted.

We store other data only for as long as required for its purpose or by law. The providers we use may have additional retention periods.

7. Website sahmo.io

Accessing the website generates connection data technically required for delivery, such as the IP address, time, requested URL and browser information. This data is used to deliver the website and keep it secure and stable. The current legal pages do not set analytics or marketing cookies and load fonts only from sahmo.io.

8. Your rights

Subject to the legal requirements, you have rights including access, rectification, erasure, restriction of processing, data portability and objection. You may withdraw consent with effect for the future. You may also lodge a complaint with a data protection authority. To exercise your rights, contact info@ailloy.io.

9. Automated decisions

sahmo automatically creates transcripts, metrics and analyses. These results do not make a decision about you that has legal or similarly significant effects.

10. Changes

We update this policy if the actual processing or legal requirements change. The date shown on this page identifies the current version.