Arelvia Studio

Privacy

Data we use

Changed-article JSON, Zendesk conversation export JSON, explicit aliases, queue rows, and generated artifacts are processed only in the buyer's current browser and are not uploaded to ReplyDrift. Raw input remains in browser memory until the tab is refreshed or closed; downloaded artifacts remain on the buyer's device. Arelvia Studio receives only anonymous fixed-name funnel events and the selected plan label. Stripe processes Checkout and payment details, while the verification service receives only the bounded claim, Checkout Session reference, public contract, and minimum entitlement data required to provide and recover paid access.

Data that is not permitted

Use a minimized buyer-owned export containing only fields ReplyDrift needs. Remove passwords, API keys, access tokens, authorization headers, signed URLs, attachments, message bodies, transcripts, customer or employee identifiers, personal contact details, payment data, confidential notes, and sensitive or regulated personal information before loading a file.

Purpose

We use the permitted data only to operate ReplyDrift, secure access, support the product, and maintain a minimal operational record.

Retention and access

ReplyDrift does not retain uploaded source data because it does not upload it. Raw inputs and in-memory results disappear when the tab is refreshed or closed; downloaded queue and audit files remain under the buyer's control. Anonymous funnel events may be retained for up to 400 days for product operation and measurement. Minimal entitlement records may be retained as needed to provide and recover paid access, secure and troubleshoot the service, resolve payment disputes, and meet legal obligations.

Sharing

We do not sell participant data. We share data only with service providers needed to operate ReplyDrift, or when required by law.

Policy approved 2026-09-04.

← Back