Privacy Policy & Local Browser Data
This page explains exactly what the current Sprite Wiki codebase stores in your browser, what stays client-side when you export or share, and what server or analytics details remain pending final launch configuration.
Local Browser State vs. Web Server Requests
Checklist tracking, JSON backups, and snapshot decoding run directly in your browser without a user account or remote Sprite Wiki collection database. At the same time, visiting any public website generates standard HTTP requests to the server or CDN delivering the pages — so a public hosting provider (once selected and deployed) may log technical request metadata such as IP address, browser user-agent, requested path, and timestamp under its own infrastructure policies.
Sprite Wiki is an independent Fortnite fan reference tool and is not affiliated with Epic Games.
Browser localStorage Collection Records
- Storage key: sprite-atlas-ag-v1 (kept consistent across all language views so switching languages preserves saved entries).
- Stored payload: A compact JSON object storing schema version (v: 1), your variant status map (1 = Collected, 2 = Mastered), and an ISO updatedAt timestamp generated on write.
- Not collected or stored: No Epic Games account ID, Fortnite credentials, name, email, or payment information is ever read or stored here.
- Removing local data: Clear browser site storage for this origin at any time, or clear individual selections in the checklist.
JSON Backups & Restore
Clicking Download backup exports a file named sprite-wiki-backup-YYYY-MM-DD.json (internal format sprite-atlas-backup, version 1) containing your current status map, patch label, data version, and export timestamp. The file is generated locally via a browser Blob URL — nothing is uploaded or emailed to any server.
When using Restore, your browser reads the selected JSON file locally, previews known vs. unknown IDs before writing anything, and lets you merge higher statuses or replace current records.
No Account Sync or Cloud Backup
Sprite Wiki does not provide user logins, Epic Games OAuth connections, cross-browser account syncing, or server-side cloud backups. Switching devices, clearing browser storage, or using private browsing will start an empty local checklist unless you import an exported JSON backup file.
External Services, Assets & Analytics Status
- Analytics & ad scripts: Currently none installed. The codebase contains no Google Analytics, Plausible, Umami, advertising pixels, or remote event telemetry calls.
- Fonts & artwork delivery: Sprite icons are served locally from this site’s static assets under /sprites/... rather than hotlinking external image servers at runtime. Typography (Chakra Petch and Inter) uses Next.js build-time local font bundling so browsers request fonts from this site’s own origin instead of calling fonts.googleapis.com.
- Outbound reference links: Source citations link out to third-party community trackers and reference sites (such as Fortnite.GG, SpriteChecklist.org, SpriteLocker.com, and Royal Arena). Leaving Sprite Wiki via external links is governed by each destination site’s privacy policy.
Contacting the Site Maintainer
For privacy questions, asset attribution/removal notices, or content corrections, email contact@spritewiki.com (also listed on the Corrections & Contact guide).
Because Sprite Wiki has no user accounts, login system, or remote checklist database, there are no server-side user collection records for us to look up or erase — clearing saved progress happens directly inside your own browser as described above.
Pending Hosting & Analytics Details
Planned Hosting & Server Access-Log Retention
Public hosting on Vercel is not active on this local review build; production CDN edge logging and server access-log retention periods will be confirmed upon public launch.
Optional Future Aggregate Analytics
No analytics or tag-manager scripts are loaded in this codebase. If aggregate measurement is enabled after public launch, it is planned around high-level navigation/action events only (never transmitting user collection maps, backup JSON files, or share #hash payloads).