How Stackr handles data

See what Stackr stores and what you share when you sign in, deploy a project, or turn on a public status link.

Your account and session

When you sign in with Grasany ID, Stackr saves a display name and a hashed identifier so you can return to your workspace. A session cookie keeps you signed in. Stackr stores a hash of that session token and revokes it when you sign out.

The installable workspace caches a public offline page. Workspace data loads when you reconnect.

Deployments and connections

Stackr stores your project settings and retained releases for preview, publication, and rollback. Publishing makes a release available at its site address under your project's access settings. Keep secrets out of files you publish.

Stackr encrypts saved Git access tokens and uses them to access repositories with the permissions you grant. Disconnect a Git provider in Stackr to remove its saved token.

When you enable an outbound release webhook, Stackr sends the selected event’s type, time and identifiers to the destination you verified. Delivery history records attempts and HTTP status codes for up to seven days after completion. Stackr discards receiver response bodies.

Traffic and public sharing

Stackr counts hosted requests and response bytes to show usage. Sampled project logs include the request method, response status, latency, bytes, time, request ID, and deployment ID where available. The logs cover up to 24 hours. Hourly project analytics cover seven days.

When a project owner enables Web Analytics, Stackr stores daily totals for eligible public static page views. Only the page paths the owner selects are shown separately. All other paths are grouped together. Referrals are grouped by source type. These aggregates exclude visitor identifiers, URL query strings, and full referrer URLs.

Anyone with an enabled workspace status link can see deployed app names and addresses, workspace usage totals, recorded charges, and published incidents. Disable or replace the link in the workspace to revoke access through the old link.

Support and privacy requests

When ticket submissions are open, you and authorized support operators can read your in-app support conversations. Resolved conversations are eligible for deletion after 90 days.

For access, correction, export, or deletion requests, use the privacy contact published by Grasany and include Stackr as the product name. Keep passwords, API keys, and payment credentials out of your request. Grasany privacy and request contact