Privacy Policy

2. Information we collect

Account information. When an editor signs up, we collect their name and email address through our authentication provider, along with the workspaces, projects, clients, and team members they create in the product. Team members an editor invites are identified by name, email address, and their assigned role.

Content editors upload.Editors upload videos, images, and audio files to their projects. These files are stored in our media infrastructure (see Subprocessors below) and belong to the editor’s workspace.

Feedback reviewers submit.Through a review link, reviewers can submit typed notes, recorded voice notes, drawings made on a frame, an overall verdict on the cut, and replies in note threads. Voice notes are audio recordings of the reviewer’s voice. All of this feedback is stored with the editor’s project.

Reviewer contact details.Reviewers never need an account. An editor may optionally save a client’s name and email address so that Prelap can send that client occasional service emails on the editor’s behalf, such as “a new version is ready to review.” We use a saved client email only for these notifications, never for marketing.

Emailed-in feedback.Each project can have a private intake email address. When someone sends or forwards an email to that address, we process the email’s subject, body, and sender address to turn it into feedback on the project.

Usage and technical data. Our systems automatically record technical information such as IP address, browser type, device information, and activity logs. We use this to operate the service securely, prevent abuse, and diagnose problems.

Product analytics. We use PostHog to understand how the product and website are used: page views, referring sites, campaign tags, and interface interactions. Analytics requests are routed through our own domain. We have disabled session recording, and the unguessable tokens in private review links are masked in the browser before any analytics event is sent, so private link addresses never reach our analytics provider.

Payments. Paid checkout has not launched yet. If you join the upgrade waitlist, we store the email address you provide so we can contact you when paid plans open. When checkout launches, payments will be handled by a dedicated payment processor (such as Stripe); card details will go directly to that processor and will never be stored on our servers. We will update this policy when checkout goes live.

3. How we use your information

We use the information described above to:

• Provide, maintain, and improve the Prelap service;
• Process uploaded content and reviewer feedback into structured revision checklists;
• Authenticate editors and keep accounts and workspaces secure;
• Send service notifications to editors (for example, when new feedback arrives) and, where an editor has saved a client’s email, to that client (for example, when a new version is ready);
• Understand aggregate product usage so we can improve it;
• Manage the upgrade waitlist and, once live, subscriptions and billing;
• Detect, prevent, and investigate fraud, abuse, and security incidents; and
• Comply with legal obligations.

We do not sell personal information, and we do not use your content or feedback for advertising.

4. AI processing

Turning unstructured feedback into an organized checklist is a core function of Prelap. To do this, feedback text, voice-note audio, and related project context are sent to third-party AI providers: OpenAI as our primary provider and Google (Gemini) as a fallback. These providers transcribe audio, structure feedback into checklist items, summarize changes between versions, and power the in-app assistant that editors use.

We never use your content or your reviewers’ feedback to train AI models of our own, and we send content to AI providers only to deliver the features described here. AI-generated results can contain errors, so editors should review structured checklists and summaries before relying on them.

5. Sharing you control

Editors can connect their workspace to outside tools. If an editor sets up an integration (for example Slack notifications, or webhooks consumed by tools like Zapier), Prelap will send review events to the destination the editor chose. Those events can include project names, reviewer names, feedback excerpts, and links back to Prelap. The editor decides what is connected, and can pause or remove any integration at any time in Settings.

Similarly, editors can export checklists (for example as editing-timeline markers) and share review links with whomever they choose. These are actions taken by the editor, under the editor’s control.

6. Subprocessors

We rely on trusted providers to run Prelap. Each processes information only to provide services to us:

• Vercel: application hosting and content delivery;
• Supabase: database, authentication, and storage of small media such as voice notes and annotated frames;
• Cloudflare R2: storage of uploaded media files;
• Bunny Stream: video encoding and streaming delivery;
• OpenAI: AI transcription and feedback structuring (primary);
• Google (Gemini): AI transcription and feedback structuring (fallback);
• Resend: transactional email delivery and inbound email processing;
• PostHog: product analytics (session recording disabled, private link tokens masked);
• Payment processor (such as Stripe): payment processing, once paid checkout launches.

7. Cookies and similar technologies

We use essential cookies for signed-in editor sessions and a short-lived cookie that grants access to password-protected review links. Our analytics provider (PostHog) stores a small identifier in the browser (cookie and local storage) so that repeat visits can be counted correctly; these analytics run through our own domain and are not used for advertising. We do not use third-party advertising cookies or cross-site tracking cookies.

8. Data retention and deletion

When an editor deletes a project or version, it moves to a Trash where it remains recoverable for 30 days. After 30 days it is permanently purged, including the media files in our storage and streaming infrastructure.

Editors can delete their entire account and workspace at any time from Settings, which permanently removes the associated data from the service. We may retain limited records where required for legal, tax, security, or fraud-prevention purposes.

9. Your rights

Depending on where you live, you may have rights to access, correct, delete, or export your personal information. Editors can delete notes, projects, and their whole account directly in the product. For anything else, contact hello@prelap.io and we will respond as required by applicable law.

Reviewers can edit or delete their own notes from the review page while the review round is open. Because reviewers do not have accounts, other requests about reviewer feedback are usually best directed to the editor who owns the project; we will assist editors in fulfilling such requests where we can.

10. International data transfers

Prelap and our subprocessors operate in various countries, so your information may be processed and stored outside the country where you live, including in countries whose data-protection laws differ from your own. When we transfer information, we rely on our providers’ safeguards for such transfers.

11. Children

Prelap is a professional tool intended for video editors and studios. It is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has provided us personal information, contact us and we will delete it.

12. Security

Data is encrypted in transit using industry-standard TLS. Workspaces are isolated so one editor cannot access another’s data. Review links use long, unguessable tokens and can additionally be password protected and set to expire. Outbound webhooks are signed so receivers can verify they came from us. Access to production systems is restricted. No online service can be completely secure, but we work to protect your information and to respond promptly to any incident.

13. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, notify editors. Your continued use of Prelap after changes take effect constitutes acceptance of the updated policy.

14. Contact

Questions about this policy or your data? Email us at hello@prelap.io.