Not signed in
Viewing events, raid bosses, egg pools, and field research needs nothing from you — no account, no cookie, no signup. Our hosting provider's web server keeps standard access logs (the kind almost every website generates) for security and abuse prevention. We don't use these logs for tracking or analytics.
You can check into an in-person meetup by scanning its QR code, and upload Pokédex screenshots for it, without creating an account. Doing so only asks for a display name to show on that meetup's scoreboard — nothing else is stored, no cookie is set, and each submission is independent. We don't remember you between visits, so there's nothing to link a later visit back to an earlier one, and nothing to delete on request beyond the individual submission itself.
If you use a "catch tracker" or trainer-stat scanning feature, the screenshot you upload is stored in our file storage and read by an OCR (text recognition) program that runs on our own server — we never send your screenshots to a third-party AI or image-recognition service.
We keep the screenshot so your submission can be shown and verified on a scoreboard. Uploading a replacement screenshot for the same submission deletes the old file. You can ask us to delete a submission and its screenshots at any time.
Registering is optional, but it's the only way your screenshot uploads and meetup check-ins are remembered across visits and devices. An account stores your name, email address, and a securely hashed password (we never store or see your password in plain text), plus your trainer settings (display name, team, timezone, community, leaderboard visibility). If you enable two-factor authentication or a passkey, we store what's needed to verify it — never the credential itself.
While you're logged in, we keep a server-side session record containing your IP address and browser identifier, purely so the login stays secure. These expire automatically after a period of inactivity.
We only email you for account essentials: verifying your address or resetting your password. No newsletters, no marketing. These emails are delivered through a transactional email provider (such as Postmark, Resend, or AWS SES) acting purely as our mail carrier — they don't use your address for anything of their own.
We use as few cookies as possible, and none for advertising or tracking:
No analytics or tracking scripts, no ad networks, no social-media widgets, no fingerprinting, and no selling or sharing your data with advertisers. Fonts and other assets are hosted by us directly, not pulled from Google or another third party that could log your visit.
If you opt in to leaderboard visibility, your display name, team, and scores are visible to members of your community. Community and site admins can see and moderate data within their scope to keep leaderboards fair. We don't share your personal data with anyone outside of the service providers mentioned above.
Pokémon GO event, raid, and research data is public game content and is kept indefinitely as a historical record — that's the point of the site. Your personal data (accounts, screenshots) is kept only as long as you keep using the related feature, and is deleted on request. An anonymous submission has no persistent identity to delete on request beyond the submission itself.
Wherever you're located, you can ask to see, correct, export, or delete the personal data we hold about you, or to opt out of a feature entirely. Since this is a one-person hobby project rather than a company with a dedicated privacy team, the easiest way to reach me is directly — see Contact below — and I'll sort it out as quickly as I can.
SilphBoard isn't directed at children, and we don't knowingly collect personal data from young children. If you believe a child has created an account, please contact us and we'll remove it.
If this policy changes in a meaningful way, we'll update the date at the top of this page.
Questions, requests, or concerns about your data? Email audun@drup.no.