Privacy Policy

This policy covers scottlapaglia.com and the services run on its subdomains — currently Meal Prepper, at meals.scottlapaglia.com and recipe.scottlapaglia.com. I run these myself as personal projects. There is no company behind them, no advertising, and nothing here is sold or shared with data brokers.

1. This website

The pages you're reading now are static files. They set no cookies, run no analytics, embed no tracking pixels, and load no third-party scripts or fonts. Nothing about your visit is collected by me.

The site is hosted on GitHub Pages, so GitHub's servers handle the request and keep their own access logs (including your IP address) under GitHub's privacy statement. I have no access to those logs.

2. Meal Prepper

Meal Prepper is private: it requires Google sign-in and your email address has to be on an allowlist I maintain by hand. There is no public sign-up.

What sign-in gives me

Signing in uses Google Identity Services. Google verifies who you are and returns a signed token; from that token the service stores your email address and the date your account was created, and nothing else. It never sees your Google password, and it does not request access to your contacts, Drive, calendar, or any other Google data.

Each sign-in creates a session record holding a hash of your session token — never the token itself — plus when it was issued, when it expires, and when it was revoked, if it was.

What you put into it

The content side is simply what you choose to save:

• Recipes you import. The source URL, and what the service extracted from that page: title, description, listed author, image URL, yield, prep and cook times, ingredient lines, and instruction steps. It also keeps the raw structured-data block it read off the page, so a bad import can be diagnosed without re-fetching the site. These are stored on my server, in a PostgreSQL database, scoped to your account.
• Everything the planner records. Your week's plan, grocery lists, shopping trips, purchases, cook logs, pantry contents, and any receipt photos you add. Today this data lives in your browser's own storage, not on my server — which means a different device, a different browser, or cleared site data starts over from empty. As these features move server-side, this policy will be updated and re-dated before that happens.

Importing a recipe makes my server fetch the URL you gave it. That request reaches the recipe site from my server, not from your browser, so the site sees my server's address rather than yours.

Logs

The server writes ordinary operational logs — request paths, status codes, timings, errors — which include the IP address the request came from. The logging is written to redact credentials, so session tokens and keys are not recorded. Logs exist to keep the thing running and debug it, nothing else.

3. Who else sees it

• Google — only for the sign-in step, and Google's own privacy policy governs what Google does with it. Nothing you store in Meal Prepper is sent to Google.
• DigitalOcean — the server runs on a droplet I administer, so they are the infrastructure provider holding the disk.
• Let's Encrypt — issues the TLS certificates that encrypt the connection.

That's the whole list. No analytics provider, no advertising network, no CRM, no error-reporting service. I will not sell your data, and I will not hand it to anyone else except where the law actually compels me to.

4. Cookies and local storage

This website sets no cookies. Meal Prepper sets no tracking cookies either: your session token is held in your browser's sessionStorage, and the planner's data in browser storage, both of which stay on your device. Google's sign-in flow may set its own cookies on Google's domains during the handshake.

5. How long it's kept

• Sessions expire 30 days after they're issued. Signing out revokes yours immediately, as does removing your email from the allowlist.
• Your account and your recipes are kept until you ask me to delete them.
• Database backups run nightly, are kept for 30 days, and are stored off the server. A deletion propagates out of backups within that window.
• Anything held in your browser is gone the moment you clear the site's data.

6. Your choices

Email me and I'll do it by hand — there's no self-service screen for this yet:

• a copy of everything stored for your account,
• a correction to anything that's wrong,
• deletion of your account and its data, or
• removal from the allowlist, ending your access entirely.

I'll confirm when it's done. If you're in a jurisdiction with statutory data rights — the UK or EU under the GDPR, California under the CCPA, or similar — treat the address below as the way to exercise them.

7. Security

Connections are HTTPS-only with HSTS. Session tokens are stored hashed, never in plain text. The service refuses to start without its authentication configuration rather than quietly falling back to being open, access is allowlisted, and credentials are redacted from logs.

That said, this is a personal project run by one person. I'm not going to claim it's unbreakable, and you shouldn't store anything in it that would hurt you to lose or to have exposed. If you find a security problem, please email me — I'd much rather hear it from you.

8. Children

These services aren't directed at children under 13, and because access is invitation-only I don't knowingly create accounts for them. If one exists, tell me and I'll delete it.

9. Changes to this policy

If what the services collect changes, this page changes with it and the date at the top moves. For anything materially different — particularly the planner's data moving from your browser onto my server — I'll say so here rather than let the change happen silently.

10. Contact

Scott LaPaglia — salapag89@gmail.com