Privacy Policy

Last updated: 12 November 2026

KeepSay turns what your band records, what you record with your phone when you choose to, and audio files you bring in, into notes you can read, search and share, and shows what your band measures about your day. This policy says what that takes: what stays on your phone, what leaves it, why, how it is protected, how long it is kept, and what you can do about it. KeepSay can be used anywhere in the world, and this policy applies to everyone who uses it, wherever they live.

Who we are

KeepSay is provided by Muhammad Tufail Khan, a sole trader in England and Wales ("we", "us"). We are the controller of the personal data described here. You can reach us at m.tufailkhan007@gmail.com.

The short version

• Your band's health readings never leave your phone in a form anyone but you can read, unless you send a page of them yourself, or choose to have them written into your phone's own health app. KeepSay sends them to no server and no AI model: if you turn on encrypted backup, what leaves your phone is sealed on it first, under a key only you hold.
• A recording leaves your phone only when you send it for notes, move it straight to a new phone of your own, or turn on audio backup, which seals each recording's audio on your phone first so that only you can open it. Audio sent for notes is deleted from our servers as soon as your notes are written, and after 24 hours at the latest.
• Recordings on a private shelf are kept encrypted, on your phone and in your account's copy. They open only behind your phone's own unlock, and are never sent for notes unless you choose that recording.
• KeepSay uses your phone's microphone only while you are recording with your phone: from your tap to start until your tap to stop. Nothing listens at any other time, your phone asks you before the first time, and it shows that it is recording for as long as it does. What you record with your phone is a recording like any other, and everything here about recordings applies to it.
• An audio file you bring in is made into a recording on your phone. KeepSay keeps a copy made for speech and leaves the file itself where it is. It reads only the file you hand it, and asks for no access to your other files. A recording brought in is never sent by itself, whatever you have chosen for your other recordings: it waits until you send it. From then on it is a recording like any other, and everything here about recordings applies to it. Where you have chosen for recordings or their audio to be deleted after a number of days, one you brought in counts its days from when you brought it in, whatever date the file carries.
• Everything that travels between the app and our services is encrypted in transit.
• We do not sell your data, show you advertising, or use your recordings to train AI models.

What stays on your phone

• Health readings from your band: heart rate, sleep, steps, distance, calories, blood oxygen, stress, heart rate variability and blood pressure estimates, and your answers to the morning and evening check-in. They are kept on your phone, and never sent to an AI model or to our notes service. If you turn on encrypted backup (Settings, then Privacy, then Encrypted backup), each day of readings is also kept in your account's backup, sealed on your phone under a key made from your passphrase or your recovery words, which only you hold: we store it but cannot open it, and nobody can without them. You can delete the backup there at any time, and deleting your account deletes it too. Readings about your body are health data, a special category of personal data under the UK GDPR, and KeepSay keeps them on your phone with the explicit consent you give when you set it up, and you can withdraw that consent at any time in Settings, then Privacy, then Health readings: KeepSay then reads nothing more from your band and asks no daily questions, and you choose whether the readings already on your phone stay or are deleted. On your phone they are stored encrypted, with a key kept in the phone's secure storage.
• Recordings you have not sent. The audio stays on your phone until you send it for notes, back it up or delete it. If you move your recordings to a new phone, their audio goes straight to it and is kept there the same way.
• How long your phones keep audio. Your phones keep a recording's audio for as long as you keep the recording, unless you choose otherwise (Settings, then The audio): then each phone deletes the audio of a recording whose notes are made 30, 90 or 365 days after it was made, and keeps its transcript and notes.
• Private shelves. Recordings on a private shelf are kept encrypted on your phone, their audio included, are shown only after your phone's own unlock (fingerprint, face or passcode), and are never searched when you ask your recordings a question.
• Reminders, home-screen widget figures and your app colour. A reminder also goes into your phone's calendar only if you choose that, as below.
• Papers you attach. A PDF, or a photo of a page, that you attach to a recording or to a shelf, or a photo, PDF or piece of text that you share to KeepSay from another app and put on a shelf, is kept on your phone alone, encrypted where the recording is on a private shelf or the shelf is private, and goes when you remove it or delete the recording or the shelf. A PDF's words are read on your phone, and nothing of a paper leaves it except, on Plus and Pro, the text of its pages, as below.
• Your own API keys, if you use the Own-API option. They are kept in your phone's secure storage (the Android Keystore or the iOS Keychain) and used only to reach the providers you chose.

KeepSay leaves its data out of your phone's automatic backups, on Android and on iPhone, so none of this is copied to a cloud backup. What it keeps in your phone's secure storage, such as its keys and your own API keys, stays tied to this phone: a backup cannot bring it to another one.

What leaves your phone, and why

Your account. To sign you in, a sign-in provider holds your email address, your name if your sign-in provider gives one, and how you signed in.

Your library's copy in your account. When you are signed in, the titles, types and shelves of your recordings, the names you give the voices in them, their transcripts, notes, posters, flashcards and quizzes, your shelves and your settings are copied to your account in our cloud database, so you can use KeepSay on a new phone. Health readings are never part of this copy; the encrypted backup, if you turn it on, is kept apart from it, and only you can open it.

Moving recordings to a new phone. Unless you turn on audio backup (below), a recording's audio is never kept in your account, so a new phone gets your notes back but not the audio. To bring the audio too (Settings, then Your copy in the cloud, then Move recordings to a new phone), both phones must be signed in to your account and on the same Wi-Fi. While the new phone waits, it leaves its address on that network in your account, for fifteen minutes at most, and the audio then goes straight from your old phone to the new one, encrypted with a key made from a one-time code that only the two phones know. It never passes through our services.

Recordings you send for notes. When you send a recording, its audio is uploaded to our notes service, which transcribes it and writes the notes with the help of an AI provider acting on our behalf. The finished transcript and notes are written to your account's copy. The audio is deleted from our service as soon as your notes are ready, and a sweep removes any audio left behind after 24 hours. On Plus and Pro, the text of the pages you attach to a recording, or to a shelf it is on, goes with it for that job alone and is deleted with the job; never the pages of a recording or shelf that is, or was, private. A poster, flashcards or a quiz is made the same way, by the same service and AI provider, from the transcript and notes already in your account's copy — never from the audio — and written back to it.

Backing up your recordings' audio. On Plus and Pro you can turn on audio backup (Settings, then Audio backup). It is off until you turn it on, and it needs your encrypted backup: each recording's audio is encrypted on your phone with your encrypted backup's key before it is uploaded, so we store it but cannot open it. Only your own phones can, and KeepSay on the web once you open your encrypted backup there. Recordings on a private shelf are backed up too, encrypted the same way, and are never shown or played on the web. Your plan keeps each recording's audio for a set time after it is backed up: 90 days on Plus, a year on Pro. If your plan changes to one that keeps less, we tell you in the app and keep what your old plan kept for 30 more days, so that you can bring it back to your phone first. On Pro you can also save a copy of a recording's audio outside KeepSay, from the note's Share button.

Who said what, and who was named. Where a recording's transcript tells its voices apart, you can name each voice for that recording. The names are kept with the recording and are used when its notes are made again or when you ask it a question. The notes also list the people and places a recording names, taken only from what was said in it, so that your library can show every recording a name came up in.

Asking your recordings. When you ask a question, your phone chooses the few lines from your recordings that match it. Your question and those lines are sent to our notes service and answered with the help of the same AI provider, and on Plus and Pro, the pages you attached that best match your question, never a private one's. They are deleted as soon as the answer is ready, and the answer itself is deleted within ten minutes. Recordings on private shelves are never searched.

AI tools you connect. On Plus and Pro you can let an AI tool you use, such as an assistant on your computer, read your recordings. The tool asks for leave from its own settings, and you answer on KeepSay on the web, where you tick the shelves it may read: nothing is given with none ticked. It then reads, through our notes service, only the recordings on those shelves that you would share without being asked: never a private shelf, your diary, a recording about someone's safety or your health readings, and never audio. It is given lines as they were said, with who said them and when and a link to each moment, and a recording's notes when it asks for that recording. It can never change anything. Every read is listed in the app under What left this phone, and you can take a tool's leave away in Settings, then Privacy, then AI tools you connected, which stops it at its next read. Once a tool has read something, what it does with it is up to that tool's own terms and privacy policy, not ours.

Shared shelves, if you choose. You can share a shelf with people you name: a household, a study group, a small team. Whoever makes a shared space, on Plus or Pro, invites people by the email address of their KeepSay account and chooses whether each may put recordings there or only read them. We keep an invitation, with that address, for 14 days or until it is answered, whether or not the address has an account, and the person sees it only in their own KeepSay, signed in with that address. A space holds its name, its shelves' names, any words and template its owner gives a shelf, each member's account and the name they choose to be shown by, which members its owner made administrators, how long it keeps what is put on it, if its owner or an administrator sets that, and a history of the changes made to it, for its owner and administrators to read: who joined, left or was taken out, which shelves were added, renamed or removed, who sent an invitation, by whom and when, and never an invitation's address. A shelf's words go with the recordings members put on it, or file to go there, when they are transcribed and noted, as words of their own do; never with a recording that is or was private. When you put one of your recordings on a shared shelf, a copy of its title, date, length and type, the names given to its voices, its transcript and its notes goes there, for the people in that space to read on their phones and in KeepSay on the web. If you also put its flashcards on the shelf, they go with that copy, for the people in that space to practise with; what each of them learns from them stays on their own phone, and you can take the flashcards off again at any time. Its audio stays on your phone, and nothing else of yours is seen. The copy is encrypted with the space's own key, which our service keeps, as it keeps the key for your private recordings, and gives only to the space's members, so it is not end-to-end encrypted. In KeepSay on the web that key is held in the open tab alone, never in the browser's storage, and goes when the tab is closed or you sign out. Recordings on a private shelf, recordings KeepSay treats as sensitive that you have not filed on a shelf, and recordings about someone's safety are never shared, and health readings never are. A recording that was once private goes on a shared shelf only after you confirm it. You answer for what you share: a recording of other people holds their words too, so tell them first, and KeepSay asks you before it goes. Each copy you share is listed in the app under What left this phone. A to-do on a shared shelf that someone ticks says who ticked it, for the space's members. You can also set a rule that puts what you file on one of your own shelves on a shared shelf too; it is kept with your settings, and you can stop it at any time. When you take a recording off, leave a space or are removed from it by its owner or an administrator, your copies are deleted; when a space keeps what is put on it for a set time, each copy is deleted that long after it was shared; when its owner closes a space, everything in it is deleted. Sharing needs you to agree to the words that say so, and withdrawing that agreement, in Settings, then Privacy, then Shared shelves, takes you out of every space and closes the ones you made.

If you use your own API keys. With the Own-API option you connect KeepSay to AI providers you have chosen, with your own accounts. When you send a recording, its audio goes straight from your phone to your transcription provider, and its transcript goes straight from your phone to your notes provider. When you ask your recordings a question, the question and the few matching lines go straight to your notes provider. On Plus and Pro, the text of the pages you attach goes the same way, with the recording's transcript or with a question it matches, never a private one's. We never receive any of it, and we never receive your keys. Those providers work for you, not for us, under your own agreement with them, so their terms and privacy policies apply to what you send them. The transcript and notes that come back are kept like any others, including the copy in your account. To show you which providers and models you can choose, the app downloads a list of them from us; that request carries nothing about you or your recordings.

Payments. Subscriptions and the Own-API unlock are sold by Google Play or the App Store, and a subscription service tells us what you have bought. We never see your card details.

Your plan and your hours. Your account keeps your plan, any Plus a code has given it, and how much of each month's hours you have used, so that the hours can be counted. What is counted is the length of the recordings you send, never what was said in them.

How long your first note took. If you are new to KeepSay, after you have read your first note the app sends our notes service one number: the whole minutes, rounded up, from when you first opened KeepSay on that phone to when you read it. It carries nothing of what you said. It goes with your sign-in, as everything sent to our notes service does, so that it is counted only once: it may be sent again when a send gets no answer or is turned away, but once it has been counted the app does not send it again. We add it to a count of how many people took each number of minutes, which holds no name and no account, so that we can see how quickly new people reach their first note, and how many do so within ten minutes, and make KeepSay's first steps better where they do not. To count it only once, we keep a note that your account has been counted, and when, with no number in it, apart from the count, until you delete your account. It is sent only after you have agreed, in the app, to the words that say so, and it is listed in the app under What left this phone.

Notifications. To tell you when notes are ready, a notification service holds a token for your phone. Notifications never contain what was said: they say only that something is ready.

Your calendar, if you choose. In Settings, then Reminders, you can have each reminder you set also put in your phone's calendar. KeepSay then writes into the phone's main calendar the to-do's words, its time and the title of the recording it came from. From there your calendar app keeps the entry, and copies it to wherever that calendar syncs, under the terms of whoever provides it. To know where to write, KeepSay reads the list of your calendars; it reads your events only if you turn on Read your calendar, below. Reminders from a recording on a private shelf, or from one KeepSay treats as sensitive, are never put there. Turn it off, or delete everything on this phone, and KeepSay takes out what it put in.

Reading your calendar, if you choose. In Settings, then Privacy, you can turn on Read your calendar, after agreeing to the words that say what it does. KeepSay then reads, on your phone, the title and times of the entries in your phone's calendar (not all-day ones, and not the reminders KeepSay put there itself), for three things: to suggest a recording's title and shelf from the entry it was made during; to remind you, as an entry begins, that a double tap on your band keeps it; and, after a night shorter than your usual, to count today's entries for your morning page. That reminder never names the entry. KeepSay keeps no copy of your entries, and sends nothing of them anywhere: not to our services and not to any AI model. A suggestion becomes a recording's title or shelf only when you tap it, and is then kept as any title or shelf you choose yourself. Turn it off and KeepSay stops reading your calendar and takes those reminders down.

Crash reports. When KeepSay fails, it sends us a crash report so that we can find and fix what went wrong. A report says what kind of error it was and where in KeepSay's own code it happened. It comes with your phone's model and system version, KeepSay's version, your band's firmware version, the phone's state at that moment (such as its free memory and storage), and an identifier for this installation of KeepSay, which is not linked to your account. A crash report never contains what you recorded, what was said, your notes, their titles, your shelves or your health readings. You can turn crash reports off in Settings, then Privacy, and any report not yet sent is then deleted.

Whether this version still works. When KeepSay opens, and when you come back to it, it asks our configuration service whether this version of the app should still run, so that a faulty version can be stopped. The question carries KeepSay's version and an identifier for this installation of KeepSay, and nothing about you or your recordings.

Proof that it is KeepSay. So that our services answer only KeepSay itself, the app asks your phone's own store service (Google Play on Android, Apple on iPhone) to confirm that it is an unmodified copy of KeepSay on a real phone, and sends that confirmation with its requests to us. It is about the app and the phone, not about you, and says nothing about your recordings.

Sharing. When you share a note, a quote, a PDF or your week, it goes only where you choose to send it, and only in the form you pick.

A page for an appointment, if you make one. In Health, then For my appointment, you can make a page of your own health figures for the days you choose, with the questions you want to ask. It is made on your phone, by arithmetic and with no AI model, and you choose what is on it. It leaves your phone only when you send or print it yourself, after KeepSay has told you that it holds health readings, and it goes only where you send it. It is not in your account, in a backup or in anything sent for notes. Your choices and your questions for it are kept on your phone with your readings, encrypted, and are deleted with them.

Your height and weight, if you give them. In Settings, then Health, you can give your height and weight to see your body mass index (BMI), and, if you choose, your sex. KeepSay works it out on your phone, by arithmetic and with no AI model, and shows it against the World Health Organization's ranges for adults; it is a rough guide and not a diagnosis. Your height, weight and sex are kept sealed on your phone beside your band's readings. KeepSay sends them to no server and no AI model. You can remove them on the same page at any time.

Your phone's own health app, if you choose. In Settings, then Health, then Your phone's health app, you can have KeepSay write what your band measured into your phone's own health app: Apple Health on an iPhone, Health Connect on Android. Each kind is turned on by itself (heart rate, resting heart rate, steps, sleep and blood oxygen), and your phone asks you first. KeepSay writes only what the band measured, never its estimates, and changes or removes only what it wrote. Nothing passes through our services. Once there, the readings are under that app's rules: other apps you have allowed can read them, and your phone's maker may back them up if you have that turned on. Turning a kind off asks whether what KeepSay wrote stays there or is taken out, and deleting your readings in KeepSay takes out everything it wrote there. KeepSay keeps a note of which readings it wrote, on your phone with your readings, encrypted, and deleted with them. Read from your phone's own health app, if you choose. On the same page you can choose to have KeepSay show heart rate, steps, sleep and blood oxygen from your phone's own health app in place of your band's, each kind by itself, for another watch or band, or none; with heart rate comes the resting rate kept beside it. Your phone asks you first. KeepSay reads them on your phone while it draws your day, and keeps no copy of them: not on your phone, not in your account and not in your encrypted backup. They are health readings like your band's, and like them they are never sent to our services or to any AI model. What KeepSay itself wrote there is never read back as another source's. Nothing read from your phone's health app, and nothing KeepSay writes there, is used for advertising or sold.

Registering your interest

If you ask us on our website to tell you when the KeepSay band can be ordered, we keep the email address you give us, and what you told us you would record if you chose to say, for that purpose only. We email you when the band is available, and then delete your details. We never use them for anything else, never add you to other mailing lists, and never share them. You can ask us to delete them sooner at any time, at m.tufailkhan007@gmail.com.

Redeeming a code

If your KeepSay band came with a code for Plus and you redeem it on our website, you sign in there with your KeepSay account, and the code is sent to our service to be checked. We never store the code itself, and it never goes into our logs: we keep a fingerprint of it (a one-way hash, which can't be turned back into the code), and once it is redeemed, which account redeemed it and when. That is how each code works only once, and how your account gets its Plus. The website keeps you signed in only until you close its tab.

Invites

Every account has an invite code, which is kept with your account together with how many friends have joined with it and the free months they brought. If you add a friend's code, we record which account invited yours. While that invite waits, and only then, the app sends our notes service the hardware address of the KeepSay band your phone connects to. We never store the address, and it never goes into our logs: we keep a fingerprint of it (a one-way hash made with a secret key, which can't be turned back into the address) and when it counted, so that each band counts for one invite only. The fingerprint names no account.

Research, if you choose to help

When you set up KeepSay you can choose to help with research, and change that choice in Settings at any time. Your choice is recorded on your phone. Nothing is collected for research today: no reading of yours is used for it. If a study with ethics approval begins, we will tell you what it involves and ask you again before anything leaves your phone.

Our website

Our website sets no cookies and uses no analytics or advertising trackers. It keeps two small notes in your browser: the colour you pick for the page, until you clear your browser's data, and that you have seen its opening animation, until you close the tab. Registering your interest and redeeming a code work as described above.

Who helps us

We use a small number of service providers to run KeepSay: for sign-in, for the cloud copy of your library and our website's interest list, for hosting our website and our notes service, for transcription and writing notes, for notifications, for crash reports, for confirming that requests come from KeepSay, and for subscriptions. They process your data only on our instructions and only to provide KeepSay, under agreements that bind them to protect it. We do not sell your data or share it with anyone for advertising.

Some of these providers may process data outside the country where you live. When that happens, we rely on safeguards recognised by data protection law, such as standard contractual clauses. You can ask us at m.tufailkhan007@gmail.com which providers these are and where they process your data.

Health information in what you say

Recordings can contain health information: an appointment, a diary entry, a conversation about how you feel. We process it only to give you your transcript, notes and answers, and only with the explicit consent you give when you set up KeepSay. KeepSay summarises what was said. It does not diagnose, give medical advice or infer a mood from your voice.

To treat each recording with the care it needs, KeepSay gives it a handling level: whether it talks about health, about someone's own feelings, or about someone's safety. Our own rules set the level from the words, and the AI provider that writes the notes can raise it in the same step, never lower it. The level only decides how KeepSay treats the recording, such as suggesting a private shelf or showing where to find support. It is never a finding about you, and it is never shown as one.

The basis for using your data

We use your data to provide the service you signed up for, under our agreement with you. We use health information in what you say only with your explicit consent, which you can withdraw at any time. If you register your interest on our website, we keep your email with your consent. We keep a band's fingerprint for invites in our legitimate interest in making sure each band counts once. We receive crash reports in our legitimate interest in keeping KeepSay working, and you can turn them off at any time. We count how long a first note took in our legitimate interest in knowing whether KeepSay's first steps work. We keep payment and account records where the law requires us to.

How long we keep things

• Recordings you delete: kept in Recently deleted, on your phones and in your account, for 30 days, so you can put them back; then deleted, with their transcript, notes and backed-up audio. Delete now, or Empty, deletes them at once.
• Audio sent for notes: deleted once the notes are written, and within 24 hours at the latest.
• Audio backup, if you turn it on: each recording's audio is kept for as long as your plan keeps it (90 days on Plus, a year on Pro, counted from its backup), for 30 more days after a change to a plan that keeps less, and is deleted sooner when a recording you deleted leaves Recently deleted, turn the backup off and choose to delete what it kept, delete your encrypted backup, or delete your account.
• Questions and the lines sent with them: deleted once answered. Answers are deleted within ten minutes.
• AI tools you connect: which tool you gave leave to, the shelves you ticked and the last day it read, until you take the leave away or delete your account. A record of each read, with which recordings it read and how much but never the words it searched for, until your phone has listed it, and for thirty days at most.
• Crash reports: kept for 90 days, then deleted.
• The identifier the version check uses: kept by our configuration service until we ask for it to be deleted. It is never linked to your account.
• A new phone's address on your Wi-Fi, while it waits for recordings from your old phone: deleted when the move ends. If the move is cut short, it expires after fifteen minutes and is deleted within a day.
• Your library's copy in your account: kept until you delete it or delete your account.
• A shared space, its shelves and who is in it: kept until its owner closes it or deletes their account. Your copies on its shelves: kept until you take them off, leave the space, are removed from it, or delete your account. A to-do ticked there, with who ticked it: kept until it is unticked, its recording comes off, the person who ticked it leaves, or the space closes. An invitation, with the address it was sent to: kept until it is answered or taken back, and for 14 days at most.
• Your plan and each month's hours: kept until you delete your account.
• How long your first note took: kept only as one more in the count, which holds no name and no account, for as long as we measure KeepSay's first steps. The note that your account has been counted, and when, which holds no number: kept until you delete your account.
• A code you redeemed: its fingerprint, with the account that redeemed it and when. If you delete your account, which account redeemed it is deleted too; the fingerprint and when it was redeemed stay, marked as used, so that the code can never be used again.
• Your invite code, who invited you, and the friends and free months your invites brought: kept until you delete your account. If you do, the friends you invited no longer show who invited them.
• A band's fingerprint, once it has counted for an invite: kept, naming no account, so that the band can never count again.
• Your email, if you registered your interest: kept until we have told you the band can be ordered, then deleted, or sooner if you ask.
• Your own API keys: kept on your phone until you remove them in Settings, delete everything on this phone, or uninstall KeepSay. We never have a copy.
• A reminder you chose to have in your calendar: there until you take the reminder off, turn the choice off, or delete everything on this phone.
• Your calendar entries, if you turn on Read your calendar: never kept. KeepSay reads them when it needs them and lets them go.
• Everything on your phone: kept until you delete it or uninstall KeepSay.

Your rights

Wherever you live, you can ask for a copy of your data, have it corrected or deleted, restrict or object to how it is used, take it with you, and withdraw your consent at any time. These are the rights the GDPR gives, and we give them to everyone who uses KeepSay. In KeepSay you can export your data (Settings, then Account, then Export your data), withdraw your consent to health readings (Settings, then Privacy, then Health readings), delete your encrypted backup (Settings, then Privacy, then Encrypted backup) and delete your account and everything in it, with everything on your phone at the same time if you choose (Settings, then Account, then Delete your account). For anything else, contact us at m.tufailkhan007@gmail.com. You can also complain to the data protection authority where you live.

Keeping it safe

Everything sent between the app and our services is encrypted in transit, and the copy of your library in your account is encrypted at rest by our cloud provider. Recordings on a private shelf get a further layer: in your account's copy, their transcripts, notes, posters and study sets, and their titles, your notes on them and the names you gave their voices, are encrypted with a key of your account's own, which we keep encrypted in turn. On your phone the same key encrypts them again, their audio included, under your phone's own security and KeepSay's private lock. While you listen to one, an opened copy of its audio is kept in KeepSay's own cache, and deleted when you close it, or at the next start at the latest. Your band's readings are also encrypted by KeepSay with a key kept in your phone's secure storage. If you turn on encrypted backup, each day is encrypted again on your phone before it is stored, with a key that only your passphrase or your recovery words unlock, and that is never sent to us. If you turn on audio backup, each recording's audio is encrypted on your phone with that same key before it is uploaded, and is fetched and opened the same way: in the browser, it is opened in the page itself and kept only in its memory. The band itself has no Bluetooth security, which is why KeepSay removes each recording from the band once a verified copy is on your phone. The band also keeps about a week of its own readings until it writes over them, and while it holds them someone nearby with the right tools could read them.

Children

KeepSay is not intended for anyone under 16.

Changes

If we change this policy, we will update the date at the top and tell you in the app before the change takes effect.