Data Deletion Policy

Runes supports several different actions because disconnecting a provider account, deleting one SaaS end user, and closing an entire Runes organization have different effects. This policy explains those options, what Runes removes, what may be retained, and how to make a request.

• Revoke a connection to stop Runes from using one advertising or creator authorization.
• Delete an external user to remove or anonymize data associated with the identifier a Customer assigned to that end user.
• Delete a Runes account to remove an individual dashboard profile, subject to organization and record-retention requirements.
• Delete an organization or project to close a Customer workspace and delete its Customer Data, subject to verification and lawful exceptions.
• Exercise a privacy right to request access, correction, deletion, restriction, or another right available under applicable law.

Email will@relativecompanies.com with the subject “Runes data request.” You may also use an available account setting, hosted connection-management flow, or documented API endpoint. Include:

• your name and email address;
• the relevant Runes organization and project, if known;
• whether the request concerns your Runes account, a provider connection, an external user, a creator connection, a project, or the full organization;
• the relevant Runes resource or external-user identifier, if available; and
• enough context for us to identify the data and understand the requested action.

Do not email passwords, API keys, Link tokens, OAuth codes, provider access tokens, payment card information, government identifiers, or unnecessary sensitive data.

We verify requests to prevent unauthorized deletion. Verification may require access to the relevant email account, a current Runes session, proof of organization membership, confirmation through the Customer that assigned an external user identifier, or other information reasonably matched to existing records.

Organization owners and administrators may request project or organization deletion only within their authorized role. An authorized agent may submit a request where law permits, but we may require proof of authorization and may verify the request directly with the affected person. We will not request more information than reasonably necessary.

An end user can revoke through an available hosted management page, the connected provider, or the Customer’s product. An authorized Customer can revoke through the Runes API or dashboard. When Runes processes a revocation, it:

• immediately blocks new Runes use of that connection;
• removes usable encrypted provider credentials from active storage;
• revokes selected advertising-account associations;
• ends future active connected-account billing periods attributable to the revoked association;
• attempts provider-side token revocation when supported; and
• records and emits safe lifecycle status without exposing credentials.

Revocation does not automatically delete advertising resources already created at Meta, TikTok, or another provider. Those resources remain subject to provider controls and may need to be paused, archived, or deleted separately.

Runes Customers can initiate an asynchronous, idempotent deletion for the external user identifier used in their project. The workflow is designed to:

• attempt revocation of associated provider connections and creator authorizations;
• remove encrypted provider credentials and selected-account associations;
• cancel pending Link and OAuth state;
• end applicable active billing periods;
• tombstone the external user identifier so it is no longer available for ordinary use;
• remove or anonymize its attribution from stored plans, resources, and private assets where deletion applies; and
• preserve a minimal terminal operation and safe audit evidence so completion, failure, retry, and abuse prevention remain verifiable.

Customers may retrieve an external-user export before deletion through the documented API. A deleted identifier may not be recoverable after the workflow completes.

Creator connections are separate from advertiser connections. A creator or authorized Customer may revoke an eligible creator connection through the available hosted flow or API. Runes blocks new use, revokes active authorizations, requests provider-token revocation, clears encrypted creator credentials, and retains only tombstoned history and minimum audit evidence.

Revoking a creator authorization prevents new use through Runes but may not remove an ad that a provider has already created or delivered. The provider controls the effect on existing ads. Private creative originals and generated variants subject to a verified deletion request are removed from active object storage, while a minimal checksum or audit tombstone may remain when necessary to prove deletion or prevent replay.

A request to delete an individual dashboard account removes or de-identifies that person’s profile and authentication data when the account is no longer required for an organization, security record, or legal obligation. Organization-owned resources are not automatically deleted merely because one member leaves.

A verified organization or project deletion can include member associations, API-key records, webhook configurations and secrets, provider connections and credentials, external-user mappings, private creative files, normalized resources, reporting data, and other Customer Data within scope. Before deletion, the owner should export required data, revoke live credentials, stop active advertising, and resolve outstanding invoices.

We may require a short administrative period to prevent accidental destruction, complete provider revocation, settle billing, and safely process distributed data. Once deletion becomes irreversible, the workspace and deleted Customer Data cannot be restored through ordinary support.

Deletion does not require us to erase every record immediately when retention is necessary and lawful. We may retain the minimum data needed for:

• security, fraud prevention, abuse detection, credential-compromise investigation, and enforcement;
• immutable audit trails, idempotency, operation integrity, provider lineage, and proof that revocation or deletion occurred;
• billing, metering, invoices, taxes, accounting, chargebacks, and financial reconciliation;
• legal holds, disputes, court orders, regulatory obligations, and establishment or defense of legal claims;
• provider rules that require safe history or prevent immediate deletion;
• aggregated or irreversibly de-identified analytics that no longer identify a person; and
• time-limited encrypted backups protected from ordinary product use until overwritten through the backup lifecycle.

Retained records are restricted to the relevant purpose and are not used to reactivate a deleted connection or external user. We delete or de-identify them when the exception ends.

Runes currently applies these technical defaults unless a shorter lawful request, legal hold, order form, or provider requirement controls:

• encrypted transient conversion IP address, user agent, and provider click identifiers are deleted after terminal provider delivery or within 24 hours, whichever comes first;
• incomplete upload intents expire after 7 days;
• blocked and unappealed quarantine bytes expire after 30 days;
• raw provider payloads expire after 30 days by default once necessary normalization and safe lineage are extracted; and
• bounded safety and provider-history evidence is retained for 90 days by default.

Normalized reporting, resource history, audit, billing, and Customer relationship records have separate schedules based on their purpose. A deletion request is evaluated against those schedules and the lawful exceptions above.

Meta, TikTok, Stripe, and other third parties control data in their own systems. A Runes deletion does not itself delete a provider account, payment record, ad, audience, or other provider-controlled data. Submit a separate request to the relevant provider when needed.

Runes does not falsely report completion when provider revocation fails. We block new use within Runes, record a safe failure, and allow an authorized retry where supported. We may ask the requester to revoke directly with the provider if the provider is unavailable or no longer accepts our credential.

Deleted data may persist temporarily in encrypted, access-restricted backups. Backups are not used for ordinary product operations and are overwritten or expire under the backup lifecycle. If restoration is required for disaster recovery, deletion controls are reapplied where technically feasible.

We acknowledge verified privacy requests and respond within the period required by applicable law. We generally aim to complete straightforward verified requests within 30 days. Complex, high-volume, provider-dependent, or legally extended requests may take longer, and we will explain an extension where required.

API-based external-user deletion is asynchronous. Customers should treat the returned operation status or the signed privacy.deletion_completed webhook as the completion signal. A redirect, accepted request, or local credential removal alone is not proof that every provider step succeeded.

We may deny or limit a request when we cannot verify identity or authority, the requested data is outside our control, an exception applies, the request is manifestly unfounded or excessive, or law permits or requires retention. We will provide the reason and available appeal information where required.

To appeal, reply to the decision or email will@relativecompanies.com with the subject “Runes privacy appeal.” You may also have the right to contact a data-protection, consumer-protection, or other supervisory authority.

Contact Relative Companies Inc. at will@relativecompanies.com for deletion, access, correction, appeal, or other privacy requests concerning Runes. If your data was submitted through another company’s product, identify that Customer where possible so we can locate the correct tenant and coordinate the request without exposing another Customer’s data.