Privacy Policy

1. Controller and contact

The SnapVee Studio website and related task services are operated by the SnapVee Studio team. Questions, deletion requests, or complaints can be sent to support@snapvee.com.

2. What we collect

Account data: your email address, login method, and basic profile information returned by Google sign-in if you choose that option.

Payment data: payment status, order identifiers, and necessary billing metadata. Full payment card details are handled by third-party processors and are not stored directly by us.

Visitor and quota-control data: to enforce guest limits, abuse prevention, and rate limiting, we process device fingerprints, IP addresses, browser information, request timestamps, error logs, and related identifiers.

Task data: submitted links, platform identifiers, requested quality, download type, task status, error details, temporary download URLs, and download history visible to signed-in users.

Credential material: if you voluntarily submit cookies.txt or similar authenticated-session material, it is processed as task input. The public site no longer teaches this workflow, and we prefer local-device handling instead.

Site storage and analytics: the website uses browser storage for language preference, cookie-consent state, affiliate attribution, and similar settings. Analytics or diagnostics tools may also receive browser and device data.

3. How we use the data

To create and maintain accounts, process sign-in, complete payments, run the task queue, and generate temporary delivery links.

To enforce guest quotas, rate limits, abuse prevention, security review, troubleshooting, and customer support.

To display task history, error states, and retry information, and to handle rights-holder notices, platform complaints, or legal requests when needed.

4. Temporary files, credential material, and retention

After a task completes, result files may be uploaded to temporary object storage before they are delivered to you. The target retention period is about 24 hours, but actual deletion can happen later if cleanup jobs are delayed or fail.

Failed-task records, error logs, and some database records may be retained longer for troubleshooting and risk control; under the current cleanup policy, failed task records may remain for about 30 days.

If you voluntarily submit cookies.txt or similar material, we use it only for the related task rather than as a public feature to keep long term. Any cloud transfer of that material carries risk, which is why local-device handling is preferred.

5. Who we share data with

We share data with service providers that support hosting, object storage, authentication, payments, analytics, messaging, databases, and infrastructure where necessary to operate the service.

We may also disclose data related to a specific task, account, or access pattern when required by rights-holder complaints, platform notices, payment-risk review, or applicable law.

6. Cross-border transfers

SnapVee Studio relies on infrastructure and service providers that may be located outside your country or region, so your data may be transferred to and processed in other jurisdictions.

By continuing to use the service, you understand that these cross-border transfers may occur.

7. Your choices and rights

You can contact us to request access, export, correction, or deletion of account data, and you can ask us to remove specific task records, subject to records we must keep for legal, payment, risk, or dispute reasons.

You can clear browser storage, disable some cookies, or adjust third-party sign-in permissions. Doing so may make some features unavailable.

8. Regions and minors

Availability may vary by jurisdiction, platform rules, and risk controls. We may limit public access in higher-risk regions.

The service is not designed for children below the age permitted by local law. If we discover such accounts or related data, we may remove or restrict them.

9. Policy updates

If our data flows, infrastructure, or legal requirements change, we will update this page and revise the effective date.