Cookie & local-storage notice

AutoDeploy currently uses storage needed to deliver a feature you explicitly request or to keep the service secure. Examples include the sign-in session, OAuth flow state, the selected workspace, and interface preferences such as theme and accessibility settings. Some interface preferences are stored in your browser's local storage rather than cookies.

Authentication/session storage is used to identify your signed-in session and protect account access. Workspace selection is a convenience only; the server independently checks your membership and permissions on every protected request. OAuth state storage helps protect sign-in and account-linking flows against request forgery.

The current website code does not intentionally load advertising trackers, behavioural advertising cookies, or optional analytics tags. We do not ask you to consent to a tracker that is not present. If optional storage or tracking is introduced later, it must be blocked until valid consent is collected where required, and refusing it must not prevent use of features that do not need it.

You can remove cookies and local storage through your browser settings. Doing so may sign you out, reset your selected workspace, or restore interface preferences to their defaults. Removing a browser value does not delete information held in AutoDeploy's service databases; use the account data controls or contact hello@smilekisan.com to exercise data-protection rights.

Storage duration depends on the feature. Some values last only for a browser session; the selected workspace can persist for up to one year. Identity-provider sign-in and payment flows may involve their own domains and storage, governed by those providers' notices. This page is not a claim that all infrastructure logs, provider-side storage, or server-side retention has been independently audited.

For questions about storage or privacy, contact hello@smilekisan.com.