Privacy Policy
Last updated: 15 November 2026
Plain-language draft. We wrote this to be honest and readable, but it has not yet been reviewed by a lawyer. If anything is unclear, email skelifywpd@gmail.com.
The short version
Brimful is built so that we know almost nothing about you. Your jars, amounts, notes and history are stored on your own device. They are never sent to us in a form we can read: if you turn on the optional cloud backup, your device locks (encrypts) the copy with your recovery code before it is uploaded, and we can't open it. There are no accounts, no analytics, no advertising and no tracking.
Who we are
Brimful is made and run by SCALIFY WPD, a small team based in Bole, Addis Ababa, Ethiopia (operated by an individual; not yet a registered company). Contact: skelifywpd@gmail.com. We are the "controller" of the small amount of personal data described below.
What stays on your device
Jar names, targets, dates, deposits and withdrawals, notes, challenges, your split percentages and your settings (currency, theme, motion, sound) are saved in your browser's local storage. If you turn on cloud backup, your recovery code is saved there too, so the app can keep the backup up to date. If you use Save Together, the invite keys and your member secret for each shared jar are saved there as well. We cannot see, copy or recover any of this. If you clear your browser data or lose the device, it is gone unless you downloaded a backup file or turned on cloud backup and kept your recovery code.
What we receive, and why
| Data | When | Why | Legal basis | Kept for |
|---|---|---|---|---|
| Birr payments: the method (Telebirr or Bank of Abyssinia), the name the payment came from, the transaction ID you type, the amount, and whether we confirmed it | Only if you buy Plus in birr | To match your transfer, unlock Plus, and handle refunds | Contract | While your licence is active, and afterwards only as long as tax or accounting rules require. If we couldn't confirm a payment, we delete the record 180 days after telling you |
| Card payments: Whop's payment ID, the amount, and whether it went through or was refunded | Only if you buy Plus by card | To unlock Plus automatically and handle refunds | Contract | As for birr payments. A checkout you start but don't pay is deleted after 3 days |
| Your confirmation that you are 18 or older, or that a parent or guardian agreed (a yes/no) | When you buy Plus | To show the purchase was allowed | Contract and legal obligation | Same as the payment record |
| Encrypted cloud backup: a locked copy of your app data, stored under a lookup number made from your recovery code | Only if you turn on cloud backup; updated about 15 seconds after you change something | So you can restore your jars on another device | Your request (you can withdraw it any time) | Until you turn it off or delete everything, or automatically 400 days after its last update. We can't read its contents |
| Your licence key (a random code) | When you buy or restore Plus, and about once a day while the app is open | To confirm the licence is valid | Contract | Same as above |
| Save Together (shared jars): the jar's name, goal and preset, each member's chosen display name and colour, and each deposit's amount and note, all encrypted on your device with the jar's invite-link key. Not encrypted, because the service needs them to work: which member slot added each deposit, how many deposits each member has added, when people joined, and timestamps | Only if you create or join a shared jar | To show the jar to its members live and apply its rules (6 people, free deposit limit, only you can remove your own deposits) | Contract | Until the person who made the jar deletes it, or automatically after 400 days without activity. If you leave or are removed, your deposits stay in the jar's total |
| Technical request data such as IP address and browser type | Whenever any website is loaded | Delivery, security and limiting abuse. We use the IP address briefly to limit repeated payment submissions and do not store it ourselves | Legitimate interests | Hosting logs are kept by our host for a limited time under its own policy |
We never ask for your Telebirr PIN, bank password or ID. If you pay by card, Whop collects your card and contact details under its own privacy policy; we never receive your card number, and we don't copy your email from Whop into our records. We don't collect your email unless you write to us.
Who helps us run it
- Vercel hosts the website and Scalify's payments service (scalify-wpd.vercel.app). The payments service currently runs in the United States; the database it uses is in the EU (Frankfurt).
- Supabase stores the payment records and encrypted backups listed above (database region: EU, Frankfurt).
- Whop processes card payments under its own terms and privacy policy.
- Telebirr (Ethio telecom) or Bank of Abyssinia process your transfer under their own terms. We see what appears on our own statement.
- Telegram delivers a message to us when a payment arrives. It says only the product, amount and payment method: never your name, transaction ID or licence key.
We don't sell or share your data with anyone else. These providers may process data outside your country, including the EU and the United States.
Your choices and rights
- Delete your app data: Settings → "Delete everything on this device", or clear your browser data.
- Take your data with you: Settings → "Download a backup".
- Payment records: email us to ask for a copy, a correction or deletion. We'll answer within 30 days. We may need to keep some records where the law requires it.
- Depending on where you live (for example the EU or UK), you may also have the right to object, to restrict use, and to complain to your data-protection authority.
Children
Brimful is for people aged 13 and over and is not directed at younger children. The app itself collects no personal data from anyone. To buy Plus you must confirm that you are 18 or older, or that a parent or guardian has agreed. A parent or guardian can ask us for a refund under the Refund Policy. If you believe a child under 13 has sent us payment details, email us and we will delete them.
Security
Payment records are stored in a database only our server can read. Cloud backups are encrypted on your device with AES-256 using a key made from your 20-character recovery code; the code never leaves your device, so neither we nor our providers can read a backup, and if you lose the code nobody can recover it. Shared jars are encrypted the same way with a random key that is part of the invite link (after the "#", which browsers don't send to servers). Anyone who has the link can open and join the jar, so share it only with people you trust; the person who made the jar can remove members. If a backup file is shared, the invite keys inside it are shared too, so keep backup files private. Your app data's safety also depends on your device: anyone who can unlock your phone and open your browser can open Brimful.
Changes
If we change what we collect, we will update this page and its date before the change takes effect.