Vendor / Subprocessor Register

This register lists the current processors and subprocessors used by the Zarova website and related operational workflows. It is intended to be practical and current, not an enterprise procurement register.

Zarova does not add services to this page unless they are used in the product or business workflow. Public social platforms linked from the website are not listed here unless Zarova sends personal data to them as a processor.

Service Category: Authentication, database, storage, and backend application services.

Purpose: Authentication, user accounts, profiles, roles, dashboards, database records, Supabase Storage, profile avatars, application files, CMS media, legal acceptance records, and related backend workflows.

Data processed: Account identifiers, email addresses, authentication/session data, profile fields, legal acceptance records, application data, uploaded files, profile avatars, CMS records, storage object metadata, and operational logs needed to provide and secure the service.

Primary Processing Region:Supabase is a United States-based provider. Zarova data is stored in the Supabase project region selected for the project, with provider operations and subprocessors potentially operating internationally according to Supabase's published terms.

Service Category: Hosting, edge delivery, Website Analytics, and performance monitoring.

Purpose: Website hosting, deployments, edge delivery, server-rendered pages, route handling, performance monitoring, consent-gated Vercel Analytics, and Speed Insights.

Data processed: Website request metadata, IP-derived location signals, browser and device information, page and route performance data, deployment logs, error signals, and analytics events where analytics consent has been granted.

Primary Processing Region: Vercel is a United States-based provider and operates a global hosting and edge network. Processing may occur in the United States and other regions used to deliver and secure the website.

Zarova has not listed payment processors, email marketing platforms, enterprise support tools, or advertising vendors here because they are not part of the current website implementation described by the live codebase.

If Zarova later adds additional processors, such as a transactional email service, payment processor, support desk, or production logging platform, this register should be updated before or alongside that launch.

This register may be updated as Zarova's infrastructure changes. Material processor changes should be reviewed against the Privacy Policy, Cookie Policy, Data Retention Policy, and internal incident response procedures.

For questions about this document or Zarova's legal and governance policies, visit the Contact page or email contact@zarova.one.