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 currently use production cookies, advertising cookies, analytics cookies, cross-site tracking, or marketing tags. It does use first-party browser storage so the editor can keep the projects you ask it to save.
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 relies 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. |
These technologies support features the user requests. They are not read across unrelated websites and are not used to identify visitors for advertising or analytics.
4. Third-party connections
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. Why there is no cookie banner
AppScreenie currently uses no non-essential tracking, advertising, or analytics storage. Its browser storage is limited to providing requested editor and save functions. On that basis, AppScreenie does not currently present a tracking-consent banner.
AppScreenie will review this position and request consent before using a future cookie or similar technology where applicable law requires it. This includes reviewing any future analytics, advertising, personalization, or embedded third-party tool before launch.
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.
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.