01What stays on your device
When you add a card in Settings, Divide stores the following in your browser’s local storage:
- A nickname you choose
- The last four digits, if you enter them
- The card network (Visa, Mastercard, Amex, Discover)
- The credit limit you enter
- The utilization percentage you enter
- The reward rates you enter or accept from a template
- Whether the card has a foreign transaction fee
Your credit limit, your last four digits, and the card network stay on your device; they are not sent anywhere. Your nickname, reward rates, and utilization are included in usage events (see below). If you uninstall Divide, the local copy goes with it.
Your preferences (your optimization focus, split threshold, any goal you set and its end date, and your analytics and developer-mode settings) are stored the same way.
02What Divide sends to us
Divide sends usage events so we can tell whether recommendations are working and where detection fails. These events are not linked to your name, your email, or any account. Each installation gets random identifiers instead: a random ID from Firebase’s anonymous sign-in, and a random Google Analytics client ID.
Events are sent when you open the Divide panel, change the category, type or confirm an amount, choose a different card than the one recommended, apply a recommendation, and when Divide’s checkout reminder is shown, clicked, or dismissed.
An event may include
- When it happened, and a random ID for the event
- The merchant’s domain (for example
amazon.com), not the full page address - The detected purchase category, what Divide guessed, and whether you changed it
- The exact purchase amount, a rough range for it, whether it was detected or typed by you, and how confident detection was
- The nickname of the card Divide recommended and of the card you chose
- For those cards: a random card ID Divide created, the reward rate, the utilization percentage you entered, the utilization after this purchase, and Divide’s score
- Whether you followed the recommendation, and the score difference if you didn’t
- Whether a split was suggested, the amount proposed for each card, and whether the store supports two cards or a gift-card route
- Whether a card would go over its limit, and how stretched your cards are overall
- How many cards you have saved, your optimization focus setting, and which goal is active, if any
- The extension version, your install type, and whether developer mode is on
- The random identifiers for your installation described above
An event never includes
- Card numbers or CVV
- The last four digits of your cards
- Your name, email address, or postal address
- Bank or merchant login details
- The content of the page you are viewing
- The full page address
03Where that data goes
Usage events are sent to:
- Google Firebase Realtime Database, where they are stored. Access is restricted to Divide’s team.
- Google Analytics 4, which we use to summarise usage. Google Analytics receives the amount, domain, category, reward rates, utilization percentages, and scores, but not card nicknames or card IDs.
Both are operated by Google, and Google’s own privacy terms apply to data it processes on our behalf. We do not sell data to anyone, and we do not share it with advertisers, card issuers, or merchants.
04This website
- Launch-update signups: if you sign up on dividepay.ai, we collect your email address and whether you want launch updates or already use Divide. Klaviyo stores the list and sends the emails. Unsubscribe with the link in any email.
- Hosting: the site is hosted on GitHub Pages, which receives standard technical data like your IP address when your browser loads it.
- Fonts: the site loads fonts from Google Fonts, which receives your IP address and browser type.
- The website uses no analytics or advertising cookies.
05How long we keep things
Usage events are kept until they are deleted. There is no scheduled purge yet. When we add one, we will update this page.
Before they’re delivered, queued events wait on your device (at most 1,000 events or 5 MB) and are removed from your device once delivered.
Signup emails are kept until you unsubscribe.
06Your choices
Turn off analytics
Divide’s Settings page has a “Share usage analytics” switch. It is on by default. Turning it off stops collection and delivery and erases any queued events. Events that were already delivered are not recalled.
Usage events and deletion
Usage events aren’t tied to your name or email, so we can’t look up your events from an email request alone. Turning off analytics stops all future collection.
Remove everything locally
Settings has an “Erase local data” button that clears your cards, preferences, and queued events on this device. Uninstalling the extension does the same. Events already delivered are not affected.
Export your data
Settings has an “Export JSON” button that gives you your cards, preferences, and the recent event history stored on this device.
07Depending on where you live
If you are in the European Economic Area or the United Kingdom, you have rights to access, correct, delete, and object to the processing of your personal data. If you are in California, you have rights under the CCPA, including the right to know what is collected and to request deletion. We do not sell personal information as that term is defined under the CCPA.
To exercise any of these, email privacy@dividepay.ai. For your signup email, we can find, correct, or delete your record. For usage events, see “Usage events and deletion” above.
08Children
Divide is not directed at children under 13 and we do not knowingly collect information from them.
09Changes to this policy
If we change what Divide collects, we will update this page and change the date at the top. Where the change is significant, we will ask for your consent inside the extension before it takes effect, as the Chrome Web Store requires.
10Contact
Divide, operated by Kimani Tate
United States