Privacy Policy

Nabbins is made by Systems and Models Technology Development LLC ("Nabbins", "we", "us"), 971 US Highway 202N, Suite N, Branchburg, NJ 08876. You can reach us using the details in Contact us, at the end of this policy.

This policy covers the Nabbins app, our website (nabbins.com) and our email list. It explains what we collect, why, who handles it for us, how long we keep it, and the choices you have.

The short version #

• Nabbins never moves your money. It reads the accounts you connect. It can't make payments or transfers.
• Nabbins never sees your bank password. You sign in to your bank in Plaid's screen or on your bank's own page, not in ours.
• We don't sell your personal information, and we don't share it for cross-context behavioral advertising. The app doesn't track you across other companies' apps and websites, and doesn't use your data for advertising. It has no advertising SDK, no advertising ID, and no third-party SDK that tracks what you do in the app. We run limited first-party product analytics on our own servers (section 1.4a). RevenueCat processes your subscription information and membership metrics for us (section 1.7).
• Your budget is kept on our servers so it's there when you sign in again. We use it to run Nabbins for you.
• You can delete your account in the app. See "Deleting your account" below.

1 · What we collect, and why #

1.1 Your account #

We use your email address for your account, for support, and for emails about your membership.

1.2 Bank data, through Plaid #

When you connect a bank account, our partner Plaid connects to your bank and passes us read-only data from it. We don't request account or routing numbers. We receive and store:

• the name of your bank;
• each account's name, type and the last 4 digits of its account number;
• each account's balances;
• your transactions: amount, date, the name and merchant on the transaction, its category, whether it's pending or posted, and a check number if it has one.

Why: to work out what you have left to spend, match transactions to your bills, and show you your own figures.

How it's kept: new transactions wait in a queue on our server until your phone collects them. They're then deleted from the queue, or after 90 days if your phone doesn't collect them. Once collected, they become part of your budget, which we keep on our server (1.4).

To connect, we give Plaid your Nabbins user ID. We don't give Plaid your name, email address or phone number.

1.3 Plaid's own collection #

When you connect an account, you use Plaid Link, Plaid's own screen inside the app. Plaid collects information there under its own End User Privacy Policy, including your bank sign-in details (which we don't see). That policy also describes device and network information Plaid may collect as its own business, such as your IP address and device details. Plaid's own declaration for the app's privacy label lists one data type: a user ID it links to you, used to make Link work, and not for tracking. Plaid also keeps data from your connected accounts under its own policy.

Read Plaid's End User Privacy Policy before you connect: https://plaid.com/legal/#end-user-privacy-policy. You'll be asked to agree to it in Plaid Link.

You can see and manage the connections Plaid holds for you in Plaid Portal (https://my.plaid.com).

1.4 Your budget and plan #

We keep these on our servers (Supabase), for as long as you have an account:

• your budget and its history: every entry Nabbins records, built from your transactions and what you do in the app, with its amounts, dates and merchant names;
• your plan: how and when you're paid, your bills (names, amounts and schedules), your spending, savings and set-aside amounts, your cards, and your accounts (name, type and last 4 digits), with the number of banks connected and their names;
• what you type: names you give bills and savings, notes you add to entries, and where a deposit came from;
• your settings, such as which reminders are on.

Why: to work out and show your figures, and so your data is there when you sign in again.

A record of each saved change. To keep your phones in step, our server also keeps a short record of each change the app saves: when it was saved and which phone saved it (its per-install ID). It doesn't hold the change's contents, which are part of your budget and plan. It's kept with your account and deleted with it.

On your phone: the app keeps a working copy of this, and changes waiting to reach our server, plus your sign-in session. If you moved data from your phone to our server and the server's copy was kept, the app also saves your phone's earlier copy as a file on your phone. Like other app data, these are included in your device or iCloud backups unless you've turned app backups off. Those backups are controlled by you and Apple.

On your other phones: if you're signed in on more than one phone, each keeps its own working copy. When your account is deleted, each other phone deletes its copy, its sign-in session and its scheduled reminders the next time it opens Nabbins and reaches our server. We can't confirm a phone we can't reach: until then, for example while it's offline, its copy stays on that phone, though it can't sync or reach your account.

1.4a How you use the app #

The Share usage data switch, in short

• What it controls: the first-party usage events below, which go only to our own servers. It isn't a setting for sharing with outside companies; we don't share usage events with any.
• Where: You › Privacy, set on each phone. On by default, including on a new install or a second phone.
• What it stops: usage events from that phone, including any still waiting to be sent.
• What it doesn't stop: events our server already has (deleted 120 days after our server received them, or when your account is deleted, whichever comes first), and app-open times, which time your reminders.

App opens. Your reminders are scheduled on your phone, and they fire at about the time you usually open Nabbins. To work that out, the app keeps the times of day of your 7 most recent opens (the hour and minute only, not the date). With 3 or more, the reminder time is the middle one of them, rounded to 5 minutes and kept between 7:00 a.m. and 9:00 p.m.; with fewer, it's 9:00 a.m. These 7 times are saved with your plan on our servers, so your other phones and a new phone time your reminders the same way. Our server doesn't use them for anything else. They aren't usage events, and the Share usage data switch doesn't cover them. They're deleted with your account.

Usage events. The app also records a short list of usage events, to see which features are used most or not at all and to improve Nabbins:

• starting and finishing setup, and the setup steps;
• seeing the membership screen, and starting a membership;
• starting to connect a bank, and whether it worked (with a code for why, if it didn't);
• the screens you open, the buttons you tap, the answers you pick to questions in the app, and opening your payday screen.

For each event we store only your account ID, the event's name, the screen, the button and the answer (each from a fixed list), the app version, the time it happened and the time our server received it. Events don't include amounts, merchant names, bank or account details, transaction descriptions, email addresses, budget figures, or anything you type.

• Where they go: our own servers, kept apart from your budget data. They aren't sent to any outside analytics or advertising company; Supabase stores and processes them as our host (section 3).
• Before you sign in: events from the welcome screens, setup and the membership screen wait on your phone and are sent under your account once you sign in. If you don't sign in, they aren't sent.
• How long we keep them. We keep two separate sets:
  • Your events, linked to your account: deleted 120 days after our server received them, or when your account is deleted, whichever comes first. If your phone was offline, an event can reach us up to 30 days after it happened.
  • Weekly totals: each week, we count events by week and broad category, such as "setup" or "bank connection", not by individual screens, buttons or answers. The totals have no account ID, are stored separately, only include groups of at least 10 members, and are designed not to identify individual members. A group with fewer than 10 members isn't stored at all, and we also leave out any total that would let a hidden one be worked out from the others. We keep the totals indefinitely. Events deleted before a weekly count (for example because you deleted your account) aren't counted; totals already written stay.
• Your choice: Share usage data, in You › Privacy, is set on each phone, and starts on, including on a new install or a second phone. Turning it off stops that phone sending usage events and clears any waiting on it. It doesn't delete events our server already has; those are deleted 120 days after our server received them, or when your account is deleted, whichever comes first (section 6).

We don't use an advertising ID for this, and we don't link it with other companies' apps or websites.

1.5 Notifications #

Nabbins' reminders are local notifications: your phone schedules and shows them. We don't collect a notification token, and no notification passes through our servers. A notification can show on your lock screen, depending on your phone's settings. You can turn them off in the app or in iOS Settings.

1.6 Technical logs #

Our app's back end runs on Supabase. We use its logs to run, secure and fix the service.

• Request and server logs include your IP address. They're kept for 1 day.
• Sign-in audit logs record events such as signing in, signing out and session refreshes, with your IP address. One copy is kept in our database while your account exists, and is deleted when your account is deleted. Supabase's copy in its log storage is kept for 1 day.

If we need to investigate abuse or a security problem, we may keep the records involved for longer, for as long as the investigation needs.

1.7 Your membership #

You subscribe through Apple's in-app purchase. Apple takes payment, and neither we nor RevenueCat receive your card number or payment details.

We use RevenueCat to process memberships for us. It receives your Nabbins user ID, your App Store receipt and purchase records, whether you're in a trial or subscribed, and which plans are offered to you. With each request it also receives your device's identifier for apps from the same developer (Apple's IDFV, not an advertising ID), your device model, iOS and app version, language settings and App Store country, and your IP address. We use this to know whether you have a membership, to restore purchases, and to measure how memberships are doing (membership metrics, such as how many trials become memberships).

Apple keeps its own records of your purchase, under Apple's privacy policy. RevenueCat's copy is separate: we ask RevenueCat to delete it when your account is deleted (section 7).

1.8 Our website #

Our host, Vercel, receives your IP address, browser details, the page you asked for, and a city and country worked out from your IP address, so it can deliver the site and protect it from attacks.

We count visits with Vercel Web Analytics. It uses no cookies. For each page view it records the page, the site that sent you, any tags in the link, your country, region and city, and your device type, operating system and browser. It tells visits apart with a code made from your request, which is discarded after 24 hours, so it can't follow you from day to day or onto other sites. We see totals.

Google Analytics, only with your consent. If you accept analytics cookies in our cookie banner, our website also loads Google Analytics 4. Until you choose, and if you say no, it doesn't load. We use Google's Consent Mode in basic mode, so nothing is sent to Google before you accept, and nothing after you reject. If your browser sends Global Privacy Control, it stays off. When it runs, it sets cookies (_ga and _ga_<ID>) and records the pages you view, what you do on them (for example, starting the sign-up form), the site that sent you, your device, browser and operating system, and your approximate location (country, region and city), which Google works out from your IP address. Its cookies last 6 months. Google Analytics 4 doesn't log or store IP addresses. We've set it up this way:

• Google Signals is off, and so are advertising features and ads personalization;
• it isn't linked to Google Ads or any other advertising account;
• data-sharing settings are off (Google products and services, modeling contributions, technical support and business insights);
• data is kept for 2 months;
• we don't send it a user ID, your email address, or anything from the app.

You can change your choice with Cookie settings at the bottom of any page, or install Google's opt-out browser add-on (https://tools.google.com/dlpage/gaoptout). Google's privacy policy: https://policies.google.com/privacy.

Our website sets no advertising cookies. Apart from Google Analytics with your consent, it uses only essential storage, which is always active (listed in our Cookie Notice).

1.9 Our email list #

If you join our list on the website, our email provider, Buttondown, receives:

• your email address;
• the page you signed up on, and any campaign tags in the link that brought you there;
• technical details your browser sends, such as your IP address and device details.

Opens and clicks. Our emails record whether you open them (using a small image) and which links you click (links pass through Buttondown before reaching the page). We use this to learn which emails are useful and improve them. To limit it, see section 6.

We use the list to email you about Nabbins. Every email has an unsubscribe link. When you unsubscribe, we delete your subscriber profile and personal details, with your opens and clicks, within 30 days. We keep only a suppression record, your email address and the date you unsubscribed, for as long as we run the list, so your address isn't added again by mistake, including in a re-import.

1.10 When you write to us #

Your message, your email address and anything you attach. We use it to reply.

1.11 What we don't collect #

We don't ask for your Social Security number, and we don't pull your credit report. The app doesn't ask for access to your contacts, photos or location, and doesn't use advertising identifiers.

2 · How we use information #

• To run Nabbins: sign you in, connect your accounts, and work out and show your figures.
• To keep Nabbins secure and prevent fraud and abuse.
• To manage your membership.
• To contact you about your account, and, if you joined our list, about Nabbins.
• To see which features are used, fix problems and improve Nabbins, using our logs, app usage events (1.4a), membership figures and, for email, opens and clicks.
• To meet legal obligations.

We don't use your bank data to target ads, or to sell you anything other than Nabbins. Nabbins doesn't give financial, investment, tax or debt advice.

3 · Who handles information for us #

These companies run parts of Nabbins for us. They handle information to provide their service to us, under contracts with us.

Their subprocessors. These providers use other companies of their own, such as cloud hosting and support tools, to run their services. Each publishes its list: Supabase, RevenueCat and Buttondown. Google lists its own for Google Analytics at https://business.safety.google/adssubprocessors/.

These companies act under their own privacy policies:

We also share information when the law requires it; to prevent fraud, protect safety or respond to a legal claim; with our lawyers, accountants or auditors under a duty of confidentiality; or if Nabbins is sold or merges (section 10).

4 · No sale, no sharing for ads, no tracking #

• We don't sell personal information, and we don't "share" it for cross-context behavioral advertising, as California law uses those words.
• Google Analytics, on our website, with your consent. With Google Signals, advertising features and data sharing turned off, we use Google Analytics as a service provider that measures our website for us, and not to sell your information or share it for cross-context behavioral advertising. GPC and the "reject" choice keep it off.
• No tracking across other companies' apps and websites. We don't link data from the app or the site with other companies' data for advertising or ad measurement, we don't use your data for advertising, and we don't share it with data brokers. The app doesn't use an advertising ID and doesn't ask to track you.
• Global Privacy Control. If your browser sends a Global Privacy Control signal, we treat it as a request to opt out of the sale and sharing of your personal information, for that browser and, if we can tell who you are, for you. It also keeps Google Analytics off, and you can't turn it on in Cookie settings while the signal is sent.
• Do Not Track. There's no common standard for Do Not Track signals, so we rely on your cookie choice and on Global Privacy Control instead.

Financial privacy notice #

We share information about our customers' finances only as described in this policy: with the service providers in section 3, under contracts that require confidentiality; with Plaid, at your direction, when you connect an account; and in the legal cases listed in section 3. We don't share it with other companies for their own marketing, and we don't do joint marketing. We don't currently share your information in any way that requires an opt-out; if that changes, we'll update this policy and tell you before the change applies, and give you any choice the law requires. We don't sell your data. You can still use the rights in section 8, under the law that applies to you.

5 · How long we keep information #

Inactive accounts. We don't delete accounts because they've been inactive. Your data stays until you delete your account, apart from the shorter periods in the table above. We keep it so that a member who leaves can come back to their history. If your membership has ended and you'd like your data gone, delete your account in the app (You › Delete account), which doesn't need a membership, or email us (see Contact us). If we ever introduce an inactivity rule, we'll tell you how it works before it applies to you.

Bank connections after a membership ends. When your membership ends, we remove your bank connections at Plaid, the same as disconnecting each bank: new transactions stop, and the history already in your budget stays. If you come back, connect your banks again.

6 · Your choices #

• Disconnect a bank. In the app, disconnecting a bank removes Nabbins' connection to it at Plaid: no further transactions from that bank arrive, and we delete our stored connection key for it. Transactions already in your budget stay part of its history. You can also disconnect Nabbins in Plaid Portal (https://my.plaid.com), which stops Plaid sharing new data from your accounts with us.
• Notifications: turn them off in the app or in iOS Settings.
• Email: unsubscribe with the link in any email.
• Limit email tracking: our email tool can't switch tracking off for one person, so to stop opens and clicks being recorded, unsubscribe. Turning off remote images in your mail app also stops open tracking.
• Membership: to cancel, open Settings on your iPhone, tap your name, then Subscriptions › Nabbins › Cancel Subscription. Deleting the app or your account doesn't cancel it.
• Sign in with Apple: to stop using it with Nabbins, open Settings, tap your name, then Sign in with Apple, choose Nabbins and tap Delete.
• Usage events: turn off Share usage data in You › Privacy on each phone. This controls our own first-party usage events; we don't share them with outside companies. To remove events linked to your account sooner than 120 days without deleting your account, email us (see Contact us) and we'll delete your account's usage events by hand. Weekly totals have no account ID, so a request doesn't reach them.

7 · Deleting your account #

In the app: You › Delete account. You'll be asked to sign in with Apple again to confirm. You don't need a membership to do this.

The stages:

• Request received: when you confirm in the app, or when we receive your email.
• Deletion started: straight after you confirm in the app. For an email request, once we've confirmed it's you.
• Deletion complete: see below. The app shows anything still pending.

The order. After you confirm, the app first sends any changes still waiting on this phone. Our server then closes your account to changes and, in this order, revokes Nabbins' Sign in with Apple access, removes each bank connection at Plaid, asks RevenueCat to delete your membership records, and deletes your data on our servers. When our server confirms, this phone deletes its copy.

Deletion complete means our servers have deleted your data and the provider steps we can confirm have finished: Apple sign-in access revoked, each Plaid connection removed, and RevenueCat's delete request accepted. If a step can't finish at once, for example because a provider is down, your account stays closed and our server keeps retrying until it does. Email requests are completed within 30 days of confirming it's you.

Your other phones aren't part of deletion complete. Each clears its copy, sign-in session and reminders the next time it opens Nabbins and reaches our server. We can't confirm a phone we can't reach; until it reconnects, its copy stays on it.

The steps:

1. At Apple: we revoke Nabbins' Sign in with Apple access.
2. At Plaid: we remove each of your bank connections, which ends our access. Plaid then deletes connection data under its own policy, with some exceptions it lists.
3. At RevenueCat: we ask RevenueCat to delete your membership records.
4. On our servers: we delete your account, your name and email address, your Plaid connection keys, your whole budget, plan and settings, your app-open times and the record of each saved change, all your app usage events linked to your account, and any transactions waiting for your phone.
5. On this phone, once our server confirms: the app deletes its copy of your data, any saved copy file, your sign-in session, scheduled notifications and any usage events waiting to be sent.

• On your other phones (not part of deletion complete): each deletes the same things the next time it opens Nabbins and reaches our server. We can't confirm a phone we can't reach.

After completion: request and server logs age out after 1 day (section 5).

Backups: We don't make or keep backups or exports of the app database, and our hosting plan includes no automatic backups.

What other companies keep, under their own policies: Apple keeps its records of your purchases; RevenueCat may keep some records as its policy or the law requires; Plaid keeps what its End User Privacy Policy says it keeps; our email providers (Zoho for support, Buttondown for our list) keep what their policies say for the messages they handled. What we keep: a record that the account was deleted (its user ID and the date, for 24 months); any email exchange about the deletion (12 months); weekly usage totals, which have no account ID, only include groups of at least 10 members, and are designed not to identify individual members; and anything the law requires. Device and iCloud backups keep copies until they're replaced.

Your membership isn't canceled by deleting your account. Cancel it in iOS Settings first.

Without the app: email us (see Contact us) from the email address on your account. Details are at nabbins.com/delete-account.

8 · Your privacy rights #

Wherever you live in the US, you can ask us to:

• tell you what personal information we hold about you, and give you a copy;
• correct it;
• delete it;
• opt out of its sale, sharing for targeted advertising, or profiling. We don't do any of these, so there's nothing to switch off, but you can still ask;
• limit our use of sensitive personal information. We use any sensitive information, such as your financial account data, only to provide Nabbins.

How to ask: email us (see Contact us) from the email address you use with us. We'll confirm it's you before we act, and reply within 45 days. Someone you authorize can ask for you, with your signed permission; we'll check with you before we act. If we can't do something you ask, we'll say why. If you live in a state that gives you a right to appeal, reply to our answer and ask us to reconsider. We'll answer within the time your state's law sets.

We won't treat you differently for using these rights.

California #

What we collected in the last 12 months: identifiers (name, email address, user ID, per-install ID, device identifier for apps from the same developer, IP address); financial information (account names, last 4 digits, balances, transactions, and your budget and plan); commercial information (membership status and purchase records, from Apple through RevenueCat); what you type into the app (names and notes); app activity (the times you opened the app, usage events such as screens opened, buttons tapped, answers chosen, and setup, membership and bank-connection steps); internet activity on our site (pages viewed and site events, including through Google Analytics if you accept analytics cookies; email opens and clicks); and approximate location from IP address on our website. The sources, purposes, recipients and retention for each are in sections 1, 2, 3 and 5. We don't sell or share personal information, and we haven't in the last 12 months. We don't knowingly sell or share the information of anyone under 16. We don't disclose personal information to other companies for their own direct marketing.

9 · Security #

• Connections are encrypted. The app, our servers and our website use encrypted (HTTPS) connections.
• Your Plaid connection keys are stored encrypted on our servers, and are used only to read your accounts and to remove connections.
• We hold little: no bank password, no full account numbers, and only the last 4 digits.
• On your phone, your data is protected by iOS, including your device passcode.
• Access to our systems is limited to the people who need it to run Nabbins. Sign-ins to our Supabase, Plaid, Apple and Vercel accounts use two-factor authentication.
• If there's a breach affecting your information, we'll tell you, and any authorities, as the law requires.

No system is perfectly secure, but we design Nabbins to keep as little as it needs.

10 · If Nabbins is sold or closes #

If Nabbins is sold or merges, your information may pass to the new owner, who must keep to this policy for the information we hold. If Nabbins is discontinued, we'll tell members by email and in the app at least 30 days ahead, explain how to cancel through Apple, remove our bank connections, and delete members' account information and the weekly usage totals described in section 1.4a, except what the law requires us to keep.

11 · Children #

Nabbins is for adults 18 and over who live in the US. We don't knowingly collect information from anyone under 18. If you think a child has given us information, email us (see Contact us) and we'll delete it.

12 · Where information is stored #

We're a US company, and Nabbins is for people in the US. Our app's database is in the United States. Some providers, such as RevenueCat, Vercel, Buttondown and Zoho, may process information in other countries under their own terms.

13 · Changes to this policy #

When we change this policy, we update the date at the top. If a change affects what we collect, how we use or share it, or your choices, we'll tell you before it takes effect, by email or in the app. If we want to use information we already hold in a way this policy didn't allow when we collected it, we'll update this policy and tell you before the change applies, and give you any choice the law requires.

14 · Contact us #

Systems and Models Technology Development LLC
971 US Highway 202N, Suite N, Branchburg, NJ 08876
support@nabbins.com