1Who is responsible
Ternclave is an Android music-practice app provided by Zydeno. Contact [email protected] for privacy questions. We do not operate an app backend.
Developer identity. Zydeno is the developer name under which Ternclave is published on Google Play, as shown on the app’s store listing. For the purposes of data-protection law, the developer is responsible (the “controller”) for the limited personal data described in this policy that actually reaches us, such as e-mails you send us. Data that stays on your device is under your control.
2What this policy covers
This policy covers the current Android app, its on-device analysis, microphone listening, local library and manual file transfers. The website, your chosen document provider, Android, Google Play and any external browser operate under their own policies.
3What the developer does not receive
The app has no ads and no analytics. There are no accounts, advertising identifiers, remote crash reporters, tracking SDKs or music uploads. The developer does not receive your audio, microphone samples, charts, filenames, device identifiers or use history through the app. Audio is not used to train a remote model, recognise speakers or create voiceprints.
4Your local audio and rehearsal library
The app stores private copies of audio you import, kept microphone takes, file metadata and hashes, waveform/analysis results, algorithm versions, manual chord and grid corrections, arrangements, transpose/capo choices, loops, sections, sets, cues and preferences on your device. Room stores library state; app-private files hold audio and recovery data. Temporary exports and pre-restore recovery snapshots may also remain locally.
Microphone listening is not memory-only: while you listen, the app writes a temporary WAV and recovery journal in private storage. An interrupted or unkept take can survive closing or restarting the app so that you can choose to keep or discard it. It is not added to the song library until you choose Keep take. Do not record sensitive conversations or other people without permission.
5No app internet access
The Android app declares no INTERNET permission and does not contact Zydeno, music services, recognition servers or other APIs. DSP and file playback run locally; no model or audio upload is required. Opening this policy or the Terms launches an external browser. That browser makes its own request, including normal connection information such as an IP address, under the website and browser policies.
6Microphone access and listening
RECORD_AUDIO is requested when you start Listen. It is used for on-device tempo/key estimates and the recoverable temporary take described above. Live listening does not generate live chord symbols. You can keep a stopped take for subsequent offline chord analysis or discard it. The microphone stops when Listen is left, the app pauses/backgrounds, audio focus is lost or input disconnects. Capture is foreground-only: there is no microphone foreground service, background recording mode, notification permission or phone-call recording feature.
Declining microphone permission leaves file import and tap tempo available. Revoke access in Android Settings at any time. The app shows listening state; Android also supplies its microphone indicator where supported. Live capture is limited to five minutes per take.
7Other permissions and device information
No contacts, camera, location, broad storage, media-library, advertising-ID or Bluetooth scanning permission is requested. The merged manifest also contains a package-specific signature permission used by AndroidX for internal receiver protection; it does not access personal data. Android supplies connected audio-route names/IDs locally for input selection and latency settings. Locale/region settings, and country codes where available without a telephony permission, help choose display conventions; no phone number, subscriber identifier or precise location is read.
8Import, export and external providers
Audio import uses Android's document picker or a file you explicitly open/share into the app. The app copies readable audio into its private library. Decoder support depends on the device; unsupported or protected media may not open. No automatic scan of all your files is performed.
You can export TXT/CSV charts and a manual backup containing library state, preferences and every owned audio file including kept takes. An unkept temporary take is not part of the song library backup: keep it first if you want to include it. Restore replaces the current library after confirmation, retaining a local pre-restore snapshot for recovery. Backups are ordinary ZIP files without app-provided encryption; protect them as you would the recordings.
Saving through the picker can send the chosen file to a cloud document provider you select. This is your explicit transfer, handled by that provider, not an automatic app upload to Zydeno. Exported files may contain audio, song titles, notes and cues. We cannot recall, delete or control copies you save or give to others.
9Libraries and original example audio
Bundled AndroidX/Jetpack components (including Media3 and Room), Kotlin/kotlinx, Guava and Okio provide local app functions. They are not advertising or analytics integrations. Lunasima and GFS Neohellenic fonts are bundled under SIL Open Font License 1.1. Open-source notices are available in About → Open-source licences. The three bundled example tracks are original deterministic synthesis authored for Ternclave, not excerpts of commercial recordings or a licensed song catalogue.
10Your controls and deletion
Use the library to inspect or correct work; export charts or a backup from Your data. Discard an unkept microphone take explicitly when you do not want it retained. Delete a song or use Delete all data after exporting what you need. Android's Clear storage or uninstall removes the app's private data, subject to Android's operation. Separately delete exported files and backups with your document provider. Revoking microphone permission stops future access but does not delete an existing take.
Automatic Android cloud backup and device-transfer backup are excluded. Device loss, clearing storage or uninstalling can therefore destroy work that you have not exported. We cannot recover your local files from a server.
11Legal bases for processing
Where the EU or UK GDPR, or a similar law such as the Swiss FADP or Brazil’s LGPD, applies, these are the legal bases for the limited processing described in this policy:
| Processing | Where it happens | Legal basis |
|---|---|---|
| Storing your entries and settings in the app’s private storage | Your device only; we never receive it | Necessary to provide the app you choose to use (Art. 6(1)(b) GDPR). Storage on your device is strictly necessary for that service, so no separate consent is needed under the ePrivacy rules. |
| E-mails you send to [email protected] | The developer and its e-mail provider | Our legitimate interest in answering you and improving the app (Art. 6(1)(f) GDPR) or steps you ask us to take (Art. 6(1)(b)); keeping records where the law requires it (Art. 6(1)(c)). |
The app makes no automated decisions that have legal or similarly significant effects on you, does not build a profile of you and does not infer sensitive traits, identify speakers or create voiceprints; audio you choose may contain sensitive information and remains local unless you export it.
12How long data remains
Library work remains locally until you delete it or clear app storage. A stopped unkept take and its recovery journal remain pending your decision; kept takes become library audio. Temporary exports, old file generations and pre-restore recovery copies can remain until their relevant cleanup or app-data deletion. Copies outside the app remain wherever you saved them.
Support e-mails. We keep e-mails you send us, and our replies, only as long as needed to handle your request and any follow-up, normally no longer than 24 months after the last message, unless the law requires us to keep them longer or we need them to establish, exercise or defend legal claims. You can ask us to delete them earlier.
13Security and your responsibilities
App-private storage and Android's access controls protect local files. The app does not add password encryption to audio or backup archives. Secure your device, check export destinations and do not import untrusted backup archives. No storage system can guarantee against loss or unauthorised access. Do not include private recordings or backups in support mail unless necessary and lawful.
14Ads, purchases and future versions
Today. The current version of Ternclave is free of charge, shows no ads, has no in-app purchases or subscriptions, and contains no advertising, analytics or payment SDKs. This describes the app as it is now, not a promise about future versions. Future versions may introduce advertising, paid features, in-app purchases or subscriptions, or other optional services.
If ads are introduced. Ads would be supplied by a third-party ad network, for example Google AdMob. Ad networks typically process your device’s advertising ID, IP address, approximate location derived from the IP address, device and app information and your interactions with ads, in order to show ads, limit repetition, measure performance and prevent fraud, and, only where you allow it, to personalise ads. Ads would also require the app to connect to the internet, which the current version cannot do.
If purchases or subscriptions are introduced. They would be processed by Google Play’s billing system. Google handles your payment details under the Google Privacy Policy. We would receive only what is needed to deliver and verify a purchase, such as a purchase token, the product, its status, the country and the currency, never your full card or bank details.
Before any such change we will update this policy with a new effective date and version, describing what data is processed, by whom, why and how you can control it; update the Google Play Data safety section; mention the change in the release notes; ask for your consent where the law requires it (for example for personalised ads and non-essential access to your device in the EEA, the UK and Switzerland, through a consent tool that meets Google’s requirements); and offer the opt-outs the law requires (for example under US state privacy laws). The change applies only from the app version that introduces it. Data already stored in the app will not be used for advertising without telling you first and, where required, getting your consent. We will not knowingly show personalised ads to children (§15).
15Children
Ternclave is designed for adult music practice, not directed at children under 13, and does not knowingly collect their information. A parent or guardian can contact us about information sent to support. Local audio is not visible to the developer.
Age limits. In the EEA and the UK we also treat as a child anyone under the age at which a child may consent to online services in their country (between 13 and 16). If you are a parent or guardian and believe that your child has sent us personal data, for example by e-mail, write to [email protected] and we will delete it. If a future version includes advertising, it will be set up in line with applicable children’s privacy rules, such as COPPA in the United States, and Google Play’s policies.
16Your privacy rights
Privacy laws in many countries give you rights over your personal data. Because Ternclave keeps your data on your phone and the developer does not receive it, most of these rights are in your own hands: you can view, correct, export and delete everything in the app (§10) and withdraw permissions in Android Settings. For data you have sent us, such as e-mails, write to [email protected].
EU and UK representative. The individual developer does not process personal data of people in the EU/EEA or the UK except occasional e-mails you choose to send to support. This occasional processing does not involve large-scale processing of special-category or criminal-offence data and is unlikely to result in a risk to your rights and freedoms. Under Article 27(2)(a) GDPR and Article 27(2)(a) UK GDPR, it does not require an EU or UK representative, so none is appointed. Contact us directly at [email protected]; you can also complain to your local supervisory authority.
Rights by region. A summary; the law where you live decides the details.
- European Union, EEA, United Kingdom and Switzerland (GDPR, UK GDPR, Swiss FADP): access, rectification, erasure, restriction of processing, data portability, objection to processing based on legitimate interests, withdrawal of consent at any time, and complaint to a supervisory authority, for example in the country where you live or work (in the UK, the Information Commissioner’s Office).
- United States (California CCPA as amended by the CPRA, and the comprehensive privacy laws of other states such as Virginia, Colorado, Connecticut, Texas and Oregon): to know and access, delete, correct and port personal information; to opt out of its sale or sharing, of targeted advertising and of profiling; to limit the use of sensitive personal information; to appeal a refusal; to use an authorised agent; and not to be discriminated against for using these rights. Notice for California residents: in the last 12 months the developer has not collected personal information through the app, other than e-mails you chose to send us. We have not sold or shared personal information, and we do not use sensitive personal information. Global Privacy Control signals are honoured where the law requires; today there is nothing to opt out of.
- Canada (PIPEDA and provincial laws, including Québec’s Law 25): access, correction and withdrawal of consent; complaints to the Office of the Privacy Commissioner of Canada or, in Québec, the Commission d’accès à l’information.
- Brazil (LGPD): confirmation of processing, access, correction, anonymisation, blocking or deletion, portability, information about sharing and revocation of consent; complaints to the ANPD.
- Japan (APPI): disclosure, correction, suspension of use or deletion; complaints to the Personal Information Protection Commission.
- South Korea (PIPA): access, correction, deletion, suspension of processing and withdrawal of consent; complaints to the Personal Information Protection Commission or the KISA privacy centre. The person responsible for personal information is the developer, reachable at [email protected].
- Australia and New Zealand (Privacy Act 1988, Privacy Act 2020): access and correction; complaints to the OAIC or the New Zealand Privacy Commissioner.
- Other countries (for example India’s DPDP Act, Singapore’s PDPA, South Africa’s POPIA or Türkiye’s KVKK): the rights your local law gives you. Write to us and we will respond in line with it.
How we respond. We answer within one month, or sooner or later where your local law sets another period (for example 45 days under the CCPA), and we may extend it where the law allows. We may ask for information to confirm that a request comes from you. Requests are free unless they are manifestly unfounded or excessive. If we cannot do what you ask, we explain why and how you can appeal or complain.
17International users
Ternclave is available in many countries. The developer does not receive the data you keep in the app, so we do not transfer it anywhere.
If you e-mail us, your message is processed by our e-mail provider and may be stored on servers outside your country. Where the GDPR or UK GDPR applies to such a transfer, it relies on an adequacy decision, on standard contractual clauses offered by the provider, or on the transfer being necessary to answer your request.
This policy is written in English. If a translation is offered, the English version prevails unless your local law requires otherwise.
18Changes to this policy
We may update this policy when we change the app (including any change described in §14), when the services the app uses change, or when the law changes. The effective date and version at the top of this page show which version applies, and the version history (§19) summarises every change.
For a material change, for example new data leaving your device, ads or purchases, we update this page and the Google Play Data safety section before the app version with that change is published, describe it in the release notes, and ask for your consent in the app where the law requires it. Changes do not apply retroactively to data processed before them. Earlier versions are available on request from [email protected].
19Version history
| Version | Effective | Changes |
|---|---|---|
| 1.0 | 2026-10-21 | Initial Android policy prepared for release: offline analysis, foreground microphone permission, recoverable temporary takes, local library and manual file transfer; support e-mail and regional rights. |
20Contact
- Developer (controller): Zydeno, the developer of Ternclave on Google Play
- E-mail for privacy questions and requests: [email protected]
- Website: zydeno.com
We aim to answer within 30 days. If you are not satisfied with our answer, you can contact your local data-protection authority.
See also the Terms of Use.