Understand the browser storage behind local projects

Cookies and project storage are different mechanisms

A cookie is a small value a website can store in a browser and send with later requests to the corresponding service. IndexedDB is a browser database that can hold larger structured data locally, including project settings and images. Local storage is another browser storage mechanism used for smaller values. These mechanisms are related to the same site but are not interchangeable. Calling all saved data “cookies” can hide an important distinction: an editable screenshot project needs more information than a typical preference cookie contains.

What the editor stores locally

The current project workflow uses local browser storage, including IndexedDB, to preserve editable design work for the same browser profile. That may include imported image data, panel content, element positions, colors, and selected output settings. The purpose is to let you continue a project without requiring an account or a server-side design library. The browser controls storage availability and limits. Private browsing, restricted storage settings, browser cleanup, or a full device can prevent persistence or shorten how long work remains available.

What is not installed in the application

The current application does not install advertising trackers, a visitor analytics package, an account-login service, or a remote project-upload endpoint. This statement describes the application code, not every behavior a future host may introduce. A hosting provider, security layer, or content delivery network can log requests and may have its own technical storage behavior. The owner must inspect the deployed site and amend this policy if those services add cookies or scripts. Browser-local design work does not mean the website is completely anonymous.

How to remove site data

Use the site-data or privacy controls in your browser to inspect and clear storage for appscreenshot.online. The exact labels differ between browsers. Clearing the site’s storage can remove locally saved projects, so download a project backup first if you need to retain editable work. Removing site data does not remove exported images, ZIP archives, or backups already downloaded to your device. Those are ordinary files that you manage through your file system and any backup service you use.

If you later import a downloaded project backup, its editable content can be written back into the browser’s project storage. Deleting a local project and retaining a backup are therefore separate choices. Consider both when removing sensitive work.

External links and email

Opening an official documentation link takes you to another website, where that provider’s storage practices apply. The contact email link opens your own mail application; it does not submit a web form to AppScreenshot.online. Any message you send is handled by your email provider and the receiving email provider. Avoid sending private project assets when a written explanation or sanitized example would be enough. Downloads do not automatically send your finished images to the contact address.

Review whenever the implementation changes

New analytics, accounts, collaboration, remote assets, or embedded third-party widgets could change storage and consent needs. Before adding such features, the owner should document the actual mechanisms, purposes, providers, and any required controls. This draft does not declare that all cookie rules are inapplicable or that one consent approach fits every jurisdiction. It gives a practical description of the current local-project architecture and the checks needed to make the final published disclosure accurate.