Cookie & Local Storage Policy
What AppScreenie saves in your browser, why it is needed, and how you can remove it.
Effective
1. The short version
AppScreenie does not use advertising cookies, cross-site tracking, or marketing tags. It uses first-party browser storage so the editor can keep projects you ask it to save and so the site can remember your analytics choice. Optional cookieless Vercel Web Analytics runs only after you choose Allow analytics.
This policy covers cookies and similar browser technologies, including IndexedDB. For the wider handling of personal information, read the Privacy Policy.
2. Cookies and similar storage
A cookie is a small value a website asks a browser to retain. Browser storage technologies such as IndexedDB can keep larger or more structured information.
AppScreenie's production editor and consent control rely on the similar technologies described below rather than cookies. The information stays in the browser profile unless a feature explicitly sends a network request.
3. Storage AppScreenie uses
| Technology | Purpose and contents | Typical duration | When used |
|---|---|---|---|
| IndexedDB: local projects | Keeps project documents, imported screenshots and images, custom fonts, previews, and revisions on your device. | Until you delete a project, clear site data, or the browser removes it. | When you create, edit, or save a project. |
| Local storage: appscreenie.analytics-consent.v1 | Remembers whether you chose Allow analytics or No thanks. It contains only the current choice, not a user or advertising ID. | Until you change the choice, clear site data, or the browser removes it. | After you make an analytics choice. |
These stores are first-party and are not read across unrelated websites. Local project storage is not used for analytics. The consent preference only decides whether the separate analytics client may load.
4. Third-party connections
If you choose Allow analytics, the browser loads Vercel's cookieless Web Analytics client and sends minimized page-view events to Vercel. The client does not load before you allow it. AppScreenie removes query strings and page fragments before events are sent. See the Privacy Policy analytics section for the data, purpose, provider, and retention details.
When the editor loads the Google Fonts catalog or a font used in a project, the browser requests resources directly from Google. That is a network connection, not an AppScreenie analytics tag. Google handles the request under its own Privacy Policy.
The Support and Support activity pages connect directly to Supabase over HTTPS and, while the live feed is visible, a Realtime WebSocket. Supabase receives ordinary connection information such as an IP address, browser details, request time, and requested resource. This is a network connection for the public support feed, not an AppScreenie analytics tag, and it does not require an AppScreenie cookie. Supabase handles that connection under its Privacy Policy.
The optional Ko-fi support link is a normal external link; AppScreenie does not embed Ko-fi tracking or payment scripts. If you follow the link, Ko-fi may use its own cookies and similar technologies under its Privacy Policy.
5. Analytics consent
On a first visit, AppScreenie asks whether you want to allow optional analytics. Allow analytics and No thanks are equally available. Until you allow it, and after you reject it, AppScreenie does not mount or request the analytics client. Rejecting analytics does not affect the editor or any other feature.
You can reopen the same choice through Privacy choices in the footer or directly in the editor. A changed choice applies to future analytics collection. Clearing the consent preference causes AppScreenie to ask again on a later visit. Clearing all site data can also remove local projects, so export or back up anything you want to keep first.
6. Your browser controls
You can inspect or clear AppScreenie site data using your browser's privacy or site-settings controls. Most browsers also let you block storage entirely. The exact menu varies by browser.
Before clearing or blocking storage, keep in mind that:
- clearing site data can permanently remove local projects;
- blocking IndexedDB can prevent project saving or editing; and
- private-browsing profiles may remove local projects when the private session closes.
Export any final images and portable project backups you want to keep before clearing AppScreenie storage.
To change only analytics, use Privacy choices in the footer or editor instead of clearing all site data.
7. Changes and contact
This policy will be updated when the storage list or its purposes materially change. The effective date at the top identifies the current version.
Questions can be sent to hello@appscreenie.com.