Privacy Policy

How to contact us

For privacy, cookie, or account-data questions, contact support@tr-entic.com. This repo currently exposes verified support contact details but not a full corporate postal notice, so that legal identity block should be completed before production publication if additional statutory information is required in your jurisdiction.

What this site stores by default

• Supabase authentication cookies are used when you sign in so the dashboard session can remain active and secure.
• A consent record is stored after you make a privacy choice so the site can remember whether optional categories remain disabled or have been enabled by you.
• Theme preference is stored locally only if you explicitly switch between light and dark mode and allow preference storage through the consent manager.

Optional categories and your choices

The consent manager separates strictly necessary technologies from optional categories for preferences, analytics, and marketing. Those optional categories remain disabled until you actively opt in.

• Necessary: authentication, security, consent persistence, and core navigation.
• Preferences: convenience choices such as theme state or other non-essential personalization.
• Analytics: traffic and feature measurement tools.
• Marketing: advertising, attribution, or retargeting tools.

In the current implementation of this web app, analytics and marketing categories are disabled by default and no active analytics or advertising integration is loaded unless a future release adds one and you opt in first.

Withdrawing or changing consent

You can reopen Cookie settings from the shared site footer at any time. Rejecting optional technologies is intentionally as easy as accepting them, and your consent decision is renewed on a rolling basis rather than treated as permanent.

Current consent policy version: 2026-03-13.

Consent audit and retention

When you save a consent decision, the site records a versioned audit receipt containing the decision identifier, timestamp, selected categories, and limited request context such as page path, browser language, and timezone. This receipt helps demonstrate when and how consent was captured.

Consent decisions are retained locally so your preferences can be respected across visits and re-requested after the configured renewal window. Audit receipts include the policy version, decision identifier, timestamp, and selected categories. Development environments may temporarily persist audit receipts to a local server file when cloud credentials are not configured.