Privacy Policy

This Privacy Policy explains how EditGod collects, uses, and shares information when you use https://editgod.ai and the EditGod web app.

EditGod is an early software product for operators in the United States. We have not registered a separate company name, employer identification number, or business address for this service. Questions about privacy go to the founder at danielfirmida@editgod.ai.

What the product does

You upload raw videos and optional instructions or product context (a public URL and/or your own text). We analyze that footage and produce an edit guided by your instructions. You may optionally claim a project with your email. We do not connect to your TikTok account, publish videos for you, or measure whether a cut sold.

Information we collect

• Video files you upload, plus files we derive from them: transcripts with word timestamps, edit plans, preview and export cuts, and — only if you accept a hook offer — a short generated opening.
• Product context you type, and text we fetch from a public product URL you give us so we can stay aligned with the product you are selling.
• A session cookie named ecomeister_sid so an anonymous project can survive a refresh before you create an account.
• Your email address if you claim a project.
• If you join the waitlist: your name, email address, and who referred you (optional), so we can contact you about access. Joining does not subscribe you to a newsletter. Signup rate limiting uses a keyed hash of the network address; the raw address is not stored.
• If you subscribe: Stripe customer and subscription identifiers. Stripe processes card details. We do not store full payment card numbers.
• Limited technical logs needed to run and debug the app. We try not to log video files, signed URLs, or other unnecessary personal data.

How we use it

We use this information to operate EditGod:

• store and validate your upload;
• transcribe speech and classify usable sales moments;
• edit the footage you provided according to your instructions;
• generate a hook only after you accept that offer, using a short cropped clip rather than the entire raw file;
• keep your session so you can return to the same project;
• send a claim or verification email if you ask us to;
• contact waitlist members personally by email about access to the product;
• send one follow-up email after you download a cut, asking whether you posted it and inviting a reply;
• ask optional in-product questions after a generation or download (whether you would test the cuts, and whether the run saved time) so we can improve the product;
• bill a paid plan and open the Stripe customer portal when available.

Commercial claims in a generated hook must stay tied to facts you supplied or that appear in the footage. We do not sell your personal information. We do not show invented performance or conversion scores in the product.

Cookies and session

The primary cookie is ecomeister_sid. It is an HTTP-only session identifier (SameSite=Lax) used to associate uploads and projects with your browser. We do not use it to build an advertising profile, and we do not send that cookie value to advertising partners. If you block cookies, you may lose an unclaimed project after you leave the site.

When product analytics is enabled, PostHog may also set its own cookies or use browser storage to keep a separate analytics identifier. That identifier is derived from your session on our servers and is not the same value as the HTTP-only session cookie.

When advertising measurement is enabled, Meta may set _fbp and _fbc cookies in your browser so we can attribute a later checkout or email claim to an ad click. Those cookies are not the same as your EditGod session cookie.

Analytics and error monitoring

When configured, we use PostHog (US Cloud) for product analytics and optional session replay to understand how the app is used and to improve the editing flow. PostHog receives event names, coarse usage properties, and replay data with inputs masked. Structured survey answers (for example yes/maybe/no) may be included; optional written comments stay on our servers and are not sent to PostHog. We do not send your email address to PostHog, and we do not track TikTok Shop sales or GMV in the product.

When configured, we use Sentry for error and performance monitoring so we can diagnose failures in the app and worker. Sentry may receive error messages, stack traces, and request metadata needed to debug issues.

PostHog, Sentry, and — when the in-app chat is enabled — Crisp act as processors on our behalf. Each provider has its own privacy policy and may set additional cookies or storage in your browser. We do not send your email address to Crisp. If you type a message in chat, Crisp receives what you write so we can reply.

Advertising

When configured, we use the Meta Pixel in your browser and Meta's Conversions API on our servers to measure ads. Browser events do not include your email. If you claim a project or subscribe, our servers may send Meta a SHA-256 hash of your email and a hashed session identifier, plus technical identifiers that help match the event: click cookies such as _fbp and _fbc (or an fbclid from the landing URL), and the IP address and user-agent of the request. Those click and request identifiers are sent in the clear because Meta requires them unhashed. If Stripe provides a name, phone number, or billing address at checkout, we may send SHA-256 hashes of those fields on the Purchase event only. We do not collect date of birth and we do not invent matching fields. We may store the click cookies, IP, user-agent, and page URL briefly on the Stripe Checkout session so a later Purchase can be attributed.

We send standard Meta events for a page view, an email claim (Lead), starting checkout, and a completed paid plan (Purchase). Ads optimization uses Lead. We do not send your video files, transcripts, or unsigned download links to Meta.

Payments

When a paid plan is required, checkout and recurring billing run through Stripe. Stripe acts as a payment processor. We receive customer and subscription IDs so we can unlock rendering and, when available, let you manage billing. Stripe has its own privacy policy for payment data.

Processors and storage

Uploaded videos and edit artifacts live on object storage (S3-compatible, which may include MinIO in some environments). We use third-party processors to transcribe audio, classify footage, render cuts, send email, and — only if you accept a hook offer — generate a short opening. Those processors receive only what they need to do that job.

How long we keep it

Unclaimed projects may be deleted after a retention period. The default is 30 days; we may configure a different positive number. Claimed or paid work may be kept longer so you can return to it. This is working storage for an early product, not an archive.

Your choices and deletion

You can start without an account. To ask us to delete a project, a waitlist entry, an email address, or other personal information we hold, write to danielfirmida@editgod.ai. We will take reasonable steps to delete it, except where we must keep a record (for example, a billing record Stripe requires). Removing a waitlist entry does not delete your projects or subscription.

If you pay, you can manage or cancel through the Stripe customer portal when that control is available in the product.

Children

EditGod is for business operators, not children. We do not knowingly collect personal information from anyone under 13.

United States

The service is intended for users in the United States. If you use it from another country, your information may be processed in the United States.

Changes

We may update this policy as the product changes. The date at the top will change when we do. Material updates will be posted on this page.

Contact

danielfirmida@editgod.ai
https://editgod.ai