invyrt

Privacy policy

1. Who is responsible

Invyrt Studio is a product name, not a registered company name. The responsible seller and data controller will be [LEGAL NAME], an individual operating in Jalisco, Mexico, at [BUSINESS CONTACT ADDRESS]. Privacy and support contact: [CONTACT EMAIL]. These details must be completed before public collection or sales. An adult representative must participate in payment onboarding where required.

2. Your editing files stay on your computer

The current desktop app processes video, audio, speech transcripts, clip selection, face-aware framing, captions, and rendering locally. It does not upload those files to us or to a cloud AI service, and it has no transmitted usage analytics or automatic crash-report uploader. We do not receive your editing content or use it to train models. Face framing detects positions locally; it is not an identity-recognition service.

Projects, source paths, transcripts, thumbnails, preview videos, presets, settings, and recovery copies can remain on your disk. Editing files are not encrypted by Invyrt Studio. License state in a configured paid build uses Windows safeStorage. Other people or software with access to your device, and any backup or sync service you choose, may be able to access them. Protect your device and choose storage locations carefully.

The app keeps up to 20 local job records with task category, outcome, elapsed time and a general error category. These records are not uploaded. Settings can save a support report containing those records, app and OS versions, memory/thread counts, processing preference and tool-readiness flags. The report excludes source paths, captions, transcripts, license identifiers and raw error messages. You choose whether to share it.

3. Downloads and internet connections

Setup downloads the editing engine from GitHub and speech or clip-analysis models from Hugging Face and their delivery infrastructure. Those providers receive normal connection data, such as your IP address, requested file, and request time. The app does not include your video, audio, or transcript in these download requests. Their own privacy policies apply to their infrastructure.

The current editor works offline after the required tools are installed. It runs a local analysis server on your computer’s loopback interface, protected by a temporary key. Future subscription activation may require internet access; the final activation frequency and account-data flow must be disclosed before that feature launches.

4. Website and early-access information

If you join early access, this website stores your email address, computer platform, video category, signup time, consent version, a random record identifier, and a hashed removal token. We use these to manage beta interest and the beta or launch updates you expressly request. Joining does not make a purchase or promise a beta place. No automated email campaign is currently connected.

The form also uses a hashed IP-based identifier, request count, and expiration time to limit abusive submissions. This is pseudonymous security data, not a promise of anonymity. The identifier expires after 24 hours; expired records are removed during subsequent successful signup requests. Raw IP addresses are not stored in the early-access database by our form code. Hosting and access providers may keep their own connection or security logs.

We have not added advertising trackers or third-party analytics scripts. Cloudflare and the Sites hosting/access platform provide infrastructure and may process technical connection and authentication information under their own terms. A private-preview login is separate from an editor account.

5. Planned payments and support

Subscriptions are not available yet. If Stripe is selected, the payment notice must identify the actual Stripe service and entities used. Stripe would receive payment details directly; we would generally receive customer identifiers, contact and billing details, payment status, subscription dates, and limited payment-method information. We should not receive your full card number or security code. This section must be confirmed against the finished integration.

If you contact support, we receive what you choose to send. Do not send passwords, full card details, identity documents, sensitive footage, or client files through ordinary support messages. We will ask for the minimum information needed and offer redacted error information when possible.

6. Purposes and choices

Necessary purposes are operating the requested service, fulfilling purchases when enabled, support, security, and applicable recordkeeping. Beta and launch marketing is optional and requires a separate choice. Declining optional marketing will not prevent a future purchase. We do not sell personal data or share editing footage for advertising.

You can leave early access using the private removal link supplied after signup at /access. Keep it private: anyone holding it can remove the matching entry. If the link is lost, the published privacy contact must provide another verified request route before public launch.

7. Retention and deletion

Desktop data stays until you remove it. Settings can clear preview-cache files; this does not delete transcripts, recovery copies, projects, models, or original videos. Uninstalling the app may leave profile data behind. Saved projects and exports may be outside the app profile. We cannot remotely erase local files we do not possess.

Early-access records currently remain until removed through their private link or by the operator. There is no automatic lead-retention deadline implemented yet. Before public launch we must adopt and implement a limited retention schedule, including support records and provider backups. Billing and tax records, when introduced, will be kept for applicable legal periods; the specific periods must be documented before collection. Deletion from the active database does not establish immediate deletion from provider backups.

8. Providers and international processing

The website uses Cloudflare D1 for the early-access database and Sites infrastructure for hosting and access. GitHub and Hugging Face provide downloads. Stripe integration is prepared locally but is disabled and has not been verified with a connected account. These providers may operate outside Mexico, including in the United States. Before public launch, the operator must confirm provider roles, processing locations, contracts, and any required transfer consent.

We disclose information only as needed for the stated purposes, with authorized providers, when you direct us, or where a valid legal obligation requires it. A new purpose or transfer requiring consent will not be justified merely by silently changing this page.

9. Your privacy rights

You may request access, correction, cancellation, or opposition to processing of data we hold, revoke consent where applicable, and ask to limit use or disclosure. Send a request to [PRIVACY EMAIL] with your contact method, the right requested, and enough information to locate the record. We will use proportionate identity verification and explain any lawful retention or refusal. Do not send identity documents until a suitable verification method is agreed.

Requests will be handled within applicable legal deadlines. You may complain to the competent data-protection authority. Residents elsewhere may have additional rights under laws that apply to them. We cannot retrieve local footage merely because you submit a privacy request.

10. Children and security

The planned purchasing service is for adults or customers acting through a parent or legal guardian with legal capacity. We do not intentionally solicit children’s personal data. A guardian can contact us about information submitted by a child.

We use access restrictions and other safeguards appropriate to the information handled, but cannot guarantee absolute security. We will assess and communicate security incidents as required by applicable law.

11. Changes and contact

The version and effective date will appear here when this policy is finalized. Material changes will be communicated through the website and, where appropriate, direct notice. We will obtain additional consent when required. Contact: [PRIVACY EMAIL]. This draft does not replace a completed Mexican privacy notice.

← Legal overview and launch decisions