Privacy policy
KeyLayers needs the internet once, to make your account; after that it plays without it. What it does send is listed here, in full.
Last updated 20 October 2026.
Who we are
KeyLayers is made by Northpocket Software Inc. (“North Pocket”, “we”, “us”). This policy covers the KeyLayers app on iPhone, iPad, Mac, Android and Windows, and the website keylayersapp.com.
The short version
- KeyLayers needs an account, made once, the first time you open it, with the internet. After that, nothing in KeyLayers needs the internet while you play.
- With your account, we keep your email address and a copy of your songs and sets, so they come back on your other devices, and the keys that unlock our sounds for you.
- Unless you turn it off, the app sends counts of which features are used, and a report when it crashes. Never your songs’ names or what you play.
- We do not sell your data, show ads, or track you across other apps or websites.
- You can delete your account, and everything it has saved, inside the app.
Your account
You need an account to use KeyLayers. You make it the first time you open the app, with Apple, with Google, or with your email address, and it stays signed in on that device until you sign out.
What we keep: your email address, the way you signed in, and when. If you sign in with Apple or Google, they send us a sign-in token; we never see your Apple or Google password. Apple lets you hide your real address; if you do, we only ever see the address Apple gives us. With Google, the sign-in can also pass along the name and picture on your Google profile; we do not use them.
Why: to sign you in, to unlock our sounds for you, to back up your songs and sets, and to send you the sign-in link when you ask for one.
Signing in with an emailed link: when you ask for a link, the app opens a sign-in request that holds your device’s own name where it has one (such as “Ana’s iPhone”), its platform (iPhone, Android, Mac or Windows), and a scrambled form of your email address (a hash), never the address itself, and a keyed scrambled form of the internet (IP) address the request came from, used only to limit how many requests one address can make in an hour, never the address itself. The page the link opens shows the kind of device and how long ago it asked, with the name the device gives itself, so you can check it is yours before you confirm. We do not keep or show where the request came from. The request is deleted after a day.
Your sign-ins: Supabase Auth, which runs our accounts, keeps each sign-in with the internet (IP) address it came from and the kind of device and app that made it (its user agent), for as long as that sign-in lasts. An account stays signed in on at most 3 devices; when a fourth signs in, the one used least recently is signed out. The app also sends a random number for the device (never its name), so a device that signs in again counts once. That number goes with your sign-ins. A sign-in ends when you sign out, when it is signed out by a fourth device, when you set a new password on another device, or when you delete your account.
We send email only to sign you in. No newsletters from the app.
Your songs and sets
While you are signed in, KeyLayers keeps a copy of your songs and sets with your account: each song’s name, its layers and sounds, its mix and scenes, and the order of your sets. That is how they reach your other devices and survive a lost phone.
Settings that belong to one device stay on it: audio outputs, controls you have mapped, appearance, and the keyboards it has seen.
Only you can read your copy. It is deleted with your account. Signed out, nothing is sent.
Usage counts
Unless you turn it off, KeyLayers sends us counts of how it is used, so we can find what is broken or slow. It is on when you install the app. Turn it off any time in Settings → Privacy → Share usage and crash reports; anything not yet sent is thrown away when you do.
What is sent:
- How many times each feature was used each day, how many different songs were played, and for how long. Never a song’s name, its notes, or anything you type.
- How long each session lasted and which screens were opened.
- Which keyboard model is plugged in. For a keyboard KeyLayers does not know yet, the name it reports over USB, with any personal name removed.
- Problems: the message the app showed, the last few steps before it, and how much memory was in use.
- How quickly the app opened, slow screen updates, and audio dropouts.
- About the device: its model, system version and chip, the app version, your language and region setting, time zone, screen size, and display settings such as dark mode or larger text.
- A random number for this installation, so one device’s counts can be told apart. It is not your name, your device’s name, or an advertising id.
We do not collect your location, contacts, microphone, or your device’s serial number. Usage counts never carry your device’s name; only a sign-in request holds it, for a day (see Your account).
To stop one account flooding us, we also count how many sessions and problems each account sends each hour.
Usage counts are linked to your account. When you sign in on a device, the counts that device has sent are linked to your account, and so is everything it sends while you are signed in. A device stays linked to the first account signed in on it. With the switch off, nothing more is sent, but what was already sent stays linked until it is deleted. Counts are sent about once every six hours while the app is open; daily counts go only once the day is over.
Crash reports
When KeyLayers crashes, or meets an error it did not expect, it sends a crash report so we can find and fix the cause. Crash reports go with usage counts: they are sent only while Share usage and crash reports is on in Settings → Privacy. Records the system keeps about KeyLayers (crashes, freezes, how it last closed) and freezes of 5 seconds or more are sent with the usage counts to our own server, only while Share usage and crash reports is on, tagged with that run’s session. Turned off, nothing more is sent and any report still waiting on the device is deleted without being sent.
What a report holds:
- The kind of error and its first line, with your home folder taken out of any file path, and where in the app’s code it happened (the code’s own names, never your songs or anything you typed).
- The app’s version and build, and the time of the crash.
- About the device: its model, system version, chip, free memory and storage at the time, and whether the system was modified.
- The same random number for this installation that usage counts carry, so a crash can be matched to a problem it showed, and a random number the crash reporter makes for itself. Neither is your name, your email address, your device’s name or an advertising id.
A crash report never holds your email address, your name, your device’s name, your songs, sounds or notes, or your location. KeyLayers uses no advertising id and no analytics from the crash reporter.
Who processes them: Google, through Firebase Crashlytics, on our instructions. Google keeps crash reports for 90 days, then deletes them. They are not linked to your account by Google; the random installation number is what we use to match a report to the usage counts and problems that device sent.
Notes about new sounds
KeyLayers can send you a note when we release new sounds. It asks first, once, after your first sound download, and only Notify me brings up your device’s own question. Turn notes on or off any time in Settings → Notifications.
While notes are on, your device gets a push token from Apple or Google, which Google Firebase Cloud Messaging uses to deliver the note, with Apple Push Notification service on Apple devices. Your device also joins a time-zone group (its offset from UTC, such as UTC+1), so the note arrives at 10:00 your time. We don’t keep the token or the group, and neither is tied to your account. A note says only which sounds are new. Turned off, the device leaves the group.
Unlocking our sounds
KeyLayers’ own recorded sounds are stored locked inside the app, each with its own key. When you sign in, and from time to time when you open the app signed in, it asks us for the keys your account may use and keeps them in the device’s secure storage (the Keychain on Apple devices). When you sign out or delete your account, they are removed from the device.
Each time keys are asked for we record the time, your account, how many keys were sent and the internet (IP) address the request came from, to stop abuse. When a fourth device signs in and another is signed out, we record that the same way: the time, your account, how many sign-ins were removed and the internet address of the device that signed in. We never record the keys themselves. This happens whether or not usage counts are on, because the sounds cannot play without it.
Song requests
When you ask for a song in Settings → Songs, we receive what you wrote: the song’s title, the artist, the link to where it can be heard, the sounds you want, your notes, and the time. You send it signed in, and it is kept in our database with your account’s id (a random number, never your email address), so only players can send requests; it is not linked to your device. We use it to decide which songs to set up next. To limit how many one account can send, we also record when each request was sent and whether it was accepted, never what it said. Delete account… deletes your song requests with your account.
If we have a question about a request, it shows under Your requests, and you can answer it. Only we can start that conversation and only you and we can read it. We keep your answers with the request, and they are deleted with it and with your account.
Reports you send
If you tap Send report (Settings → Help, Settings → Health, the + in Chat with us, or the safe-start card), we receive what the screen showed you before you sent it: the report code, the app’s version, build and the code it was built from, a line about your device (its system, the system’s version and its chip, never its name), this launch’s session tag, a list of facts about the app at that moment, the last part of the app’s own log, and a note if you write one. The facts are what help us find a fault: the device’s model, memory, storage space, heat, battery and power saving, and how much space the app’s own data takes; the audio output’s kind, maker and settings, and changes to it (a new output, an interruption, a dropout); the keyboard model, its identity reply, and the kinds of the last MIDI messages it and the app exchanged (channel and note or control numbers, never a recording of what you played); which of our songs and sounds were playing, with their settings (a song of your own is only said to be yours, never named); errors the app met, with where in the app they happened; the screens you visited and the app’s own actions in the last few minutes; calls the app made to our servers (address, result and time) and the difference between your clock and ours; your app settings, accessibility settings such as text size, and whether the app’s permissions are on; how the last session ended, which versions were installed, and the system’s own crash, freeze and exit records for this app; where the app was installed from and when it was installed and updated; and whether you have a subscription. With it, the app sends its own earlier log from this device, up to about 2 MB, cleaned the same way. You send it signed in, and it is kept in our database with your account’s id (a random number, never your email address). Email addresses, sign-in tokens, keys, your home folder in file paths and the names of your devices and keyboards are taken out of the log on your device before it is written, and email addresses again when it arrives. Nothing is sent unless you tap Send report or write to us in Chat with us; if it cannot be sent, Email the report opens your own mail app with the same details. If you add a screenshot, it is a picture of KeyLayers’ own screen as it was when you opened Send report, shown to you before it goes, and kept 90 days with the report. A report is kept for 90 days, then deleted automatically, and Delete account… deletes it sooner. As with song requests, we record when each report was sent, never what it said.
Support chat
If you write to us in Chat with us (Settings → Help & Support), you chat signed in, and we keep your messages and our replies, and any pictures or videos you attach. When the chat opens, the app also sends what helps us answer: the app’s version, a line about your device (its system and version, never its name), the keyboard you have connected, your language and your time zone. When you send the first message of a conversation (a new one, or one where no report has gone for 6 hours), a full report goes with it, the same as Send report, so we can see what happened without asking. See what’s sent shows it first; it is cleaned as reports are.
Before a picture leaves your device, the app draws it again without its location and camera details, and when a picture or video arrives we take out anything else saved inside it (location, the device’s make and model, when it was filmed). Files are kept in our own private storage and open only inside the chat, by a link that lasts five minutes. Only you and we can read your chat.
When we reply, your device gets a notification that says only “Support replied”, never the message.
Chats are not deleted, so we can help you again with what was said before. Delete account… keeps the chat but takes away your email address, your device details, and any email address written in it, so it no longer says who you are.
Reviews you leave
If you tap Leave a review in Settings, we receive the stars you chose, your comment if you write one, the time, the app’s version and the kind of device (iPhone, Android, Mac or Windows). It is kept in our database with your account’s id (a random number, never your email address), to learn what to improve, until you delete your account. We record when each review was sent, as we do for reports.
This website and the waitlist
keylayersapp.com sets no cookies and runs no advertising scripts.
To know how many people visit, the site uses Cloudflare Web Analytics, which sets no cookies and keeps nothing that identifies you: it counts page views, which pages, the referring site, the country, the kind of browser and device, and how quickly the page loaded.
If you join the waitlist, the form sends your email address straight to our database, which keeps it with when you joined, your place on the list and when you first signed in to KeyLayers with that address (that is what makes a place among the first 500 yours), to tell you when KeyLayers launches and to honour the locked-in price.
To stop a flood of sign-ups, the database counts how many arrive from one internet address in an hour. It keeps only a scrambled form of the address (a hash), never with your email, and deletes the count after a day.
Where it is kept
- Supabase, which runs on Amazon Web Services, holds your account, your songs and sets, the keys to our sounds, usage counts, song requests, reports and the waitlist.
- Supabase also holds the support chat’s messages, and Cloudflare (R2, private storage with no public address) holds the pictures and videos you attach to it.
- Google (Firebase Crashlytics) holds crash reports.
- Google (Firebase Cloud Messaging) delivers notes about new sounds, while they are on, and holds your device’s push token and its time-zone group to do it; on Apple devices, with Apple Push Notification service.
- Cloudflare serves this website’s pages and counts its visitors.
- Apple and Google handle the sign-in when you choose them, under their own privacy policies.
- Cloudflare also sends the sign-in, confirm and password emails, from signin@mail.keylayersapp.com; it is given your email address and the message, nothing else.
These providers may store data outside your country. They act on our instructions and may not use it for their own purposes. Everything travels encrypted.
How long we keep it
- Your account, songs and sets: until you delete your account.
- Your sign-ins: while you stay signed in, on at most 3 devices.
- Sign-in requests: 1 day, then deleted automatically.
- Usage counts, including the keyboards seen: 400 days, then deleted automatically. On your device, daily counts are kept for 90 days.
- Hourly counts of what each account sends: 2 days.
- Crash reports: 90 days, then deleted by Google, which keeps them for us.
- Records of key requests, and of sign-ins removed by the 3-device limit, with their internet address: 180 days.
- Reports you send: 90 days, then deleted automatically.
- Reviews you leave: until you delete your account.
- Support chat, and what you attach to it: chats are not deleted; Delete account takes away what says who you are.
- When reports, reviews and song requests were sent: 180 days, to limit how many one account can send.
- Song requests: until you delete your account, or until we no longer need them.
- A record that an account was deleted: when it was deleted and a scrambled form of the account's random id, never your email address: 180 days, to show the deletion was done.
- The waitlist: until we no longer need it. The count of sign-ups from one internet address: 1 day.
Deleting your data
- There is one way to delete: Delete account… in Settings → Account, or email us at hello@northpocketsoftware.com. It removes your KeyLayers account, your saved songs and sets, your song requests and your answers about them, the reports you sent, your reviews, your KeyLayers sign-ins, the hourly counts of what your account sends, the record of when you sent reports, reviews and song requests, and the usage counts of every device linked to your account and of this device, which then gets a new random number. It takes the keys to KeyLayers’ sounds off this device. Your songs and sets stay on your device.
- Your email address and sign-in are deleted with it, unless you use another of our apps with the same email address: deleting your KeyLayers account does not affect that app, which keeps them until you delete your account there too.
- Records of key requests and of removed sign-ins are kept for their 180 days, and sign-in requests for their 1 day, then deleted automatically. We also keep a short record that your account was deleted, and when, for 180 days; it holds no email address and nothing you saved.
- Your support chat is kept without your email address, your device details or any email address written in it.
- Backups of our database are kept for up to 12 weeks, then deleted.
- To stop sending usage counts and crash reports without deleting anything, turn off Share usage and crash reports in Settings → Privacy.
- To stop notes about new sounds, turn off New sounds in Settings → Notifications; the device leaves its time-zone group.
- Crash reports already sent are not deleted with your account; Google deletes them after 90 days. Email us with the report code if you want one deleted sooner.
- Deleting the app removes everything it kept on your device.
- For anything else, such as the waitlist, email us and we will delete it.
Your rights
Wherever you live, you can ask us for a copy of what we hold about you, to correct it, or to delete it. Email us from the address on your account and we will answer within 30 days. If you are not happy with our answer, you can complain to the data protection authority where you live.
Children
KeyLayers is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child under 13 has given us data, email us and we will delete it.
Changes to this policy
When this policy changes, we update the date at the top. If a change affects what we collect or how we use it, we will say so in the app before it takes effect.
Contact
Questions or requests: hello@northpocketsoftware.com.