Sign in Sign up

Privacy Policy

Last updated 2026-10-26 · Effective 2026-10-26

This Privacy Policy explains what IBC Tool collects, how we use it, where it lives, and the choices you have. We have written it to be readable. Where the legal precision matters, we have kept the precision. Where it doesn't, we have kept the prose.

IBC Tool is operated by StarKiln Ventures LLC ("we," "us"), reachable at privacy@ibctool.app.

Contents
  1. What we collect
  2. What we don't collect
  3. How we use it
  4. Where it lives
  5. Service providers
  6. Cookies and local storage
  7. Children
  8. Your rights
  9. Security
  10. Retention
  11. Changes to this policy
  12. Contact

1. What we collect

Account information

When you create an account we collect your email address and your name. We also save the timezone of your browser, which you can change in Settings. We also keep the page of ibctool.app that sent you to sign up and the first page of that visit, the other site that linked you to each of those pages when your browser shares it, and the campaign tags (utm_source, utm_medium, and utm_campaign) of the first page of that visit. A visit starts on the first page that you open in a tab, and again when another site or a link with campaign tags opens a page of ibctool.app. Other parts of those addresses are not stored. We also keep whether you signed up on a phone, a tablet, or a computer, worked out as for the page counts below. We do not store a password. If you enter your email in the form on the home page, we keep your email, the page with the form, the first page of that visit with the other site that linked you to it and its campaign tags, whether you used a phone, a tablet, or a computer, and the IP address of the request. When you sign up, we also add your email to the same list. We keep an entry until you ask us to delete it, or until you delete your account. If you change your account email, the entry moves to the new email.

Insurance and financial data you enter

IBC Tool exists to track whole-life policies and the loans, payments, and budget allocations that flow through them. To do that, we store the data you enter or upload, including:

Third-party connections you authorize

IBC Tool connects to an outside service only when you choose to connect it. Today the only such service is YNAB. Before we add another, we will name it here, describe the data it handles, and ask you to opt in.

Budgeting service (YNAB)

You connect YNAB by signing in on YNAB's own site (OAuth), so we never see your YNAB password. YNAB gives us access tokens, which we keep encrypted with a key stored separately from the database. IBC Tool asks for full access because it writes to your plan, as described below.

What we read. Your plan names, and the accounts, categories, category targets, and scheduled transactions of the plan you choose. We use them so you can pick where each payment is budgeted, and so the sync can see what is out of date. We ignore the balances YNAB includes. We do not read your posted transactions, except a one-time paid-up additions transaction that IBC Tool created, to check whether it has cleared before we change it.

What we write. Only what you set up and confirm: category targets, a category when you ask for one, a scheduled transaction for each policy and loan, and a transaction for each one-time paid-up additions payment you record as not yet made. They carry the policy name, the loan purpose, the insurance company, the amounts, and the dates. We change no other transaction, and we never move money.

What we keep. The tokens, until you disconnect. The name of your plan, until you choose a different plan or delete your account. The YNAB identifiers that link each policy and loan to your plan, until you stop that sync, delete the policy or the loan, choose a different plan, or delete your account. The identifiers of each one-time paid-up additions transaction, until that contribution is deleted. An error message from YNAB, until a later sync clears it or the sync ends. A cached copy of the lists we read, used for at most 15 minutes and removed within about two weeks. We do not store your posted transactions, balances, or the amounts you assign.

No sharing. We never sell data from YNAB or pass it to anyone without your knowledge. Only the providers that host IBC Tool (section 5) process it. It never goes to the service that parses your statements, and it is never used to train AI models.

Deleting it. Disconnect YNAB in Settings to delete the tokens. The sync setup stays, so that reconnecting resumes it. Stop a sync to delete its setup, or delete your account to delete all of it. You can also email privacy@ibctool.app and we will delete it. If we ever read new YNAB data, or use it in a new way, we will update this policy and ask you first.

Sharing with your advisor's practice

If you signed up through a partner practice, such as your insurance advisor's, or we linked your account to the practice that referred you, that practice sees your name, email address, and signup date, and can ask you to share your account. It sees nothing more unless you share.

If you share, in Settings or on the dashboard, the practice can view your account as you see it, including your documents, and a summary of your policies in its partner portal. Sharing is view-only unless you also allow changes. Even then, the practice cannot change who sees your account, your sign-in email, your passkeys, or your YNAB connection, and it cannot download your data or delete your account.

The practice sees no data from YNAB, such as your plan name, categories, or YNAB error messages. But if you use the YNAB sync, a change the practice makes is synced like your own, and it can update your YNAB plan.

Settings shows the practice's recent views and changes. You can stop sharing at any time. We keep the sharing records until you delete your account.

Service-level data

You sign in with a 6-digit code we email you, or with a passkey that you add on your device. We store only a hash of that code. The code expires in 10 minutes, and we never store the code itself. We keep a sign-in session so you stay signed in. A customer session stays until you sign out. It does not expire on its own. For a passkey, we store its public key, a device name such as "iPhone", the date you added it, and the date you last used it. Your device keeps the private key. We never see your face or your fingerprint. Application logs may record IP address and request metadata for the limited purpose of operating and securing the service.

Error reports

We use an error-monitoring service to find and fix problems. When the app hits an error, it sends a report of the error and a short replay of the screen. The replay masks all text, typed values, images, and media in your browser before it is sent. Reports can include the page address, your browser and device type, and details of the request that failed. We remove sign-in codes, the sign-in token, and your IP address before anything is sent. We also send a count of app sessions and, for a sample of page loads, timing data to find slow pages.

Payment records

When you pay for IBC Tool, you give your card to our payment processor. The processor receives the card number, the expiration date, the security code, and the billing details it needs to charge the subscription. The processor does not keep the security code after it authorizes the charge. IBC Tool does not receive or store your card number or your security code.

We do keep the records we need to run the subscription: the plan you chose, the amount, the dates of charges and refunds, and the customer identifier the processor assigns to your account.

Marketing site page counts

We count page loads on ibctool.app, our public site with these policies and the help pages, to see which pages people open. Each count records the page path, the site that linked you there, the campaign tags of the link when it has them, whether the device looks like a phone, a tablet, or a computer, whether the page is the first page of a visit, and the time. We work out the device from the browser's description of itself and from whether the screen is a touch screen of tablet size, and the count stores only the device class. Other parts of the address, such as other query parameters, are not stored. Like any request to IBC Tool, the request that sends a count also appears in the application logs described above.

2. What we don't collect

IBC Tool does not load behavioral analytics platforms, advertising-attribution pixels, or any other third-party tools that track users across pages or sessions, other than the error reports described in section 1. We do not sell or share your data for advertising. If that ever changes, we will say so here before it happens.

The page count described in section 1 uses no cookie, includes no account data, and does not run in the signed-in app. To credit a signup to the page where a visit started, the site keeps that page, the referring site, the campaign tags of that page, the time that page opened, and whether that page started the visit in your browser's session storage. Your browser deletes it when the tab closes. It is not a cookie. The site sends it only when you open a sign-in or signup link or submit the email form on the home page. The page count sends only whether the page is the first page of the visit.

We do not store your card number or your card security code. The payment processor receives them to charge the subscription, and it does not keep the security code after it authorizes the charge. We keep the payment records described in section 1.

3. How we use it

We use the data above to:

4. Where it lives

IBC Tool's application servers and primary database are hosted in the United States. Uploaded documents are kept in object storage with our cloud storage provider. Customer data is encrypted at rest. Connections between you and IBC Tool, and between IBC Tool and our service providers, use TLS in transit.

5. Service providers

We rely on third-party service providers to host the application, store uploaded documents, charge the subscription, report errors in the app, and parse the contents of annual statements you upload (so cash value, available loan amount, and similar fields can be populated automatically rather than re-typed). The payment processor receives the card data described in section 1. It uses that data to charge the subscription, to issue a refund, and to handle a payment dispute. Each provider receives only the data needed for its role and is bound by contractual confidentiality and security obligations. We do not permit service providers to use your data to train AI models or for any purpose other than delivering their service to us. If you'd like a current list of named sub-processors, email privacy@ibctool.app and we will share it. We will give notice on this page before any change that materially affects how your data is handled.

Integrations that you authorize yourself are described under "Third-party connections you authorize" in section 1.

6. Cookies and local storage

IBC Tool keeps this state in your browser:

We do not use advertising cookies or analytics cookies, and none of this state tracks you on other sites. We do not show a cookie banner today; if we add anything that would require one, we will add the banner first.

7. Children

IBC Tool is for users 18 and older. We do not knowingly collect personal information from minors; if you believe one has provided us information, contact us and we will delete it.

8. Your rights

You can ask us to:

You can delete your account at any time from the settings page in the app. The flow asks you to type your email address, and then to enter a 6-digit code we email you. We then remove the account data our Data Retention Policy says we delete. That policy lists the records we keep, including payment records. We do not keep your card number. For access, correction, export, or anything else listed here, email privacy@ibctool.app and we will respond within thirty days. You can also export your data yourself: Download your data on the settings page gives you a ZIP file of your records as spreadsheet (CSV) files, plus the documents you uploaded. Depending on where you live, additional rights may apply under the laws of your jurisdiction (for example, the GDPR in the EU/UK or the CCPA/CPRA in California). We honor those rights regardless of where your account is hosted, and we honor Global Privacy Control signals from your browser as a request to opt out of any sale or sharing of personal information.

9. Security

We do not store a password. You sign in with a 6-digit code we email you, or with a passkey on your device. We store only a hash of that code. The code expires in 10 minutes, and we never store the code itself. Third-party access tokens you authorize are encrypted in our database, with a key that is kept separately from the database. All traffic to and from IBC Tool is served over TLS. No system is perfectly secure, but we treat your insurance and financial data as data we'd want a serious provider to treat ours.

If we discover a security incident that affects your account data, we will notify you within thirty days of confirming the incident — sooner where law requires — and report to the relevant authorities on the timelines those authorities require.

10. Retention

While your account is active, we retain the data needed to operate it. When you delete your account, we remove your data from our primary database immediately and from object storage within minutes via a background purge job, with the exceptions described in our Data Retention Policy. Backups age out on the schedule maintained by our hosting providers.

11. Changes to this policy

We may update this policy as the product changes. Material changes will be communicated by email and in-app notice. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the service after a material change means you accept the updated policy.

12. Contact

Questions, complaints, or requests under section 8 can go to privacy@ibctool.app.