Privacy Policy

Topee AI. (“Topee,” “we,” “us,” or “our”) turns a real product flow — a staging or preview URL you give us — into an editable, narrated demo or launch video. This policy explains what information we collect across topee.io and the Topee application (together, the “Service”), why we collect it, who we share it with, and the choices you have.

This policy is written for people who use Topee directly (account holders, workspace members) and, in the sections that apply to them, for people who only view a video someone shared with them.

We collect the following categories of information.

• To operate the Service: authenticate you, run browser sessions against the URL you provide, plan and render videos, and store your projects.
• To generate narration and avatar video, where you request it, using the providers listed in Section 4.
• To process payments and manage subscriptions.
• To provide viewer analytics on shared videos, for plans that include that feature.
• To respond to support requests and send service notices.
• To send product updates or marketing email, which you can opt out of at any time.
• To monitor, secure, and improve the Service, including diagnosing errors and preventing abuse.
• To comply with legal obligations and enforce our Terms of Service.

Building a video involves several automated steps: a language model plans which parts of your product to capture and drafts narration, our system operates a real browser against the URL you provided, and a rendering pipeline assembles the final video. A few things we want to be explicit about:

• We do not fabricate functionality. Any product behavior shown in a video comes from an action actually performed and recorded in your session. Motion graphics, titles, and captions may frame or explain that behavior, but they do not imply a feature that was not really captured.
• Automation is non-destructive by design. The browser session is instructed not to take destructive actions (such as deleting data or sending payments) while exploring your product.
• Your content is not used to train third-party foundation models. We send the minimum content necessary — page structure, your brief, and similar inputs — to our AI subprocessors to generate your video. We do not authorize those providers to use your submissions to train models for other customers.
• Every generated video remains editable and reviewable by you before you share or publish it — nothing is published automatically on your behalf.

We do not sell your personal information. We share it only as follows.

We use two categories of cookies and similar technologies:

• Essential: required for the site and application to function — keeping you signed in, remembering your cookie preference, and basic security protections. These cannot be turned off.
• Analytics: help us understand how the Service is used, so we can improve it. You can decline these from the cookie banner shown on your first visit, or by clearing your cookie preference in your browser to see the banner again.

We keep account and project data for as long as your account is active, plus a limited period afterward to allow recovery and to meet legal, accounting, or dispute-resolution requirements. Uploaded media you delete from the Asset Library is marked for deletion and removed from active storage; deleted media that is still referenced by a video you have already generated is retained only as long as needed to keep that video working, or until you remove the reference. Waitlist entries are kept until you ask us to delete them or until we complete the outreach they were collected for.

We apply the following practices, consistent with what we describe publicly on our Security page:

• Data encrypted in transit and, where supported by the underlying provider, at rest.
• Uploaded and generated media is stored privately; it is never publicly listable, and access requires a short-lived, scoped link.
• Workspace-level access control — a member only sees the workspaces they belong to, and their role determines what they can change.
• GitHub connections are read-only and scoped to the repositories you select.
• Each internal service (the app, the render pipeline, the browser-automation worker) uses its own least-privilege credentials rather than one shared key.

No method of transmission or storage is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you as required by applicable law.

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, or to object to or restrict certain processing. To exercise any of these rights, contact us at mloza@placehub.mx. We will respond within the time required by applicable law.

You can also unsubscribe from marketing email at any time using the link in that email.

We and our service providers may process information in countries other than your own, including the United States. Where required, we rely on appropriate safeguards, such as standard contractual clauses, to protect information transferred internationally.

The Service is intended for business use and is not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with personal information, contact us and we will delete it.

The Service may link to third-party websites or contain videos that link out. We are not responsible for the privacy practices of sites we do not operate.

We may update this policy from time to time. If we make material changes, we will notify active account holders by email or through the Service before the changes take effect. The “Last updated” date at the top of this page always reflects the current version.

Questions about this policy or requests regarding your personal information can be sent to mloza@placehub.mx.