What the toys keep, why, and how to make them forget.
updated · 29 Jun 2026
title block⌖
doc no.
PNDR-PRIV
rev.
2026.06.29
jurisdiction
TX · US
sheet
1 of 2
medium
woff2 · edge
drawn by
Anmol Saxena
ponderance.dev and the apps and services it hosts (each a "service", listed in the Services
section below) are operated by Anmol Saxena, an individual based in Texas, USA
("we", "us", "our"). This policy covers the portfolio's contact form and every listed service.
Exactly what each one collects is spelled out in the Services section; the clauses below are the
rules common to all of them. Questions or privacy requests:
anmol@ponderance.dev.
Jump to clause ▾01
§01
What we collect
In short — only what each toy needs; the per-service list below is the specifics.
Across the services we may collect: identity when you sign in (for a service that uses a third-party login like Google or Spotify, the provider shares basic profile fields such as your name, email, profile picture, and an account identifier — never a password; for a service with its own accounts, the username and password you set, stored hashed by that app); content you create or upload (for example artwork you save, or photos you add), kept on your device until you choose to save it; contact-form submissions (the name, email, and message you send, delivered to us by email through Resend); and technical metadata — your IP address and basic request data — for security, abuse-prevention, and rate-limiting, plus a Cloudflare Turnstile bot-check where a service uses one. Site traffic is measured with Cloudflare Web Analytics, which is cookieless. The only cookie we set is a strictly-necessary one that keeps you signed in; there are no advertising or cross-site tracking cookies. See the Services section for exactly what each service collects.
02
§02
How we use it
In short — to run the services and keep bots out. No ads, no selling, no AI training.
We use this information to authenticate you, to store and show the content you save, to display anything you choose to make public (and at its shareable link), to reply to inquiries you send, and to keep the services working and safe — preventing abuse and spam, enforcing limits, debugging, and protecting against fraud or attack. We do not sell your personal information or use it for advertising. Where a service uses a third-party sign-in, our use of the data that provider shares with us follows that provider's developer and data policies — set out for each live provider in the Services section below (today: the Google API Services User Data Policy, including its Limited Use requirements; and, when the Audio Visualizer goes live, the Spotify Developer Policy).
03
§03
Who sees it
In short — a few infrastructure providers, plus anyone you publish to on purpose.
We rely on a small set of processors to run the services; the ones in use are listed (with their role and privacy policy) in the Services section — today Google (sign-in), Cloudflare (hosting, database, file storage, CDN/tunnel, bot-protection, and analytics), and Resend (contact-form email), with Spotify joining when the Audio Visualizer launches. They handle data on our behalf under their own terms. We may disclose information if required by law. When you mark something public, that content — along with the display name and avatar on your profile — is visible to anyone by design.
04
§04
Your choices and rights
In short — change or delete your content, or your whole account, whenever you like.
You can change the visibility of, or delete, content you've saved at any time, and you can delete your account for a given service, which removes your profile and the content tied to it there. Depending on where you live (for example the EEA, the UK, or California), you may have rights to access, correct, export, or erase your personal data and to object to certain processing. To exercise any of these, email anmol@ponderance.dev.
05
§05
Data retention
In short — kept while your account exists, gone shortly after you delete it.
Your account and saved content are kept until you delete them or close your account for that service. After deletion they're removed from active storage promptly, though cached or backup copies may linger briefly. Contact-form emails are kept only as long as needed to handle your inquiry. Security logs are short-lived.
06
§06
Children
In short — not for young kids.
The services aren't directed to children under 13 (or the minimum age in your country, such as 16 in parts of the EEA), and they shouldn't use them or sign in.
07
§07
Security
In short — encrypted in transit; passwords are never ours to lose when you sign in with a provider; still, nothing is bulletproof.
For services with third-party sign-in, a provider handles your login and we never see or store a password; for services with their own accounts, passwords are stored hashed by that app. Sessions can be revoked. Traffic is encrypted in transit and served through Cloudflare's edge. No method of storage or transmission is completely secure, so we can't promise absolute security.
08
§08
Where it's processed
In short — served globally, so processed abroad.
The services run on Cloudflare's global network (and, for self-hosted services, on our own hardware reached through it), so your information may be processed in countries other than your own.
09
§09
Changes
In short — if this changes, the date at the top changes too.
We may update this policy. The "last updated" date will change, and significant changes will be noted on the page.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements: we do not use Google user data to serve advertising, to determine creditworthiness or for lending; we do not sell it to data brokers or others; and we do not use it to develop, train, or improve generalized AI or machine-learning models. Read the policy →
Turn a photo of a paper calendar into device calendar events — on the web and as an iOS app.
how you sign in
Google sign-in (OAuth)
what it collects
account: your Google or Apple sign-in — the provider shares basic profile fields such as name, email, and an account identifier; no password reaches us
Plus-tier scans: the calendar image you upload is sent to Google Gemini for text recognition (OCR) and is deleted from our servers within 24 hours
extracted events (titles, dates, and times) are never stored on our servers — they live only on your device or in your browser
payments: subscription billing is handled by Lemon Squeezy on the web and by Apple In-App Purchase on iOS; we receive only the confirmation and status needed to unlock Plus, never your card details
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements: we do not use Google user data to serve advertising, to determine creditworthiness or for lending; we do not sell it to data brokers or others; and we do not use it to develop, train, or improve generalized AI or machine-learning models. Read the policy →
An iOS & macOS dashboard for the open-source “glance” aggregator you run on your own server — cards, widgets, Live Activities, and container start/stop/restart. No account with us.
how you sign in
No account needed
what it collects
Nothing reaches us — Homelab Glance has no server of ours, no analytics, and no tracking.
On your device only: the server address and access/control tokens you enter (kept in the system Keychain) and your card/widget layout, shared with the app’s widgets through a private App Group.
The app connects only to the glance server you run; that traffic goes straight to your own machine.
who processes it
No third parties — this app has no backend of ours; it talks only to the server you run.
Runs entirely on your device. The server address and tokens you enter live in the system Keychain and are shared with the app’s widgets through a private App Group; none of it is sent to us.
A widget-first iOS & macOS app that controls the lights on your own Home Assistant server. No account with us.
how you sign in
No account needed
what it collects
Nothing reaches us — FoldLight has no server of ours, no analytics, and no tracking.
On your device only: the Home Assistant address and access token you enter (token kept in the system Keychain) and your widget/preset preferences, shared with the app’s widgets through a private App Group.
The app connects only to the Home Assistant server you point it at; that traffic goes straight to your own machine.
who processes it
No third parties — this app has no backend of ours; it talks only to the server you run.
Runs entirely on your device. The server address and tokens you enter live in the system Keychain and are shared with the app’s widgets through a private App Group; none of it is sent to us.
Runs on Anmol's own hardware; Cloudflare only carries traffic (tunnel / CDN).
Face-grouping and search features are computed locally on that server and are never sent to any third party.
Text recognition (OCR) on Plus-tier calendar images for Calque; images are deleted within 24 hours and are not used to train models on the paid API. Privacy policy · Data policy
