Bumalik sa Login

Cookie Policy

Document Version: 1.1 | Effective: October 13, 2026 | Last Updated: October 13, 2026

1. What are Cookies?

Cookies are small text files stored on your computer or mobile device when you access websites or online platforms. They are widely used to make websites work, or work more efficiently, as well as to provide reporting information and store preferences.

The current Owner Web login uses localStorage for both access and refresh tokens and selected preferences, requesting the backend's long-lived session mode. The backend also supports an HttpOnly refresh cookie (Secure in production, SameSite=Strict) for clients using its non-mobile login mode; this does not make the current Owner portal's localStorage tokens HttpOnly. LocalStorage and cookies are different technologies; browser storage controls apply separately.

2. How We Use Cookies

We use browser storage and related session information for these purposes:

A. Essential Browser Storage

A signed access token in localStorage authorizes API calls. The current Owner portal refresh token is also stored in localStorage. Cookie-based refresh is supported for other login modes. Logout and token revocation affect session access.

B. Security & Session Metadata

Request and session metadata help protect accounts, enforce authorization, and investigate suspicious access.

C. Preference & Settings Persistence

Browser storage retains supported preferences, branch selection and device-session context. Preferences can persist until cleared or replaced; a token's expiry does not automatically erase all stored values.

D. Performance & Logging

Server request, security and audit logs support service operation. Optional Sentry error/performance integration exists but depends on deployment configuration; no claim of active production analytics or guaranteed exclusion of all personal data is made here.

3. Specific Storage Technologies Implemented

Storage KeyTypePurposeLifespan
accessTokenLocalStorageSigned JWT authentication for API calls, with server authorization checks.15-minute token validity; stored value may remain until replaced or cleared.
refreshTokenLocalStorage in current Owner portal; HttpOnly cookie in supported non-mobile modeSession renewal with server-side rotation and revocation.Current Owner portal requests 180-day refresh validity; non-mobile cookie mode uses 7 days. Rotation, expiry and revocation apply; stored values may remain until cleared.
Interface preferences and branch/device contextLocalStorageSupported interface settings and session context; keys vary by feature.Persistent

4. Managing Your Cookies

You can choose to accept or block cookies:

  • Browser Controls: Most web browsers allow managing cookie behaviors through settings (usually located in "Privacy and Security" preferences).
  • Consequences of clearing or blocking storage: Removing authentication tokens signs you out; blocking required browser storage may prevent the portal from maintaining a session or preferences.

5. Policy Updates

We may update this Cookie Policy from time to time to match additions to our security mechanisms or browser parameters. Any revisions will be indicated by the version details at the top of this page.

6. Contact Information

If you have any questions or require support regarding our use of cookies, please email us at:
Email: admin@octechph.com — OCTECH SOFTWARE DEVELOPMENT SERVICES, Namnama, Tuding, Itogon, Benguet 2604, Philippines; +63 960 293 2001; https://tindahango.com.