What we collect, where it lives, who can see it.

Last updated 9 May 2026

QuikSnap is a personal finance dashboard run on a single server, used by a small invited group. This policy is short on purpose. We don't sell anything to anyone. We don't run ads. We don't track you across the internet. The only data we keep is what's needed to render your dashboard.

Who runs QuikSnap

QuikSnap is operated by Evan Briggs as a personal project. There is no company, no team, no investors. If you have a question about your data, email evan.briggs91@gmail.com.

What we collect

• Your Google account info. When you sign in, Google tells us your email address, name, and profile picture URL. That's the standard profile email scope. We use the email to check that you're on the invited list. The name and picture are only displayed back to you in the app.
• Your linked bank data. When you click Connect a bank, Plaid opens its own login window and (after you authenticate at your bank) hands QuikSnap an access token. We use that token to fetch your account names, balances, and transactions from Plaid. We store these in a local SQLite database on the QuikSnap server.
• Web-server access logs. The server records each request — your IP address, the URL, a timestamp, and the response size. Standard web logs, kept for short periods for security and debugging.

What we don't collect

• No analytics, no tracking pixels, no third-party scripts on the site.
• No advertising data. We don't run ads and we don't sell anything.
• No location beyond what your IP address discloses.
• No microphone, camera, contacts, calendar, or device data.

Where the data lives

Everything is on a single Google Compute Engine virtual machine in us-central1-a. Bank tokens, accounts, and transactions live in /var/lib/quiksnap/quiksnap.db (a SQLite file). Disk-level encryption at rest is provided by Google Cloud by default. No data is mirrored to other servers, third-party analytics, or backup services.

Who can see your data

• You — through the QuikSnap dashboard, after signing in with your invited Google account.
• The operator of the server (Evan Briggs), who has administrative access to the VM.
• Plaid Inc. — when you link a bank, Plaid is the party that talks to your bank on QuikSnap's behalf. Plaid's own privacy policy governs what Plaid does with the data they process: plaid.com/legal.
• Google — only sees the OAuth sign-in handshake (the standard "Sign in with Google" flow). They don't see your bank data.
• Google Cloud Platform — hosts the VM. Standard cloud-provider relationship.
• Let's Encrypt — issues the TLS certificate so your browser trusts the connection. They never see your data; they only know the hostname.

That's the entire list. We do not share data with anyone else.

How long we keep it

• Bank tokens and transactions. Kept as long as you have that bank linked. Click Disconnect on the Connect page and the access token, all transactions, and the sync cursor for that bank are deleted from the database immediately.
• Google account info. Cached in your sign-in cookie for up to 7 days. Sign out, or wait for the cookie to expire, and there's nothing left in your browser.
• Server logs. Rotated on the standard server schedule.

Your rights

• Disconnect any linked bank from the Connect page — your data for that bank is deleted on the spot.
• Email evan.briggs91@gmail.com and ask for a full export of your data, or full deletion. The reply will be a human one.
• Stop using QuikSnap any time. There's no subscription, nothing to cancel.

Children

QuikSnap is not intended for anyone under 13. If you are under 13, please don't use it.

Security

The site is HTTPS-only with a Let's Encrypt certificate. Sign-in is gated by Google OAuth against an explicit allowlist — accounts that aren't on the list are turned away after Google authentication. The QuikSnap API runs only on the loopback interface; it cannot be reached from the internet without first passing through the auth gate. Bank access tokens are stored on disk and never sent to the browser.

No system is perfectly secure. If you find a vulnerability, please email evan.briggs91@gmail.com directly rather than posting it publicly.

Changes to this policy

If this policy changes, the date at the top of the page will change too. Material changes (new third parties, new data categories) will be flagged on the dashboard the next time you sign in.

Contact

Questions, requests, complaints, or just hello — evan.briggs91@gmail.com.