Governance & Data Sovereignty

Privacy Policy

Last Updated: March 2026 · Effective Immediately

1. Our Data Sovereignty Philosophy

At Zynqora AI, we believe user data should belong to the user. We design our technology platform from the ground up to minimize telemetry, avoid gratuitous tracking, and run computing workloads locally in your browser whenever mathematically feasible.

2. Browser Utilities & Cloud Saving

The Word & Character Counter, Case Converter & Text Cleaner, JSON Formatter & Validator, and Developer Utilities Suite process your input in your browser. When you are signed in, successful tool inputs and results are also sent to Zynqora and saved to your private cloud history so you can access them in My Workspace. Saving requires an authenticated account; guests can continue to use the tools without cloud history. AI-powered tools send the information needed to generate a result to their configured AI providers.

3. Account Data & Authenticated Services

When you voluntarily register for an account, we store:

  • Your email address and hashed authentication credentials managed securely by Supabase Auth.
  • Your optional profile display name and avatar URL.
  • Your saved tool inputs and outputs, prompt history, authenticated conversation messages, article bookmarks, favorites, and uploaded-file metadata.
  • Private uploaded files in access-controlled storage. File content is not stored in database rows.

Private history is protected by account-scoped authorization and PostgreSQL Row Level Security. Allowlisted administrators can view aggregate tool execution and storage metrics, plus limited account-level operational information. The metrics do not expose private prompts, conversation content, generated results, or file contents.

4. AI Assistant Model Processing

When you submit prompts to the Zynqora AI Assistant, your query is routed through our server to configured foundation model providers (such as Groq, Google Gemini, or OpenAI) to synthesize a response. API keys remain server-side and are not exposed to browser clients. Authenticated conversations are stored in your account; anonymous chats are not permanently stored in the conversation database.

5. Cookies & Local Storage

We use strictly necessary session cookies required for authentication and persistent login state. Browser local storage also preserves your visual theme, language, and analytics-consent preference. If a cloud save fails, the result may be held temporarily in session storage so you can retry without running the tool again. Analytics are optional: page views are sent to Supabase only after you accept in the analytics prompt. You can reopen the privacy settings control to change your choice.

6. Optional Cloud Analytics & Newsletter

If you accept optional analytics, the site stores the page path and visit timestamp in Supabase. When you are signed in, the visit is associated with your account so allowlisted administrators can review account-level page-view counts. We do not send IP addresses or browser user-agent strings to this analytics table. Newsletter addresses are stored in Supabase only after you submit the signup form and consent.

7. Account Deletion & Right to be Forgotten

You can permanently delete your account and associated profile, conversations, bookmarks, saved tool history, and private uploaded files from Account Settings. Deletion is irreversible. Security, legal, or operational records that are retained separately are not used to restore deleted account content.