Privacy policy

1. Who processes the data

KIPRI is developed by an independent developer. You can get in touch at the support address shown in the site footer and on the "About" screen of the app.

2. What data is processed

How much depends on whether you use an account.

• Without an account, your records (tasks, notes, birthdays, reminders, habits) are stored on the device only and are not transmitted anywhere. Usage events and crash reports are not sent in this mode either.
• With an account we process your email address, display name and uploaded avatar, plus the records themselves, so they can sync across devices. If you sign in with Google, we receive your email address and name from your Google account.
• Attachments: photos and audio in notes. On plans with cloud attachments enabled, a copy of the files is kept in cloud storage; on other plans the files stay on the device only.
• The device push token, used to deliver notifications and service announcements. It is stored together with your account ID and removed when you sign out.
• Usage events: what happened in the app (the app was opened, a task was created or completed, a reminder was snoozed, the assistant got a command, a plan limit was reached and the like), when it happened, and short technical parameters: where the action came from (manually or from a notification), what kind of assistant command it was and whether it was understood, which section hit a limit, which plan you are on. Events are stored with your account ID, so they are not anonymous. The text of your records, titles, names and the words of assistant commands never enter events.
• App crash reports: the error message, stack trace, app and operating system version, and the screen where the crash happened. If you are signed in, the report is stored with your account ID. The content of your records is not included.
• Your plan, redeemed promo codes and subscription state.

3. Where data is stored

A local copy always lives on your device, because the app works offline and needs no connection to save anything.

The cloud copy (when you are signed in) is stored in a Supabase database in the eu-north-1 region: the servers are in Stockholm, Sweden. Cloud attachments live there too, in Supabase storage. Access to rows and files is restricted by database-level security policies: queries return only the data belonging to your account.

The database is backed up once a day. Backups are encrypted, kept in private GitHub storage (Microsoft) for no longer than 14 days and then overwritten.

4. Who data is shared with

Data is never sold and never shared with advertising networks. There are no ads in the app at all.

Processing involves the technical providers the service cannot run without. Each one receives only what its part of the work needs:

• Supabase - hosting for the database, sign-in and attachment storage (eu-north-1 region, Sweden).
• Resend (Resend, Inc., USA) - sends emails with address confirmation and password recovery codes. It receives your email address and the email text.
• Google - Google sign-in, if you choose it; push delivery on Android through Firebase Cloud Messaging.
• Apple - push delivery on iPhone through the Apple Push Notification service.
• Expo Push Service - relays push notifications to the Google and Apple services.
• GitHub (Microsoft) - storage for the encrypted database backups.
• The device speech recognition service - voice input. On Android this is usually Google’s service, on iPhone Apple’s; audio may be processed on these companies’ servers under their own terms. The app receives only the recognised text from the service and parses the command itself: neither the audio nor the command text is sent to KIPRI servers.
• Kipri’s voice is pre-recorded files: they are downloaded once from kipriassistant.com and then play from the device, and phrases without a recording are read by the system speech synthesiser. Your voice goes nowhere except the speech recognition service and is not stored.

5. How long data is kept

Records are kept until you delete them. A deleted record survives for a while as a deletion marker, otherwise your other devices would never learn it should go. Those markers are physically cleared after about a month.

Habit check-in history is kept for a limited period (over a year) and cleared automatically beyond that.

Usage events are kept for 90 days and then deleted. Every day they are rolled up into a summary with no link to individual people: how many people opened the app and how many events of each kind happened. Crash reports are kept for 30 days.

Database backups live no longer than 14 days, so anything deleted from the database is gone from them within 14 days as well.

If you delete your account, the data associated with it is deleted along with it. How to delete the account and what stays afterwards is explained on the Delete your account page.

6. Your rights

You can export your data from the app on any plan, the free one included, delete individual records or the whole account, turn sync off and keep working locally, and switch notifications off.

A deletion request can be sent to the support address, including without the app: the Delete your account page explains how. We carry it out without conditions or extra requirements.

7. Children

The app is not intended for children under 13 and does not knowingly collect their data.

8. Site analytics

The kipriassistant.com website counts visits with its own analytics running on the same server as the site itself. Nothing is sent anywhere else: there are no third-party analytics services here.

The counter sets no cookies and does not store your IP address. Only a country is derived from it, after which the address is discarded. What is recorded is the page you opened, where you came from, screen size, browser and system, plus a few on-page actions: clicking the download button, opening Telegram, switching language or theme, whether you read an article to the end, and in the notification settings checker the phone brand you picked, what exactly is wrong with the notifications and which app you are setting them up for, whether you started the list, whether you came back to a started list with the «Continue» button, which step helped, whether you opened the QR code, whether you saved a brand page for offline use, whether you completed, copied or shared the list, and which answer you gave in the live test: the reminder arrived on time, late or not at all, plus whether you scrolled to the app card and pressed its button. In the Eisenhower matrix article only the fact that you sorted a list or went through it with the question is recorded; the tasks themselves are never sent anywhere. In the birthday calendar we record that a person was added, a list was pasted, a contacts file was loaded or the calendar file was downloaded; names and dates stay in your browser, and the contacts file is read there and never sent to the server. In the habit tracker we record that a habit was added and that a day was ticked; habit names and ticks stay in your browser. In the date calculator we record only that the calendar file was downloaded; the dates themselves are never sent. On the printables page we record which template was sent to print; your habits and items stay in your browser. In the recurring reminder builder we record that the calendar file was downloaded and which kind of repeat it held; the reminder name and the dates are never sent. If you came to the notification check by a link from another app’s developer, we record only that fact: the app name from the link is not stored. On the page for developers we record that the link was copied. In the alarm check we record which clock app and which problem you picked. In the iPhone notification check we record which problem you picked. In the packing list we record that you started filling it in, which set you added and that it was sent to print; the items themselves stay in your browser. On the blog we record whether you shared an article and how, and your answer to «Did this help?». Your reading history for «Continue reading» stays in your browser and is never sent to the server.

So that pages you have opened work without a connection, your browser keeps copies of them in its own storage on your device. Only you can see these copies, and they are never sent to the server. You can remove them by clearing the site data in your browser settings.

All of it exists to tell us which texts are useful to readers. None of these records can be tied to a particular person or to an account in the app.

9. The iPhone release email

In the iPhone notification check you can leave an email address to hear when the iPhone version is out. Along with the address we store whether you ticked that you want to try the app before release. One email about the release goes to that address, and it carries a promo code for three months of the Plus plan. The code is entered in the app, which needs an account. Those who ticked testing get the build ahead of the public release, and we may write about the testing itself. The address is stored on the same server as the site, is not shared with anyone and is not used for marketing mailings.

The Android version is already out, its form has been removed from the site, and no addresses left for Android are stored. iPhone addresses are deleted after the iPhone release email. To have yours removed earlier, write to the support address in the site footer.

10. Changes to this policy

If the policy changes, the update date at the top changes too, and material changes are announced in the app and in the Telegram channel.