Cookie Policy
Effective Date: 4 August 2026
Version 2.0 - TeamThink Solutions (Pty) Ltd t/a Devv Technology
1. What Cookies Are
Cookies and similar browser storage technologies are small records stored on your device when you use a website or web application. They help a service remember your session, security state, preferences, and product context.
2. How Devv Uses Cookies
Devv primarily uses first-party cookies and local browser storage for authentication, session management, workspace selection, product preferences, installation prompts, and security. These are necessary for Devv Hub and the native apps to keep you signed in, route you to the right workspace, prevent cross-organisation access, and preserve basic settings.
3. Main Cookie and Storage Categories
Purpose: Maintain your Devv ID session, refresh secure access tokens, and authenticate requests.
Typical names: Names may include sb-* authentication cookies or equivalent Supabase session cookies.
Duration: Session or persistent duration depending on the authentication token and browser settings.
Domain: Usually scoped to devv.co.za or a Devv subdomain so cross-app sign-in can work.
Purpose: Remember the active organisation, workspace, product context, onboarding step, or app handoff state.
Examples: Active organisation cookies, app launch parameters, invite context, plan selection, or setup progress.
Duration: Usually session-based or retained until replaced, cleared, or no longer needed.
Purpose: Remember interface choices such as dismissed guides, install prompts, selected display options, or local product preferences.
Storage: May use cookies, localStorage, IndexedDB, or app storage depending on the product.
Duration: Varies by feature and browser settings.
Purpose: Support installed app experiences, local drafts, cached app shells, pending offline actions, and device-specific state where a product supports it.
Examples: Devv Inspect drafts, uStock offline/POS state, service worker caches, and local app queues.
Control: Clearing site/app data may remove offline drafts, cached state, and app preferences.
4. Cross-App Sign-In
Devv is designed around one Devv ID across multiple products. Where technically possible and secure, authentication cookies may be scoped so devv.co.za and Devv subdomains can recognise the same signed-in user. This reduces duplicate login prompts and helps Hub route you to the correct app, workspace, or partner portal.
5. Analytics, Marketing, and Third-Party Cookies
Devv does not require third-party advertising cookies for core product access. If Devv introduces analytics, marketing, conversion tracking, or similar optional cookies in future public marketing surfaces, we will update this policy and, where required, provide an appropriate consent or preference mechanism. Payment providers, embedded services, or third-party links may have their own cookies and policies when you interact with them.
6. Managing Cookies and Site Data
You can manage or clear cookies and site data in your browser. Clearing cookies may sign you out, reset your active workspace, remove local preferences, and delete unsynced local drafts or offline queues.
- Chrome: Settings - Privacy and security - Third-party cookies / Site data
- Firefox: Settings - Privacy and Security - Cookies and Site Data
- Safari: Settings - Privacy - Manage Website Data
- Edge: Settings - Cookies and site permissions
7. Changes to this Policy
Devv may update this Cookie Policy when products, authentication systems, installed app features, offline functionality, or third-party services change. Material changes will be communicated through the platform, email, or another reasonable channel.
8. Contact
For questions about cookies, browser storage, or privacy, contact legal@teamthink.co.za.
Last Updated: April 13, 2026