Kraymus · Waitlist & private preview
Cookie Policy
This policy covers cookies and similar browser storage for Kraymus at kraymus.ai. Browser storage can have privacy implications even when it is not a traditional cookie.
Current public website
Our own waitlist code does not set advertising or analytics cookies, include tracking pixels, or load a third-party audience analytics tool. It can read a previously saved appearance preference. The public legal pages are static documents with no tracking script. Hosting and security infrastructure can still receive technical requests and keep logs; this is explained in the Privacy Policy. This inventory describes application code and does not claim that every third-party infrastructure service uses no cookies.
Browser storage in the private app
| Storage | Purpose | Lifetime and control |
|---|---|---|
| Supabase sign-in session, normally sb-<project>-auth-token in local storage | Keeps the authorized account signed in and supplies credentials to the backend. | Persistent until sign-out, expiry/refresh, or browser removal. Blocking it can prevent sign-in. |
| OAuth connection state and result in session storage | Matches an account-connection response to the request and shows its result. | Removed when processed; otherwise lasts for the browser tab/session, subject to browser session restoration. |
| Reply request identifier in session storage | Prevents accidental duplicate sends during a retry. | Cleared after the action; otherwise lasts for the tab/session. |
| Theme, layout, workspace and navigation preferences in local storage | Remembers choices you make in the interface. | Persistent until replaced or removed in your browser; there is no automatic expiry in the current code. |
| Saved CRM filters in local storage | Keeps views you choose to save on this browser. | Until you remove the view or clear site data. |
Your controls
You can sign out, change appearance settings, remove saved views, or block or clear storage using your browser’s privacy and site-data settings. Clearing local storage can sign you out and remove preferences; it does not delete your server-side Kraymus account, business records or posts on another platform. Use data-deletion controls for those records.
When you open a social-provider authorization screen or a linked third-party site, its cookies and privacy policy apply there. Kraymus’s public landing does not currently embed a social feed or third-party tutorial video; adding embeds can introduce third-party storage and requires a new review.
If optional tracking is introduced
No optional advertising or audience analytics tracker is currently offered by our waitlist code, so there is no optional tracker to accept. Before enabling such technology, we will update this inventory and provide a consent and withdrawal mechanism where required. We will not treat scrolling, clicking a normal link or a preselected choice as consent. Necessary service storage and optional tracking must remain distinguishable.
Questions: privacy@kraymus.ai. We will review this policy before full launch or adding new storage purposes.
Where consent is required, non-essential storage or access must wait for an affirmative choice. Rejecting or withdrawing optional consent must be as easy as giving it; scrolling, silence or accepting general Terms is not that consent. The notice must explain purposes, providers and duration and provide accessible controls. This is a condition for adding optional tracking, not a claim that a new consent manager is already deployed.