SovAIHub

Privacy

How SovAIHub handles your information.

This notice explains information processed through accounts, page views, contact and newsletter forms, browser-local tools, hosting, and email delivery.

Information

What may be processed

  • Academy learning records: when you save progress or submit scenario practice, lesson identifiers, self-reported completion status, latest practice scores, up to five recent saved attempts per module, and save timestamps are stored privately with your account. These are learning records, not certification or access entitlements.
  • Accounts: email address, name, email-verification status, and authentication/session records managed by Supabase Auth. Passwords are processed by Supabase Auth; SovAIHub does not store them in application tables.
  • Contact requests: name, email address, optional company, role, timeline, solution interest, and message.
  • Newsletter requests: email address and any limited context submitted with the request.
  • Technical records: hosting and email providers may process security, delivery, and service logs such as IP address, timestamps, and request metadata.
  • Page-view analytics, when enabled: page URL without query parameters or fragments, site section, timestamp, browser timezone and language, referring website hostname, browser/device information, and your application user ID if signed in. IP address and approximate country, region, or city are recorded only when supplied by a configured trusted hosting proxy. These records are stored in Supabase.
  • Browser-local settings: theme and some interactive-tool answers may be stored in your browser. SovAIHub does not receive those values unless you choose to submit related information. Account sessions use essential cookies; signing in does not sync your local tool drafts.
  • Deployment projects: when you choose Save project, your project name, purpose, GPU label, memory and model planning settings are stored with your application user ID in Supabase. Other users cannot access your projects through the application. You can delete a saved project from your workspace. Do not put passwords, access tokens or private documents in these fields. If you use the optional description assistant, only the text you explicitly submit is sent to Groq; you can complete the form without it.

Purpose

Why it is used

  • Resume Academy lessons across devices and show your latest scenario practice results when you use these features.
  • Create and maintain your account, verify your email, provide sign-in and password recovery, and control access to account information. Creating an account does not subscribe you to marketing emails.
  • Respond to questions, architecture-review requests, and product or implementation enquiries.
  • Record and manage newsletter requests and send requested SovAIHub updates.
  • Operate, secure, troubleshoot, and prevent abuse of the website and email forms.
  • Save and export private deployment planning projects when you choose to use the workspace.
  • Understand which pages and features are used and improve the website through first-party page-view analytics when enabled.
  • Maintain necessary business correspondence and records.

Providers and Retention

Where information goes and how long it remains

Service providers

Supabase provides account authentication and stores account, session, Academy learning, deployment-project, application-access, and enabled page-view analytics records. Authentication emails are delivered through the email provider configured for Supabase Auth. Form submissions are sent through Resend, an email-delivery provider, to SovAIHub-controlled email recipients. If you explicitly use the optional deployment assistant, Groq processes the description you submit to produce form suggestions. The hosting provider may process normal request and security logs. These providers may process information in countries different from yours under their own infrastructure and contractual safeguards.

Retention

Account information is retained while your account is active and can be requested for deletion using the contact details below. Saved deployment projects remain until you delete them or your account is deleted. Academy learning records remain until you clear them or your account is deleted. Contact correspondence is kept only as long as reasonably needed to answer the request, maintain necessary records, resolve disputes, or meet applicable obligations. Newsletter contact information is kept until you withdraw the request or it is no longer needed. Provider logs follow the applicable provider retention settings. When page-view analytics is enabled, its daily cleanup is configured to remove records older than 90 days. Protected backups follow their separate retention settings.

Choices

Your controls

SovAIHub does not sell personal information and does not use advertising cookies. Its page-view analytics does not create tracking cookies or persistent visitor identifiers. Collection is skipped when your browser sends Do Not Track or Global Privacy Control. Essential authentication cookies continue to support sign-in. Page-view analytics does not collect precise device location.

You may ask to access, correct, or delete information you submitted, or withdraw a newsletter request, by emailing contact@sovaihub.com. Applicable rights and exceptions depend on your location and the circumstances.

External links, GitHub repositories, and third-party services have their own privacy practices. Review their notices before submitting information to them.

Contact

Questions about this notice

Email contact@sovaihub.com or use the contact page. This notice is updated 22 October 2026 and may be updated when the website or its service providers change.