Privacy Policy

This policy applies to information RELAVANZ processes for its own account, product, security, support, and billing operations. When RELAVANZ processes personal data solely on behalf of a business customer, that customer may be the controller or business and RELAVANZ may act as its processor or service provider. Our Data Processing Addendum addresses that processor role.

Third-party services you choose to connect have their own terms and privacy practices. A connected provider is not automatically a RELAVANZ subprocessor merely because you authorize RELAVANZ to exchange data with it.

• Account information such as email address, authentication identifiers, Workspace membership, role, invitations, notification preferences, and settings.
• Site information such as domains, Site names, URLs, configuration choices, implementation instructions, and customer-confirmed business facts.
• Customer Content such as prompts, questions, objectives, instructions, article inputs, review-request recipient information, and other material you submit to a RELAVANZ feature.
• Support and legal communications, including information you send to hello@relavanz.com.
• Billing contact, subscription, invoice, and payment-status information for paid purchases. Payment card details are handled by Stripe rather than stored by RELAVANZ.

When you submit a public domain or add a Site, RELAVANZ may fetch publicly available website pages, HTTP responses, redirects, robots directives, sitemaps, metadata, structured data, images/media metadata, internal links, performance observations, and other technical evidence needed to understand the Site.

RELAVANZ may retain crawl records, snapshots, findings, recommendations, approvals, implementation evidence, validation results, monitoring history, regression events, and related provenance so the product can distinguish what was observed, what changed, what was applied, and what was later verified.

Public teaser scans and public report links may be retained separately from authenticated Workspace records. If you later adopt a public scan into a Workspace, RELAVANZ may associate eligible scan evidence with that Workspace without treating the public scan itself as write authorization.

When you connect a provider, RELAVANZ processes authorization metadata, provider account/resource identifiers, granted scopes or permissions, connection health, resource bindings, imported observations, and audit history. Access and refresh credentials are handled server-side through protected secret-storage mechanisms, including Supabase Vault for supported OAuth credentials, rather than exposed through customer-facing read models.

• Google Search Console: RELAVANZ requests https://www.googleapis.com/auth/webmasters.readonly ("view Search Console data for your verified sites") and uses it for read-only Search Console evidence.
• Google Business Profile: RELAVANZ may request https://www.googleapis.com/auth/business.manage for authorized profile/location discovery and capability-gated management workflows. RELAVANZ uses this only for listings the customer owns or is authorized to manage.
• Google Merchant: RELAVANZ may request https://www.googleapis.com/auth/content. Connecting Google is separate from binding a Merchant account/data source and separate from authorizing a write operation.
• Shopify: current baseline scopes are read_products, read_content, read_online_store_navigation, and read_markets. Supported write workflows can progressively request write_products, write_content, write_online_store_pages, and write_online_store_navigation. RELAVANZ also handles Shopify's required privacy webhooks for customer-data requests/redaction and shop redaction.
• GitHub: RELAVANZ uses a GitHub App installation. It uses metadata read access for installation/repository discovery, Contents read or write as needed for repository reads/approved branch changes, Pull Requests write for PR creation, and can read Checks/Deployments when those permissions are granted. Current signed webhook processing handles installation, installation-repositories, pull-request, and deployment-status events. Source changes use dedicated branch/commit/pull-request workflows rather than direct protected-base-branch writes.
• WordPress / Custom CMS: capabilities vary by the connected Site, connector tier, credential, and detected supported API. WordPress Basic uses a dedicated application password rather than asking for a normal WordPress administrator password; Full Connector uses a site-bound signed connector secret.

Google Business Profile API policiesGoogle Merchant API termsShopify app privacy requirementsGitHub App permissions

You can disconnect Search Console and other supported integrations in RELAVANZ. Disconnecting stops future use of that connection and revokes or invalidates stored credentials where the integration supports it. Historical evidence already imported into a Workspace may remain as product history subject to the retention and deletion rules below.

RELAVANZ's use and transfer of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including applicable Limited Use requirements. Google user data is used to provide or improve customer-facing features the customer requests and authorizes. RELAVANZ does not sell Google user data or use it for advertising.

Google API Services User Data Policy

RELAVANZ uses artificial intelligence for features such as Ask RELAVANZ and the Article Engine. Depending on the feature and your plan, RELAVANZ may send prompts, Site evidence, objectives, article context, or other feature-specific inputs to an AI model provider to generate analysis or content.

Current production Agent and Article Engine model execution uses OpenAI. Separate audit and SEO/GEO analysis paths also use Google Gemini for supported classification, summarization, content, competitor, authority, and live-presence analysis. Some Free or snapshot-mode Agent responses can be generated only from saved RELAVANZ evidence without starting new external research or full model/tool execution.

RELAVANZ does not currently operate a general-purpose model-training pipeline that trains a RELAVANZ foundation model on customer content. Provider data handling depends on the applicable API agreement and configuration. We do not make a broader "no training" promise about a provider unless that promise is supported by the current contract and configuration.

See our AI Terms for additional limitations and agentic-action rules.

• Local SEO may process business/location identity, keywords, grid points, Google Business Profile observations, Local AI visibility observations, listing-directory state, review observations, and campaign configuration.
• Review-request features may process recipient contact information, delivery/suppression state, and opt-out information for the purpose of sending honest review invitations configured by the customer.
• Commerce may process Shopify store/catalog/product/variant/market information and Google Merchant account, data-source, product, and issue observations.
• Backlinks Intelligence may process domains, source/target URLs, competitor domains selected for research, provider observations, opportunity evidence, and later verification/monitoring results.

RELAVANZ may process IP address and request metadata, authentication/session data, security and abuse signals, application logs, error and diagnostic information, worker/job telemetry, provider-call metadata, cost/usage telemetry, and email delivery state such as sent, delivered, delayed, bounced, complained, or failed status needed to operate, secure, meter, and troubleshoot the Services.

RELAVANZ uses browser storage or cookies where needed for authentication, security, OAuth return state, and product preferences. Our current application audit did not identify advertising pixels or cross-context behavioral advertising SDKs. If non-essential tracking is introduced, RELAVANZ will re-evaluate the need for additional notice and consent controls before relying on that technology where required.

• Provide, operate, secure, troubleshoot, and improve the Services.
• Create and administer accounts, Workspaces, members, Sites, permissions, and connected integrations.
• Crawl and analyze authorized Sites; prepare recommendations; support controlled implementation; validate changes; and monitor later regressions.
• Provide AI, Article, Local, Commerce, Backlinks, performance, and integration functionality.
• Measure plan usage and enforce entitlements, capacity, abuse controls, and safety boundaries.
• Process supported paid subscriptions and capacity purchases through Stripe.
• Send service, security, account, support, and other communications required to operate the Services.
• Comply with law, enforce agreements, resolve disputes, and protect RELAVANZ, customers, and others.

Where a legal basis is required, RELAVANZ may rely on performance of a contract, legitimate interests such as security/support/reliability, consent for optional processing where required, and compliance with legal obligations. The applicable basis depends on the feature, relationship, and jurisdiction.

RELAVANZ may disclose information to infrastructure, database, hosting, email, AI, billing, research, security, and other service providers that support the Services; to customer-directed connected platforms when you authorize an integration or action; to professional advisers; in a corporate transaction subject to appropriate safeguards; or when required by law or reasonably necessary to protect rights, safety, or service integrity.

See our Subprocessor List for the current core service-provider inventory.

RELAVANZ does not currently sell personal information for money and does not use Google user data for advertising. Our current application audit did not identify cross-context behavioral advertising technology in the customer application. If practices change in a way that constitutes "sale," "sharing," or targeted advertising under applicable law, RELAVANZ will update notices and provide required choices.

RELAVANZ retains information for as long as reasonably necessary for the feature and relationship in which it was collected, to preserve customer-requested Site/work history, maintain security and audit records, resolve disputes, enforce agreements, satisfy billing/tax obligations, and comply with law.

• Account and Workspace records generally remain while the account or Workspace is active and for a reasonable period afterward where needed for legitimate operational or legal purposes.
• Site evidence and lifecycle history may be retained to preserve recommendations, implementation, verification, and monitoring history. Archiving a Site is not a deletion request.
• OAuth/access credentials are revoked, invalidated, or rendered unavailable on disconnect where the provider and integration support it; historical imported evidence may remain.
• Billing and transaction metadata may be retained as needed for accounting, tax, fraud prevention, and dispute purposes.
• Backups and security logs are deleted or overwritten according to operational cycles rather than necessarily at the same moment as primary records.

Where an exact retention period is not fixed by the product architecture, RELAVANZ uses the criteria above rather than promising immediate deletion that the system cannot perform.

RELAVANZ uses administrative and technical safeguards designed to reduce unauthorized access, disclosure, alteration, or misuse. Current architecture includes tenant scoping, row-level security, server-side secret handling, capability checks, signed internal requests, and separation between customer-facing application data and privileged service credentials.

No service can guarantee absolute security. RELAVANZ does not claim a certification, penetration-test schedule, or "bank-grade" security standard unless that claim is separately verified and published.

RELAVANZ and its service providers may process information in the United States and other locations where they operate. Where applicable law requires a transfer safeguard, RELAVANZ will use an available lawful mechanism appropriate to its role and provider relationship.

Depending on where you live and how RELAVANZ processes your information, you may have rights to request access, correction, deletion, portability, restriction or objection, withdrawal of consent, or other rights provided by law. You may also have a right to appeal certain denied requests or use an authorized agent where applicable.

See Privacy Rights & Data Deletion for request instructions and important distinctions between account deletion, Site Archive, and integration disconnect.

RELAVANZ provides Workspace-level preferences for supported optional notification classes such as weekly digests, recommendation reminders, successful-validation notices, Article-ready notices, and informational Local or Commerce updates. Where an unsubscribe mechanism is legally required for optional marketing, RELAVANZ will provide one.

RELAVANZ may record delivery, bounce, and complaint events and suppress an address after a bounce, complaint, or manual suppression so we do not continue sending messages that should not be delivered. Service, security, support, account, billing, and other mandatory operational communications may still be sent when necessary to provide or protect the Services.

RELAVANZ is a website and business-software service and is not directed to children under 13. We do not knowingly collect personal information from children in circumstances where verifiable parental consent is legally required. If you believe a child has provided personal information improperly, contact us.

We may update this policy when the Services, providers, data practices, or legal requirements change. We will update the "Last updated" date and provide additional notice when required. RELAVANZ also uses internal Legal Health monitoring to flag material product changes for legal review; the monitor does not automatically rewrite or publish legal text.

Privacy questions and requests may be sent to hello@relavanz.com. RELAVANZ currently operates online and does not publish a physical business address.