Introduction
This Cookie Policy explains how OPERASCH (OPERASCH), operated by ScalMint (Accra, Ghana), uses cookies and similar technologies on the OPERASCH platform. It forms part of and should be read alongside our Privacy Policy.
Cookies are small text files placed on your device (computer, tablet, or mobile phone) when you visit a website. They allow the website to recognise your device and remember information about your visit, such as your login state, your preferred language, or the items in a form you are completing.
This policy applies to cookies and similar technologies (including local storage and service worker caching) set by OPERASCH when you browse our website and use our platform. It does not cover cookies set by third parties on their own websites, which are governed by their respective privacy policies (see Third-Party Cookies below).
How We Use Cookies
OPERASCH uses cookies and similar technologies for a limited set of purposes that are essential to providing the service and protecting your account. We do not use cookies for advertising, cross-site tracking, or building behavioural advertising profiles.
Specifically, we use cookies to:
- Authenticate users. When you sign in, cookies are used to maintain your authenticated session so that you do not have to re-enter your credentials on every page. Authentication is provided by Clerk, our identity provider.
- Protect your account. Cookies help defend against cross-site request forgery (CSRF) attacks, session hijacking, and other fraudulent activity, so that only you can access your account.
- Remember your preferences. We store your selected theme (light or dark), language, and accessibility settings so the platform behaves the way you expect each time you return.
- Provide Progressive Web App (PWA) functionality. A service worker caches application assets and data so that OPERASCH remains usable during limited or no connectivity, which is common in many parts of Ghana. Cookies and local storage support this offline capability.
Consistent with the openness principle of Act 843, we have set out above, in plain terms, the specific purposes for which each category of cookie is used. We do not use cookies for any purpose beyond those described here without first updating this policy.
Types of Cookies We Use
The table below summarises the categories of cookies and similar technologies used by OPERASCH. Further detail on each category is provided in the sections that follow.
| Cookie Name / Purpose | Type | Duration | Description |
|---|---|---|---|
| Authentication cookies (set by Clerk) | Essential | Session | Used to verify your identity and maintain your logged-in session after you sign in. These cookies are deleted when you close your browser or sign out. |
| Security cookies | Essential | Session | Used for CSRF protection, fraud prevention, and to detect unauthorised access attempts. Required for the platform to function securely. |
| Preference cookies | Essential | Persistent | Remember your chosen theme (light/dark), language, and accessibility settings across sessions. These remain on your device until they expire or you delete them. |
| PWA / Service Worker cookies | Essential | Persistent | Support offline functionality and asset caching so the platform remains usable during limited connectivity. Stored locally on your device. |
| Performance / Analytics cookies | Non-essential | Not currently used | OPERASCH does not currently use analytics or performance cookies. If we introduce them in future, we will update this policy and, where required by Act 843, seek your consent before they are set. |
Third-Party Cookies
Some cookies are set by trusted third-party service providers thatScalMint engages to operate OPERASCH. These third parties are data processors acting on our instructions, and they have their own privacy and cookie policies that govern how they handle data.
Clerk (Authentication)
Authentication for OPERASCH is managed by Clerk (clerk.com). When you sign in, Clerk may set essential cookies on the clerk.accounts.dev and clerk.com domains (and, in a production deployment, on a custom domain configured for your tenant) to establish and maintain your session, issue authentication tokens, and protect against unauthorised access.
These cookies are necessary for the login process and cannot be disabled if you wish to use OPERASCH. Clerk's privacy practices are described in the Clerk Privacy Policy.
Cloudinary (Image Delivery)
Images used across OPERASCH (such as school logos, user avatars, and document previews) are delivered through Cloudinary from the res.cloudinary.com domain. Cloudinary may set technical cookies required to serve and cache images efficiently. These are limited to what is necessary for image delivery and do not track your browsing behaviour across other sites. See the Cloudinary Privacy Policy for details.
Essential vs Non-Essential Cookies
Under Act 843 and good data protection practice, a distinction is drawn between cookies that are strictly necessary for a service you have requested, and cookies that are not strictly necessary (which generally require your consent).
Essential cookies
The authentication cookies, security cookies, preference cookies, and PWA/service worker cookies described in this policy are strictly necessary for the delivery of the service you have requested from OPERASCH. Without them, you would not be able to sign in securely, your preferences would not persist, and the offline PWA functionality would not work. Because they are essential, these cookies are set automatically and cannot be disabled within OPERASCH itself.
Non-essential cookies
OPERASCH does not currently set any non-essential cookies, such as analytics, advertising, or social media cookies. Should we introduce any non-essential cookies in the future, we will update this policy and obtain your consent before setting them, in accordance with the openness and consent principles of Act 843.
Managing Cookies
You have the right to control cookies on your device. Most modern browsers allow you to refuse cookies, delete existing cookies, or alert you when a cookie is being set. You can usually find these controls under the "Privacy" or "Cookies" section of your browser's settings.
Guidance for popular browsers is available from the providers below:
You can generally:
- Block all cookies. Your browser can be set to refuse all cookies. You may also block cookies from specific domains.
- Delete existing cookies. You can clear cookies already stored on your device through your browser's history or privacy settings.
- Use private/incognito browsing. Most browsers offer a private mode that limits cookie storage to the duration of that session.
If you disable a cookie that OPERASCH relies on, we will not be able to guarantee the full functionality of the service for you. This does not affect your right to access and use other features of your browser.
Updates to This Policy
ScalMint may update this Cookie Policy from time to time to reflect changes in the cookies we use, improvements to OPERASCH, changes in applicable law (including any amendments to or regulations under Act 843), or for operational, legal, or regulatory reasons.
When we make material changes, we will update the "Last updated" date shown at the top of this page and, where appropriate, provide a more prominent notice (for example, on the OPERASCH website or through your account). We encourage you to review this policy periodically.
Continued use of OPERASCH after a change to this Cookie Policy takes effect constitutes your acceptance of the updated policy, to the extent permitted by Act 843 and other applicable law.
Contact Us
If you have any questions, concerns, or requests regarding this Cookie Policy or the way OPERASCH uses cookies and similar technologies, you may contact our Data Protection team:
- Data Protection / Privacy: mwinisaviour87@gmail.com
- General Support: mwinisaviour87@gmail.com
- Operator: ScalMint, Accra, Ghana
- Website: https://smartsos.cloud
You may also write to us at the address above. We aim to respond to all legitimate enquiries within a reasonable timeframe and in accordance with our obligations under the Data Protection Act, 2012 (Act 843) of Ghana.