Privacy Policy
Last updated: 28 October 2026
Micnoteai is an iOS app that records or imports audio, PDFs and YouTube links, turns them into transcripts and AI-generated summaries, and lets you ask questions about your own notes in a chat. To do that, the content you give the app is uploaded to our backend server, processed there, and stored in your account so it can be synced back to your devices. We do not sell your personal information and the app contains no advertising or ad-tracking SDKs. To measure our own App Store ads, the app uses Apple's privacy-preserving ad attribution, which does not use advertising identifiers or track you across other apps (see section 3). This policy explains exactly what is collected, why, how long it is kept, and what rights you have over it.
1. Who we are
Micnoteai is developed and operated by Hamid Manafov, an individual developer based in Azerbaijan. Hamid Manafov is responsible for the personal data described in this policy (the data controller).
For privacy requests and app support, email support@micnoteai.com. A postal contact address is available on request.
Privacy requests are handled directly by the developer. No separate Data Protection Officer or EU/UK representative is currently appointed. This does not limit your privacy rights or our obligations under applicable law.
2. Scope of this policy
This policy applies to the Micnoteai iOS app, the servers used to provide it, and the Micnoteai website.
It does not apply to:
- Apple. Your App Store account, App Store purchases, Sign in with Apple, iCloud and push notification delivery are governed by Apple's own privacy policy. We receive only what Apple passes to us, described in section 3.
- Google. If you choose Google Sign-In, Google's handling of your Google Account is governed by Google's privacy policy.
- Third-party content you point the app at. If you submit a YouTube link, the video is fetched and processed on our side; YouTube's own terms and privacy policy still apply to your use of YouTube.
- Other websites that this policy or the app may link to.
The app is intended for people aged 13 or over, and 16 or over in the EEA, the UK and Switzerland. A higher minimum age applies where required by local law. These are the service eligibility requirements described in our Terms of Use; see section 13 for how we handle children’s information.
3. Information we collect
The table below describes the categories of personal data the app handles, where it comes from, why we need it, and — for users in the EU/UK — the legal basis under Article 6 GDPR. The app has no email/password sign-up: you can only sign in with Apple or Google, so we never receive or store a password.
| Data category | Examples | Source | Why we collect it | Legal basis (GDPR) |
|---|---|---|---|---|
| Account & identity data | Account ID, email address, full name, locale, time zone, account creation/update dates, premium status | Returned by Apple or Google when you sign in, then stored by our backend. Sign in with Apple requests only your name and email; if you use Apple's "Hide My Email", we only ever see the relay address. | To create and identify your account, sync your notes across devices, and reply to support requests | Art. 6(1)(b) — performance of a contract (providing the app to you) |
| Authentication credentials | Sign-in tokens, an account identifier and temporary sign-in verification data | Issued by our backend during sign-in; stored on your device in the iOS Keychain (accessible only after first unlock, this device only) | To keep you signed in securely and to protect sign-in against replay and interception attacks | Art. 6(1)(b) — contract; Art. 6(1)(f) — legitimate interests in account security |
| Audio recordings | .m4a recordings you make in the app or audio files you import, plus title, duration and language |
Created by you in the app (microphone) or chosen by you from your device. Uploaded to our backend for processing. | To transcribe and summarise the recording — this is the core function of the app | Art. 6(1)(b) — contract |
| Imported documents and links | PDF files you import; YouTube URLs you paste | Provided by you and uploaded/submitted to our backend. For a YouTube link, the app also asks Google directly for the video's title and thumbnail to show you a preview, which means your IP address reaches Google (see section 7). | To extract the text and produce a summary you asked for | Art. 6(1)(b) — contract |
| Note content (transcripts and summaries) | Transcript text and timed segments, AI summary, note title, detected transcript/summary language, speaker names you assign, folders, pin and archive flags, processing status and error details | Generated by our processing pipeline from the content you submit, plus edits you make. Stored on our backend and mirrored to an offline cache on your device. | To show you your notes, let you edit and organise them, and sync them between your devices | Art. 6(1)(b) — contract |
| AI chat content | The questions you type in a note's chat and the conversation history sent with them | Typed by you; sent to our backend, which forwards it to an AI provider together with the relevant note | To answer your questions about your own note | Art. 6(1)(b) — contract |
| Onboarding preferences | Preferred language, your stated goals, profession, and the display name you enter during onboarding | Entered by you. Stored locally on your device (app settings); the display name may also be saved to your profile on our backend. | To tailor the app's language and initial setup to you | Art. 6(1)(b) — contract; Art. 6(1)(f) — legitimate interests in a usable first-run experience |
| Device & technical data | Push notification device token and a hash used to detect re-registration, app badge count, app version, device model, operating system version, coarse locale/region | Generated by your device and the app; the push token comes from Apple Push Notification service | To deliver notifications about your notes finishing processing, and to keep the app working correctly across device and OS versions | Art. 6(1)(b) — contract (notifications you enabled); Art. 6(1)(f) — legitimate interests in operating the service |
| IP address | The IP address your device connects from | Seen by our servers on every request, as it is by any internet service | Used temporarily in security logs and short-lived request-limit records to protect sign-in and prevent abuse. Some limits use your IP address; others use your account. We do not use IP addresses for advertising profiles. | Art. 6(1)(f) — legitimate interests in operating and protecting the service |
| Purchase & subscription data | Whether you have an active premium subscription, subscription product and status, usage limits and counters, a purchase identifier linked to your account | Apple's App Store handles the payment; subscription state reaches us through RevenueCat and our backend. We never receive your card number or billing address. | To unlock the features you paid for, enforce free-tier limits, and handle restore-purchases and refunds | Art. 6(1)(b) — contract; Art. 6(1)(c) — legal obligation (tax and consumer-law record keeping) |
| Ad campaign attribution | Whether the app was installed after tapping one of our Apple Ads (formerly Apple Search Ads) ads and, if so, the campaign, ad group, keyword and country of that ad, and the date of the tap or install | The app requests an attribution token from Apple's AdServices framework and sends it to RevenueCat, which asks Apple for the attribution result and stores it with the purchase identifier linked to your account. For installs that did not come from our ads, Apple returns no campaign data. No advertising identifier (IDFA) is used and no tracking permission is requested. | To measure which of our own App Store ad campaigns lead to installs and subscriptions, so we can decide where to spend our advertising budget | Art. 6(1)(f) — legitimate interests in measuring the effectiveness of our own advertising. You can object by emailing support (see section 10). |
| Product analytics & diagnostics | In-app events such as screens opened, notes created, paywall shown/dismissed, feature usage; an analytics identifier linked to your account when you sign in; app and device metadata attached to those events | Collected by the app through PostHog, hosted in the EU (Frankfurt). Contains no recording audio, transcript text or chat content. | To understand which features are used, find crashes and broken flows, and decide what to improve | Art. 6(1)(f) — legitimate interests in improving and maintaining the app. You can object to analytics by emailing support (see section 16). |
| Device-level usage and app verification | A count of notes created on the device, and app-integrity verification identifiers and proofs | Generated by the app and Apple’s App Attest service. The usage count is kept in secure device storage and can survive account deletion and reinstallation. | To enforce device-level free-tier limits and protect the service against automated abuse | Art. 6(1)(f) — legitimate interests in preventing abuse and protecting the service |
| Support correspondence | Your email address and whatever you write to us | Sent by you by email | To answer your question or handle your privacy request | Art. 6(1)(f) — legitimate interests; Art. 6(1)(c) — legal obligation for rights requests |
Special-category data. We do not ask for and do not intentionally collect sensitive data (health, biometric, religious, political or sexual-orientation data). However, a recording is whatever you recorded — if you record a medical appointment or a personal conversation, that content may contain sensitive information about you or others. Please only record where you are legally allowed to (see section 5).
Using the app without an account. The app lets you browse onboarding as a guest, but no account is created and the app returns you to the sign-in screen. Practically, an account is required to create and process notes.
What we do not collect. We do not collect passwords, precise or background location, contacts, photos beyond the file you explicitly import, advertising identifiers (IDFA), or any data for ad targeting or cross-app tracking. The app contains no advertising SDKs and shows no ads. The only advertising-related data we handle is the ad campaign attribution described above, which we use solely to measure our own Apple Ads campaigns.
4. How we use your information
We use the data described above only for the following purposes:
- To provide the core service — receiving your audio, PDF or YouTube link, transcribing it, generating a summary, and storing the resulting note in your account.
- To sync and display your notes across your devices, including keeping an offline copy on the device so your notes are readable without a connection.
- To run the AI chat so you can ask questions about a specific note.
- To manage your account — signing you in, keeping the session alive with refresh tokens, letting you sign out of one or all devices, and deleting your account when you ask.
- To handle subscriptions — checking whether you have premium, applying free-tier usage limits, and restoring purchases.
- To notify you when a note has finished processing or failed, if you allowed notifications.
- To keep the service secure and reliable — preventing replay attacks on sign-in, rate-limiting abuse, retrying failed uploads, and diagnosing errors.
- To improve the app — reviewing pseudonymous product analytics to see which features are used and where flows break.
- To measure our own advertising — seeing which of our Apple Ads campaigns and keywords lead to installs and subscriptions. This is not used to show you ads or to profile you.
- To comply with the law — meeting tax, accounting and consumer-protection obligations, and responding to valid legal requests.
We do not:
- sell or share your personal information for money or for cross-context behavioural advertising;
- use your recordings, transcripts, notes or chats to build advertising or marketing profiles;
- make decisions about you that produce legal or similarly significant effects using solely automated processing.
If we ever want to use your data for a genuinely new purpose that is not compatible with the purposes above, we will update this policy and, where the law requires it, ask for your consent first.
5. Audio recordings and transcription
Because audio is the most sensitive thing the app handles, here is precisely what happens to it.
Recording
Recording only starts when you tap record, and iOS requires you to grant microphone permission before the app can access the microphone. You can withdraw that permission at any time in iOS Settings → Privacy & Security → Microphone; without it, recording stops working but the rest of the app still functions. The app does not record in the background without your knowledge and does not listen when you are not recording.
Storage on your device
Each recording is written to disk as an .m4a file inside the app's own Documents area, in a private folder associated with your account. These files are protected by iOS app sandboxing and the device's file-level encryption while the device is locked. The app does not add a second layer of its own encryption on top.
Backup. Once a recording has been uploaded successfully and is kept on the device, the app marks the file as excluded from backup, so it is not copied into your iCloud backup or an iTunes/Finder backup — the copy on our server is the one that survives a device restore. A recording that has not yet been uploaded (for example one still waiting in the offline queue) is not excluded, and is therefore included in your backups according to your own iOS backup settings. The offline note cache is likewise excluded from backup.
Keeping recordings on your device
By default, recordings stay on your device after they have been uploaded. This is deliberate: it lets the app play the original audio back to you instantly, without re-downloading it, and lets you check the transcript against what was actually said. You are in control of it — the app has a "keep local audio" switch in Settings. Turn it off and each recording is deleted from the device as soon as its upload has completed successfully; the note and its transcript are unaffected, and playback then streams from our server instead, which needs a connection. Turning the setting off also clears the local playback references for your account. The setting belongs to the device, not to the account, so it applies to whoever is signed in on that device. The app never deletes a local recording before its upload has succeeded.
Upload and processing
To transcribe a recording, the app uploads it to our servers over an encrypted connection, together with its title, duration and language. A connection is needed for processing. If an upload fails or you are offline, the app keeps a pending copy and can retry later. PDFs are uploaded for text extraction; submitted YouTube links are processed on our servers.
Retention of audio
On the server, the audio file is retained after processing so that the note can offer audio playback alongside the transcript. It is not deleted immediately after transcription. It is stored in Amazon S3 in Frankfurt, Germany, and there is no automatic age-based deletion — the file is kept for as long as the note exists. Deleting the note or your account also requests removal of its stored file; background cleanup and retries can take time (see section 8). Playback links handed to your app are signed CloudFront URLs that expire after one hour, so a link cannot be shared or reused indefinitely.
On your device, unless you turn the "keep local audio" setting off, the app keeps a local copy of the recording and a mapping of which file belongs to which note, as described above. Deleting a note deletes its server-side record; deleting your account deletes all local recordings in the background as part of the cleanup described in section 10.
Who can hear your recordings
Your recordings and transcripts are tied to your account and are not shared with other users. They are accessible to our processing pipeline and to the transcription provider used to convert speech to text, and to the developer only where strictly necessary to investigate a fault you have reported. The transcription providers we may use are listed in section 6.
Recording other people
Laws about recording conversations differ by country and by US state — some require every participant's consent. You are responsible for making sure you have the right to record, and for telling the other participants when the law requires it. If someone else's voice ends up in your recording, you are acting as the person who decided to record them.
6. AI features
Micnoteai uses AI models for speech transcription, processing imported PDFs and submitted YouTube links, generating note summaries and titles, translation, and answering questions about a note.
Your choice before sharing
Before this version of the app sends new content for AI processing, it shows an in-app explanation of the data and recipients and asks you to choose Agree and continue or Not now. Completing onboarding or granting microphone permission does not grant AI-sharing permission. The app stores your choice, the disclosure version and the decision time on this device for your signed-in account. A different account or an updated disclosure requires its own decision.
You can decline and continue viewing existing notes. Features that require new AI processing remain unavailable until you agree. You can change your choice in Settings → AI processing and select Stop AI sharing. This blocks new AI requests from this installation, including upload retries. It does not recall content already transmitted, cancel processing already accepted by our servers, or delete existing notes. To delete content, use the note or account deletion controls described in this policy.
How content reaches the AI
The app sends content to our servers over an encrypted connection. Our servers pass the content needed for the requested task to an AI provider. We do not intentionally send your profile name or email address, but the content itself may identify you or other people. File names or temporary file links may also contain a note or account identifier.
What is sent
- Transcription: the audio you recorded or imported.
- PDF processing: the PDF you selected and its contents.
- YouTube processing: the link you submitted and video content or transcripts used to produce the note.
- Summarisation: the transcript or extracted document text of that one note.
- Translation and reprocessing: the relevant source content, existing note text and your chosen language.
- Note chat: the message you typed, the earlier messages in that conversation, and the content of the note you are asking about. Only the note you have open is included — the AI is not given your whole library.
AI services we use
Micnoteai uses OpenAI and Google Gemini for AI-powered features. Content needed for your request is shared through our servers for processing, as described above.
Content and file information. Providers receive the content needed for the task and its language. Audio, text or file information may contain personal information, even though we do not separately send your profile details.
Training
We do not use your recordings, transcripts, notes or chat messages to train our own AI models, and we do not sell or license them to anyone for that purpose. We use AI providers under business/API terms rather than consumer terms, which ordinarily excludes customer content from provider model training. We cannot promise on their behalf that they are contractually barred from training on the content, and each provider sets its own retention period for abuse monitoring. If this matters to you, read the API terms of the providers listed above before submitting sensitive material.
Accuracy
Transcripts and AI summaries are generated automatically and can be wrong, incomplete, or misattributed to the wrong speaker. They are not a verbatim legal record, and they are not professional advice. Please check anything important against the original recording — which is why the app keeps the audio available.
7. Sharing and disclosure
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We have never done so, and we receive no money or other valuable consideration for your data.
The following table describes service providers and the data used to deliver the stated features.
| Recipient | What is shared | Purpose | Where to find their policy |
|---|---|---|---|
| Apple Inc. | Your App Store account and payment details (handled entirely by Apple — we never see them); the sign-in token if you use Sign in with Apple; your push notification device token and notification payloads | App distribution, subscription payment and billing, Sign in with Apple, delivery of push notifications through Apple Push Notification service; app-integrity verification through App Attest; attribution of installs to our Apple Ads campaigns through the AdServices framework | apple.com/legal/privacy |
| Google LLC | Only if you choose Google Sign-In: the sign-in exchange between your Google Account and the app, which returns an ID token to us | Authenticating you with your Google Account | policies.google.com/privacy |
| RevenueCat, Inc. | A purchase identifier linked to your account, your App Store receipt/subscription status, basic device and app metadata, and the Apple ad attribution token and its result (see section 3). No recordings, transcripts or chat content. | Managing subscription entitlements, verifying receipts, restoring purchases; measuring which of our Apple Ads campaigns lead to subscriptions | revenuecat.com/privacy |
| PostHog (EU Cloud, Frankfurt, Germany) | Product-analytics events, an analytics identifier linked to your account when signed in, and app/device metadata. No audio, transcript text, note content or chat content. | Understanding feature usage and diagnosing broken flows so the app can be improved | posthog.com/privacy |
| AI services — OpenAI and Google Gemini | Content needed for the selected AI feature, as described in section 6. We do not separately send your profile name or email. Content, file names or links may contain identifying information. | AI processing for the features described in section 6 | openai.com/policies, policies.google.com/privacy |
| Hetzner Online GmbH (European Union) | Everything our application servers and databases hold: the account record, transcripts, summaries, note metadata and chat history | Hosting the application servers and databases that provide Micnoteai | hetzner.com/legal/privacy-policy |
| Amazon Web Services (file storage in Frankfurt, Germany, and file delivery) | Your uploaded audio files and PDF documents | Storing the files your notes are made from and delivering them back to you over time-limited signed links | aws.amazon.com/privacy |
| Cloudflare | Website requests and connection information, including IP address and browser metadata | Hosting and protecting this informational website. The website does not contain a separate analytics script or a content-upload form. | Cloudflare privacy policy |
| YouTube / Google LLC | The video URL you paste. Two separate requests reach Google: our backend fetches the video's content, and — before you confirm — your device itself asks Google's public oEmbed endpoint (video preview service) for the video's title and channel name and downloads the thumbnail image from Google’s image servers. Those two requests come from your device, so your IP address, approximate device/browser metadata and the video ID reach Google. No account identifier, recording, transcript or note content is sent. | Retrieving the video you asked us to summarise, and showing you a preview card with the video's title and thumbnail so you can confirm you pasted the right link | policies.google.com/privacy |
We may additionally disclose personal data:
- To comply with the law — in response to a valid court order, subpoena or other binding legal request, or to establish, exercise or defend legal claims. We will tell you about such a request unless we are legally prohibited from doing so.
- To protect people — where disclosure is necessary to prevent fraud, abuse of the service, or a serious threat to someone's safety.
- In a business transfer — if the app is ever sold or transferred, your data may pass to the acquirer, who would remain bound by this policy until you are notified of any change. You would be told before your data became subject to a different policy.
8. Data retention
We keep personal data for the purpose described below. Deletion is a process, not a promise that every copy disappears instantly. Background cleanup, retries and service-provider retention can affect when removal finishes.
| Data | Retention and deletion |
|---|---|
| Account profile | Kept while your account exists and removed through account deletion, subject to the limited security, billing and deletion records below. |
| Audio, PDFs, submitted links, transcripts, summaries and chat | Kept with the note, without an automatic age-based expiry. Deleting a note or account starts removal of the associated content and files. Processing copies and security records have separate retention below. |
| Local recordings, pending uploads and offline notes | Kept to support offline access, playback and upload recovery. Local storage controls and account deletion remove the relevant files. Signing out or a session expiring does not necessarily erase local recordings or pending uploads. Removing the app removes its local app data, but secure device-level records and copies in your backups may remain. |
| Sign-in credentials | Kept in secure device storage until expiry or removal on sign-out or account deletion. |
| Device-level free-tier count | Persists in secure device storage without an automatic expiry. It is not reset by sign-out or account deletion and can survive reinstalling the app. It records usage count, not recording or note content. |
| Account-level usage counters | Some counters can remain after account deletion to prevent abuse. Their configured cleanup period is normally one year after account deletion. |
| App settings and onboarding answers | Kept locally until cleared through the applicable settings, account cleanup or removal of the app. An analytics-objection preference may be retained to keep your objection in effect. |
| Push and app-integrity records | Kept as needed for notification delivery, app verification and security. Records may expire, be replaced or be removed during account cleanup. |
| AI usage counts | The configured retention period is normally 365 days. These records measure usage rather than store note content. |
| AI processing records | May contain input and generated text. Account deletion requests a purge. Completed and failed records also have a configured 30-day cleanup period. Stalled records and unsuccessful purge requests may require manual cleanup. |
| Security audit records | May remain after account deletion for security and abuse prevention. Account cleanup removes content fields and replaces the account identifier with a derived identifier; retained metadata can include note identifiers, actions and dates. The configured retention period is normally two years. |
| Purchase, subscription and deletion records | Limited identifiers and records may remain for billing reconciliation, handling disputes, meeting applicable record-keeping requirements and documenting deletion. Apple and RevenueCat apply their own retention rules. |
| Ad campaign attribution | Stored by RevenueCat with the purchase identifier linked to your account and subject to RevenueCat's retention rules. Contact us to request its removal. |
| Analytics | PostHog applies the retention configured for our project. Resetting the app’s analytics identifier does not itself erase previously collected events. Contact us for the applicable period or to exercise your rights. |
| Support correspondence | Up to 24 months after the conversation ends, unless a legal obligation or unresolved request requires longer retention. |
| Security logs and temporary request limits | Server logs rotate as new entries arrive; temporary request-limit records expire after their enforcement window. Logs can contain IP addresses and technical identifiers. Error logs may occasionally include a short excerpt of a provider response, which can contain transcript text. |
Our cleanup routines can be delayed by outages or failures. A failed cleanup may need developer intervention. Email support@micnoteai.com if you need confirmation that a deletion has completed or want us to review retained records. Copies already sent to service providers are also subject to their terms and retention requirements; we cannot promise immediate removal of every provider-held copy.
Where a legal obligation requires us to retain a record, we retain only what is needed for that obligation. Retained security records are not used to restore deleted notes or build advertising profiles.
9. Data storage and international transfers
Your data is processed primarily in the European Union. Our application servers and databases are hosted by Hetzner in the EU. Uploaded audio and PDFs are stored by Amazon Web Services in Frankfurt, Germany. Product analytics use PostHog’s EU Cloud in Frankfurt. Website delivery and third-party processing may involve other locations.
Personal data nevertheless leaves the EEA in two situations. First, the developer is based in Azerbaijan, which is outside the European Economic Area and is not covered by a European Commission adequacy decision, so administrative access to the service takes place from Azerbaijan. Second, some service providers operate outside the EEA — the AI providers listed in section 6, and Apple, Google and RevenueCat, which are US companies. This means your personal data may be transferred to, stored in, or accessed from countries outside your own, including the United States, which may not offer the same level of data protection as your home country.
When we transfer personal data out of the EEA, the UK or Switzerland, we rely on a lawful transfer mechanism under Chapter V GDPR:
- Standard Contractual Clauses (Article 46(2)(c) GDPR), in the European Commission's 2021 form, together with the UK International Data Transfer Addendum where UK data is involved — this is our default basis with service providers;
- an adequacy decision (Article 45 GDPR), where the destination country has one;
- certification under the EU–US Data Privacy Framework, where the provider is certified.
We also carry out a transfer risk assessment where required and apply supplementary measures such as encryption in transit and access controls. You can ask us for a copy of the safeguards that apply to a specific transfer by writing to support@micnoteai.com.
10. Your rights under GDPR
If you are in the European Economic Area, the United Kingdom or Switzerland, you have the following rights over your personal data. They are free to exercise, and we will respond within one month (extendable by two further months for complex requests, in which case we will tell you why).
- Access (Art. 15) — ask whether we hold data about you and get a copy of it, together with information about how it is used.
- Rectification (Art. 16) — have inaccurate data corrected. You can edit your display name, note titles and note content directly in the app.
- Erasure (Art. 17) — have your data deleted. You can do this yourself at any time (see below).
- Restriction (Art. 18) — ask us to stop processing your data while a dispute about its accuracy or our legal basis is resolved.
- Portability (Art. 20) — receive the data you gave us, and the notes generated from it, in a structured, commonly used, machine-readable format, and have it sent to another provider where technically feasible.
- Objection (Art. 21) — object to processing based on our legitimate interests, including product analytics and ad campaign attribution. We will stop unless we can show compelling legitimate grounds that override your interests.
- Withdraw consent (Art. 7(3)) — where processing is based on consent, withdraw it at any time, without affecting processing that already happened. Withdrawing microphone or notification permission in iOS Settings has immediate effect.
- Not to be subject to automated decision-making (Art. 22) — we do not make decisions with legal or similarly significant effects about you by automated means.
Deleting your account
To delete your account, open Settings → Delete account in the app. This requests removal of your profile, notes and associated audio or documents, and clears account data and recordings on the device. Removal across services may take time and failed cleanup may require intervention. The limited records that can remain, including device usage counters, are explained in section 8.
Account deletion is permanent and cannot be undone: there is no soft delete, no recycle bin and no restore window, so please export anything you want to keep beforehand. Deleting a single note requests removal of that note and its stored audio or document; cleanup can take time. The narrow exceptions that survive deletion are listed at the end of section 8. Account deletion does not cancel an active App Store subscription — you must cancel that in iOS Settings → your name → Subscriptions, because only Apple can manage the subscription and any refund.
How to exercise your other rights
Email support@micnoteai.com from the address associated with your account and tell us what you want. We may need to ask a question or two to confirm you are the account holder — we do this to stop someone else obtaining or deleting your notes, and we will not ask for more identifying data than we need.
Complaints
If you believe we have handled your data unlawfully, we would like the chance to put it right, so please contact us first. You also have the right to lodge a complaint with a data protection supervisory authority — in the EEA, the authority in the country where you live, work, or where the alleged infringement took place; in the UK, the Information Commissioner's Office (ico.org.uk). A list of EEA authorities is published at edpb.europa.eu.
11. Your rights under CCPA/CPRA
If you are a California resident, the California Consumer Privacy Act as amended by the California Privacy Rights Act gives you the rights described below.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined by the CCPA/CPRA. We have not done so in the preceding 12 months, and we do not sell or share the personal information of consumers under 16 years of age. Because we do not sell or share, there is no "Do Not Sell or Share My Personal Information" link to provide — but if this ever changes, we will update this policy and offer an opt-out before it takes effect.
Categories collected. In the past 12 months we have collected the categories described in section 3, which map to the CCPA categories of identifiers (account ID, email, device and push tokens), customer records (name, email), commercial information (subscription and purchase status, and the Apple Ads campaign that led to the install, if any), internet or network activity (in-app product analytics), audio and electronic information (your recordings, transcripts and chat content), and inferences drawn from your onboarding answers. The sources, purposes and recipients are set out in sections 3, 4 and 7.
Sensitive personal information. Your recordings and transcripts may contain whatever you chose to record. We use that content only to deliver the service you asked for — transcription, summarisation and chat — and never to infer characteristics about you. We therefore do not use or disclose sensitive personal information for purposes beyond those permitted by CPRA section 1798.121, and no right to limit its use applies.
Your rights are:
- Right to know — request the specific pieces of personal information we hold about you, and the categories collected, the sources, the business purpose, and the categories of third parties they were disclosed to.
- Right to delete — request deletion of your personal information, subject to the exceptions in the statute (for example records we must keep for tax purposes). You can exercise this immediately yourself with Settings → Delete account in the app.
- Right to correct — request correction of inaccurate personal information; most fields are editable directly in the app.
- Right to opt out of sale or sharing — available to you even though we do not sell or share.
- Right to limit the use of sensitive personal information — see the paragraph above.
- Right to non-discrimination — we will never deny you service, charge you a different price, or give you a lower quality of service because you exercised a privacy right. We offer no financial incentives in exchange for personal information.
How to submit a request. Email support@micnoteai.com with "CCPA request" in the subject line, or use the in-app deletion flow for deletion. We will confirm receipt within 10 business days and respond within 45 days, extendable once by a further 45 days if we tell you why. We verify requests by matching the email address on the request to the account, and by asking about account details only you would know. An authorised agent may submit a request on your behalf with written permission signed by you, and we may still contact you to confirm it.
12. Device permissions
| Permission or action | Purpose and your choice |
|---|---|
| Microphone | Needed to record audio. Recording starts only when you choose it. You can change microphone access in iOS Settings. If you decline, you can still import supported files and use existing notes. |
| Notifications | Optional notifications about processing completion or failure. You can change notification access in iOS Settings; note processing works without notifications. |
| File import | The system file picker gives the app access to the file you choose. It does not grant ongoing access to your entire file or photo library. |
The app does not request access to your location, contacts, calendar, camera or health data. It does not use advertising identifiers or track you across other companies’ apps for advertising.
13. Children's privacy
Micnoteai is intended for people aged 13 or over, and 16 or over in the EEA, the UK and Switzerland. A higher minimum age applies where local law requires it. Users below the age of majority must meet the parental-involvement requirements in our Terms of Use.
We do not knowingly collect personal data from children below these minimum ages. We do not currently ask for a date of birth; Apple or Google sign-in is not proof that a user meets our age requirements. If you believe a child below the required age has provided personal data, contact support@micnoteai.com so we can investigate and arrange deletion.
14. Security
We use encrypted connections, access controls, iOS secure credential storage and app-integrity checks to protect the service. Local recordings and cached notes rely on iOS device protection and app isolation; the app does not add separate end-to-end encryption. Our servers and processing providers must be able to access the content needed for transcription, summaries and chat.
File playback uses temporary signed links. These links expire, but anyone who obtains a valid link may be able to use it before expiry. Access to account data is restricted, and the developer may access content where necessary to investigate a problem you report.
Security checks may use account identifiers, device verification information and IP-based request limits. These uses are separate from advertising, which the app does not contain. See section 8 for retention and deletion limitations.
No storage or transmission method is completely secure. Protect your device with a passcode, keep it up to date and keep your Apple or Google account secure. We handle personal-data breaches and notify affected people or regulators when applicable law requires it.
15. Purchases and subscriptions
Micnoteai offers a premium subscription through Apple's In-App Purchase system.
- Apple handles the payment. Your purchase is made with your App Store account. Card numbers, billing addresses and payment processing are entirely Apple's — the developer never receives, sees or stores your payment details.
- What reaches us. Subscription state — whether your premium entitlement is active, which product it is, and whether a purchase should be restored — reaches the app through RevenueCat, which verifies the App Store receipt. RevenueCat links this to a purchase identifier associated with your account, not to your recordings or notes.
- Free-tier limits. Our backend keeps counters of your usage against the free-tier limits so it knows what to allow. Some account-level counters and the device-level count remain after account deletion for abuse prevention, as explained in section 8.
- Managing and cancelling. Subscriptions renew automatically until cancelled. Manage or cancel yours in iOS Settings → your name → Subscriptions. We cannot cancel a subscription or issue a refund on your behalf — only Apple can, through reportaproblem.apple.com.
- Restoring purchases. "Restore purchases" asks Apple and RevenueCat to re-check your existing entitlement; no new personal data is collected.
- Records. Signing out resets the RevenueCat identity stored on the device. Purchase records that Apple and we must keep for tax and accounting purposes survive account deletion, as described in section 8.
16. Analytics and diagnostics
Micnoteai uses PostHog EU Cloud for product analytics and diagnostics. Events include screens opened, feature usage, paywall interactions and technical error information. They include app/device metadata and an analytics identifier that is linked to your account when you sign in. These are pseudonymous records, not anonymous data.
We do not intentionally include recording audio, transcripts, summaries, note titles, chat content or imported files in analytics events. Session replay is disabled. The app does not contain advertising or cross-app advertising tracking.
How to object. Email support@micnoteai.com with an analytics objection, using the email associated with your account where possible. There is currently no analytics switch in Settings. We can disable collection for your account through a remote setting; the app must connect and receive that setting for it to take effect. An objection preference is retained locally so sign-out does not silently undo it.
We rely on legitimate interests in maintaining and improving the app for this processing, subject to applicable law and your right to object. An objection stops future collection once applied; it does not automatically delete earlier events. You may also request access or deletion under section 10. Resetting the app’s analytics identifier on account deletion is not the same as deleting stored events.
17. Changes to this policy
We may update this policy when the app changes, when we add or replace a service provider, or when the law requires it. The "Last updated" date at the top always reflects the current version.
If we make a material change — for example collecting a new category of data, using your content for a genuinely new purpose, or adding a recipient that meaningfully changes where your data goes — we will give you notice inside the app before the change takes effect, and where the law requires it, we will ask for your consent. Continuing to use the app after a non-material update means the updated policy applies to you.
We will not retroactively reduce the protections that applied to data we already hold without telling you first.
18. Contact us
Privacy, data requests and app support: support@micnoteai.com
Data controller: Hamid Manafov, individual developer, Azerbaijan. A postal contact address is available on request.
You can write in English or Azerbaijani. We aim to reply within a few business days and handle formal privacy requests within the applicable statutory deadlines described above. Please describe your request without attaching private recordings or documents unless they are needed and we have agreed a suitable way to receive them.