Privacy Rights & Data Deletion
This page explains how to make privacy and deletion requests and how different RELAVANZ product actions affect data.
1. Submit a request
RELAVANZ currently accepts privacy and account-deletion requests at hello@relavanz.com. Include the email address associated with your account and enough context for us to identify the relevant Workspace or Site without sending passwords, OAuth tokens, API keys, or other secrets.
2. Rights that may be available
Depending on where you live, your relationship with RELAVANZ, and the data involved, applicable law may give you rights to:
- request access to personal information;
- request correction of inaccurate information;
- request deletion;
- receive a portable copy where required;
- restrict or object to certain processing;
- withdraw consent for processing based on consent;
- opt out of certain sale, sharing, targeted advertising, or profiling if RELAVANZ later engages in a practice to which such rights apply;
- appeal a denied request where applicable; and
- use an authorized agent where applicable law permits.
3. Identity and authority verification
RELAVANZ may ask for information reasonably necessary to verify identity, account ownership, Workspace authority, or an authorized-agent request. We will not ask you to email passwords, access tokens, or other secret credentials.
4. Account deletion
RELAVANZ does not currently rely on a public self-service delete button as the sole deletion path. You may request deletion using the contact method above. We will verify the request, determine which records are controlled by RELAVANZ and which belong to a customer Workspace or third-party provider, and process the request consistent with applicable law and our retention obligations.
Deleting an account may end access to one or more Workspaces. If another organization controls data associated with your membership, RELAVANZ may need to preserve organization-controlled records or direct you to that organization for certain requests.
5. Site Archive versus deletion
Site Archive is a product-state change used to stop or limit new work while preserving Site identity, evidence, recommendations, implementation history, validation, monitoring, and other records. Archiving is not a privacy deletion request.
If you want RELAVANZ-held personal information associated with a Site deleted, submit a privacy request and identify the Site and Workspace involved.
6. Integration disconnect
Disconnecting Google Search Console, Google Merchant, Shopify, GitHub, WordPress, Custom CMS, or another supported connection stops future RELAVANZ use of that connection and revokes, invalidates, or renders unavailable stored credentials where supported.
Disconnecting does not necessarily delete historical observations, audit records, recommendations, or evidence already stored in RELAVANZ. Those records follow the applicable Workspace retention and deletion process.
7. Shopify privacy requests
Where RELAVANZ operates a Shopify app subject to Shopify's mandatory privacy webhooks, RELAVANZ handles the applicable data request, customer redaction, and shop redaction events through the Shopify integration. Those provider-driven requests are distinct from a general RELAVANZ account deletion request.
8. Public scan and report data
If you submitted a public scan or report without an account and want RELAVANZ to review deletion of associated personal information, include the domain, report context, and email address you used, if any. RELAVANZ may retain limited security, abuse-prevention, or audit records after removing customer-facing data where permitted by law.
9. Billing records
When paid billing is enabled, some Stripe and RELAVANZ billing records may need to be retained for accounting, tax, fraud-prevention, dispute, or legal reasons even after account deletion. RELAVANZ is not designed to store full payment-card numbers.
10. AI and generated content
A deletion request can include prompts, objectives, AI messages, Article outputs, or related account-linked records held by RELAVANZ where applicable. Provider-side treatment of data previously sent to a model provider depends on the applicable provider contract, configuration, and legal requirements.
11. Exceptions and retention
RELAVANZ may retain limited information after a deletion request when necessary or permitted for legal obligations, security and fraud prevention, billing/tax records, dispute resolution, legal claims, backups, enforcement of agreements, or protection of rights and service integrity.
12. Timing and appeals
RELAVANZ responds within the timeframe required by applicable law. If additional time is permitted and necessary, we will provide required notice. Where applicable law provides a right to appeal a denied privacy request, you may appeal by replying to the decision or contacting hello@relavanz.com.
13. Non-discrimination
RELAVANZ will not unlawfully discriminate against you for exercising an applicable privacy right.
14. Related information
See the Privacy Policy for data practices and retention criteria, and the Subprocessor List for core service providers.