What this release uses
Gramsify uses an essential first-party session cookie named gramsify.sid. It supports sign-in, session security, form protection and temporary status messages. The default session is rolling and expires after up to seven days without renewal; sign-out removes the current browser’s session cookie. Session access can also end because of account restrictions, a password change or other security action.
The current application does not include advertising pixels, third-party analytics scripts or marketing cookies. Its aggregate server-side counters do not use a cross-site tracking cookie. An operator who adds new optional tracking must update this notice and provide the choice required by applicable law before activating it.
Installed-app storage
When supported, the service worker stores a versioned cache of static interface assets, icons, fonts and the generic offline screen. This helps the app display essential interface files when the connection fails. The cache is limited to a fixed asset list; personalised pages, applications, messages, uploads and API responses are not saved in that offline cache.
Installation prompts and app-update state are handled by the browser and the current page. The application does not store unsent collaboration forms for later automatic delivery. Browser history and other browser-managed information remain subject to your browser settings.
External services
Opening a social profile, external reference or payment link takes you to a separate service that may use its own cookies and storage. The current platform links to those services rather than embedding their tracking widgets. Review their notices when you leave Gramsify.
Your choices
You may clear cookies and site storage in your browser, sign out, uninstall the web app or block cookies. Blocking the essential session cookie may prevent sign-in and form submission. Clearing site storage removes local app assets and may sign you out; it does not by itself delete your server account or collaboration records.
Because this release uses essential sessions and interface storage only, it does not present a misleading “accept all” marketing-cookie banner. If optional cookies are added later, any required consent controls must be implemented before they load. Contact Support with questions about storage or use the Account Deletion Policy for server-side data requests.