Privacy Policy

Last updated: 30 July 2026.

This policy covers teamsnelgrove.com and the personal software projects developed under it, including the duckdb-stripe DuckDB extension.

Summary

This is a personal website. It sets no cookies, keeps no sessions, runs no analytics or advertising scripts, and has no user accounts. The software projects published here are written for my own use, against my own data. There are no other users whose data I collect, and I sell or share nothing with anyone.

Website

What is collected

The web server records a standard access log for each request: IP address, date and time, requested URL, HTTP status, referrer, and user agent string. That is the only collection that happens.

What is not collected

• No cookies, local storage, or any other client-side state.
• No sessions, logins, or accounts.
• No analytics, tag managers, advertising, or tracking pixels.
• No third-party fonts, scripts, or embeds.
• No forms — nothing is submitted to this site.

How log data is used

Access logs are used only to operate the site: diagnosing errors, spotting abuse or attack traffic, and looking at aggregate request counts. Logs are not used to build profiles of individuals and are not combined with any other data source. They are retained for a short operational window and then discarded.

Projects

Software published under this site is written for my own use, against my own data. Some of it integrates with hosted services that require a published privacy policy URL as a condition of access — Stripe Financial Connections, for example, requires one before a Financial Connections application can be enabled, because the API is designed for products that handle other people’s financial data. Those requirements apply regardless of scale, so each such project gets its own section below describing exactly what it touches.

Nothing described here is offered as a service. None of it has end users other than me.

duckdb-stripe

duckdb-stripe is a DuckDB extension that pulls personal bank transactions through Stripe Financial Connections into a local DuckDB database.

Whose data

Mine only. The extension is a personal tool that links my own bank accounts so I can query my own transactions. It is not offered as a service, has no end users other than me, and is not used to access anyone else’s accounts.

What data is involved

Data returned by Stripe Financial Connections for accounts I have personally linked and consented to: account identifiers and metadata, balances, and transaction records (amount, currency, description, status, and transaction dates).

How it is handled

• Bank credentials are never seen or handled by me or by the extension. Account linking happens entirely inside Stripe’s hosted flow, and Stripe holds the bank relationship.
• Stripe is the system of record for customers, linked accounts, and refresh subscriptions. The extension holds no local state beyond API credentials stored in DuckDB’s secret mechanism and whatever tables I choose to build.
• Retrieved transaction data is stored in a local DuckDB database file on my own machine, on encrypted storage, and is not published, hosted, or exposed publicly.
• All communication with Stripe is over HTTPS.
• Data is retained as long as it is useful to me and deleted at my discretion. Linked accounts can be disconnected at any time via Stripe.

Sharing

None. Financial data is not sold, shared, transferred, or disclosed to any third party. The only third party involved is Stripe itself, acting as the data provider under the Stripe Privacy Policy and the Financial Connections End User Terms.

If any of this changes

If any project here is opened up to other people’s financial data, this policy will be revised beforehand to describe the consent, use, retention, and deletion practices that apply, and affected users will be told what changes.

Source code

This site and its projects are open source. The site is built as static HTML by Zine with no server-side application code.

Changes to this policy

Changes are published on this page with an updated date at the top.

Contact

Questions about this policy, or about data handled by anything described here: snelgrove2@gmail.com.