Privacy Policy

The short version

1. This policy covers two things: our website, goeddi.com (where you can join the waitlist or book a demo), and the Eddi app (where businesses that use Eddi make videos).
2. On the website, we collect what you type into our forms, plus where you came from (the page and campaign), to contact you about Eddi, including product updates and marketing emails; every email has a link to unsubscribe (2.1a). Advertising and measurement tools from the advertising platforms and networks we use (social, search, video and display advertising, including ads shown to you on other websites and apps), and analytics if we use it, load only after you agree to them where the law requires that (such as in the EU, the UK and Quebec). Elsewhere they load by default, and you can turn them off at any time from "Cookie settings" in the footer (2.3).
3. In the app, we keep what we need to run your account and keep it secure: your name, email, sign-ins, and a record of important actions.
4. Footage and brand material belong to the business that uses Eddi. We process them for that business, to make its videos. We also use what Eddi learns from that work, such as its work notes and check results, to improve Eddi's editing for all customers, including with AI tools, not the footage and videos themselves; we don't train AI models on them, and a business can opt out by writing to us (5.6).
5. Eddi's AI runs on AI models from an AI model provider. Mostly it runs on the business's own AI provider account (for example Anthropic's Claude, connected through Eddi's connector, or the business's own API key), under the business's own agreement with that provider. Eddi's own account with our AI model provider, on its commercial terms, covers what runs without it: background work such as indexing footage and reviews, usage included in free plans, and work when no account of the business's is connected. To make videos, Eddi sends the AI provider parts of the work: messages, transcripts, frames of footage, brand material. On Eddi's account, we use only an AI model provider whose commercial terms say it doesn't train its models on that content. Transcription, built-in voices, voice separation and visual search run on our own servers. Section 7 names every provider and what it receives.
6. People who appear in a business's footage: the business decides what footage it uses and is responsible for their consent. If that's you, contact the business first; we'll help.
7. The app uses only the cookies and browser storage it needs to run (sign-in, security, preferences); if we add product analytics or support chat to it, we'll ask for consent where the law requires it. The website uses cookies that are strictly necessary, and others (preferences, analytics, advertising): where the law requires it only if you agree, elsewhere by default with a way to turn them off (cookie notice). The demo booking tool and our payment provider's checkout set their own.
8. If you pay for a plan, you buy it through our payment provider, which acts as our reseller and Merchant of Record (named in 7.2). It collects your payment details and handles tax and invoices under its own privacy policy; we never see your card number. We keep the order and billing records we need to run your plan, for tax, and as evidence if a charge is disputed (3.11).
9. You can ask to see, correct or delete your personal data, or complain to the Philippine National Privacy Commission. Write to [email protected] (or another contact method we publish).

1. Who we are and what this policy covers

1.1 Eddi is run by Vernard Alexis Luz ("we", "us"), an individual in the Philippines who provides the Eddi service ("Eddi"), of 115 GF Future Point Plaza 2, Mother Ignacia Ave., South Triangle, Quezon City 1103, Philippines. Privacy questions and requests: [email protected], or another contact method we publish on our website or in the app; wherever this policy gives that address, the other published methods work too. Data Protection Officer: Vernard Alexis Luz, at [email protected].

1.2 This policy covers:

• (a) the website goeddi.com and its forms (section 2); and
• (b) the Eddi service in every form we offer it: the web app, any mobile or desktop apps, browser extensions, connectors and integrations (such as the connector for your own AI assistant, 5.3), any API, and related services, including payments (sections 3 to 12; "the app" in this policy means all of these).

1.3 Our role.

• Where we decide (controller). We decide how and why the data is used (we are the "controller", or "personal information controller" under RA 10173) for: website visitors, waitlist and demo requests; the account data of everyone who signs in to Eddi (name, email, sign-ins, memberships and roles); security and operational records (the audit log, request logs, usage and cost records); the billing records we keep (3.11); and the records we keep to improve Eddi (3.7), and Organisations' content to the extent we use it to improve Eddi for all customers (5.6; Terms 7.4).
• Where the business decides (processor). For the content a business (the "Organisation") brings into Eddi, and what Eddi makes from it, the Organisation decides what is processed and why, and we process it on its behalf to provide the Service (we are its "processor", or "personal information processor" under RA 10173). This covers footage, photos and audio and the people in them (their faces, voices and what they say), transcripts and clip reviews, brand material, documents, scripts, messages and comments, and the drafts and videos made from them (Terms 7.1). The Organisation's own privacy notice applies to the people in that content.
• Advertising platforms (website). When advertising tools load on the website (2.3), the advertising platforms and networks we use (2.3) collect data on our pages through their advertising and measurement tools (pixels, tags and similar) for their own purposes too, as independent controllers; for the collection and sending of that data from our site, they and we may be joint controllers.
• Our payment provider (payments). Paid plans are sold through our payment provider, which acts as our reseller and Merchant of Record (Terms 6.3; named in 7.2). It collects the buyer's payment and billing details, handles tax, invoices, refunds and disputes, and processes that data as its own controller, under its own privacy policy (linked from 7.2); it is not our processor. Card networks, banks and other payment providers involved in the payment also act for themselves.

2. The website (goeddi.com)

2.1 Waitlist form. Access to Eddi may be limited, for example through a waitlist. If you join the waitlist, we collect:

• your email address;
• what you make (the kinds of videos), from the choices on the form;
• your website or channel (optional);
• the page the form was sent from, the campaign tags in the link you arrived by, any ad click IDs in that link (such as gclid or fbclid, which an ad platform adds when you click an ad), and the time of your request. We store click IDs with your sign-up so we can measure which ads work.

To prevent abuse of the form, we keep a short-lived, non-identifying record of requests, which isn't linked to your sign-up. Sign-ups are stored with our website's providers: our hosting provider and an email service provider, which stores waitlist sign-ups and sends you updates about Eddi (7.2). We use this to contact you about Eddi and getting access, to send you product updates and marketing emails (2.1a), to decide who to invite first, and to understand which pages and campaigns bring people to us.

2.1a Emails from us. If you join the waitlist, we may send you product updates and marketing emails about Eddi (for example news, early access, new features, offers and invitations). Every email has a link to unsubscribe, and you can also write to [email protected]. Our email service provider may record whether an email was delivered, opened or clicked, so we can see what is useful and stop writing to addresses that don't work.

2.2 Booking a demo. Demo bookings are handled by an independent booking tool (7.2), through its calendar embedded on our site. The calendar loads only when you open the booking page or start booking a demo. When you book, the booking tool collects your name, email, the kinds of videos you make, the time you pick and any notes you add, and sends the invitation and reminders; it sets its own cookies and handles this under its own terms and privacy policy. The call runs on a video-call service (7.2). Demos aren't recorded or transcribed.

2.3 Cookies, analytics and advertising. Cookies that are strictly necessary (for example to remember your choice, or keep the site and its forms secure) are always on. For everything else, what happens depends on where you are:

• Where the law requires your agreement first (such as the EU and the rest of the EEA, the UK and Quebec), the website shows a consent banner (accept, reject, or choose by category), and nothing below loads until you agree to it.
• Everywhere else, or if we can't tell where you are, the tools below load by default, with no banner. You can turn them off at any time from "Cookie settings" in the footer, and we treat a browser that sends a Global Privacy Control signal as having turned them off.

To decide which applies, the website uses the country and region our hosting provider works out from your connection. We don't store it; your browser remembers the answer until you close the tab.

The tools are:

• Analytics, if we use it, only with your consent where the law requires it, to understand how the site is used.
• Advertising and measurement tools from the advertising platforms and networks we use: social, search, video and display advertising, including ads shown to you on other websites and apps (retargeting), for example social networks, search engines' pay-per-click ads with their conversion-tracking tags, video platforms, and ad networks and exchanges that place ads on other sites and apps. Their tools (pixels, tags and similar) load as described above. When they load, they collect device and browser identifiers, cookies, your IP address, ad click IDs (such as gclid or fbclid), the pages you view and events such as signing up, and send them to that advertising platform. We use them to measure our ads (which ads lead to visits and sign-ups) and to show ads to people who visited our site, on that platform and on other websites and apps, including in custom or lookalike audiences built by the platform; for that a tool may also send the platform your email address in hashed (scrambled) form, so it can match you to an account. The platforms also use this data for their own purposes, as independent controllers, or jointly with us for the collection (1.3), under their own privacy policies (the platforms we use now are listed, with links, in 7.2). This data may go to the United States and other countries (8.1). All of this applies to any advertising platform or network we use; the ones we use now are listed in 7.2.

You can change your choice or withdraw your consent at any time from the "Cookie settings" link in the footer, which is there while the site uses these tools; tools you turn off stop loading from the next page. Turning them off doesn't undo what was collected before, which the platforms keep under their own policies (2.6). See the cookie notice at the end.

2.4 Hosting, content delivery, fonts and booking tools. The website uses providers for hosting, content delivery, fonts and booking tools (7.2). When your browser loads the site, these providers see your IP address and basic browser details, and our hosting and content delivery provider keeps request logs (such as IP address, browser, the pages requested and the time) to deliver the site and keep it secure, for as long as its own policies say. We may also keep logs of our own, for the same purposes.

2.5 When you're invited. If we invite you to the app, we use your email (and name and company, if you gave them) to set up your Organisation and send the invite. From then on, section 3 applies.

2.6 How long we keep website data. Waitlist sign-ups: until you ask us to delete yours or unsubscribe from all our emails, or until we stop offering Eddi; there is no fixed period. After you unsubscribe, we keep only your email address on a do-not-contact list, so we don't write to you again. If we invite you, section 3 applies from then. Abuse-prevention records: short-lived (2.1). Data collected by advertising pixels and analytics: kept by each platform under its own retention policy. Demo bookings: the booking tool keeps them under its own policy. You can ask us to delete any copy we have of your booking. You can unsubscribe from our emails at any time, using the link in them or by writing to us.

2.7 Requests for access in the app. The app may also have a form to ask for access, which collects your name, email, company, website and an optional note, and tells our administrators that you asked. The request also records when we decided on it and who decided. Requests are kept as in 9.1.

3. The Eddi app: what we collect

3.1 Accounts and sign-in (from you, or the person who invited you).

• Your account: name, email address, a profile photo if you add one, when the account was created and last used, whether it is disabled, and whether you are one of our administrators.
• How you sign in: with email and password, or a third-party account such as Google, if offered (we then receive the name, email and account identifier that account shares). Your password is never stored; we keep a salted hash of it.
• Sign-in sessions: a random token in a cookie (we keep only a hash of it), the Organisation you're working in, when the session was created and last used, your IP address and your browser's user agent. A session lasts for a limited period (9.1).
• Invites and password resets: the email invited, the role and brands offered, who invited, and a hashed one-time link that works for a limited time.
• Your acceptance of the Terms: when you tick the sign-up box (agreeing to the Terms and this policy, and confirming you'll only bring in content you have the rights and consents for, Terms 7.7), we record the Terms version and the time.
• Your preferences: pinned items and display settings.
• The connector: if you connect your own AI assistant (for example Claude) to Eddi, we keep the approval (an OAuth grant: which app, which Organisation, when last used), hashed access and refresh tokens, and what the connector did in your Organisation (tool names, renders and drafts, with your user id and time).

3.2 Organisations and membership (from the Organisation's owner and admins). The Organisation's name, website, plan and limits; who belongs to it, with their role (owner, admin or member) and which brands each may access; its settings, brands and projects.

3.3 Your content (from the Organisation and its members; we are its processor, 1.3).

• Uploads and footage: video, photos, audio, logos, fonts and other brand material, uploaded or imported from a connected cloud drive or storage bucket, or fetched from a link (including videos on social media and video platforms).
• The library: each brand's footage, organised by creator, recording date and batch.
• Brands: brand guides, products, facts and claims, voice and style notes, and what Eddi read on the brand's website (text, images, logos, colours and fonts, read by a browser on our servers).
• Videos: briefs, ideas and pitches, scripts, captions, drafts and their versions, comments on drafts, and finished videos.
• Chats: your messages to Eddi and Eddi's replies, and its working trail (the tools it used and their results), kept with each video.
• Work notes: Eddi's notes on its process (checks it ran and what it found, re-renders and why, what couldn't be verified), kept with the video and visible to our administrators, not shown in the chat.

3.4 What Eddi derives from your footage. To find and use footage, Eddi makes and keeps, for each clip:

• a transcript of its speech, with word timings. By default this runs on our own server, with an open model; if the Organisation chooses online transcription, the audio goes to the transcription provider it chooses, on the Organisation's own key;
• contact sheets, poster frames and playback copies (smaller copies of the video for playing in the browser);
• an AI review, made by AI (5.1) from the contact sheet and transcript: a summary, tags, quality notes, the best lines, products shown, and notes on who appears (for example "creator, family, kids") and anything to avoid. Where the clip itself says or shows it, the review also records the on-camera person's name or social handle (for example "hi, I'm Megan", or a handle on screen) and a short story of who they are in their own words (for example where they live and what they use the product for);
• the creator and channel, read from folder and file names (for example an influencer's folder);
• visual search vectors ("embeddings") of about a dozen frames per clip, made on our own server by an open image model, so the Organisation can search clips by what they show;
• a voice-only track of a clip when Eddi needs to separate speech from background sound (on our own server).

Faces and voices. Footage contains people's faces, bodies and voices, and transcripts contain what they say, which may include health, family or other personal details. Eddi doesn't use face recognition or voice recognition, and doesn't make face templates, voiceprints or other biometric identifiers: people are grouped only by the names in folders and file names, and by what a clip says or shows. Visual search vectors describe what a frame shows, not who a person is.

3.5 Connected accounts and keys (Terms 10). When the Organisation connects an account or adds a key, we store what's needed to use it: for cloud drives, the access and refresh tokens and the connected account's name and email; for storage buckets, the bucket details and keys; for the Organisation's own AI provider and the AI footage, voice, music and sound providers it chooses to use, the API key. Keys and drive tokens are stored encrypted; the connected account's name and email are kept readable so Settings can show them. Our pages only ever show whether a key is set, never the key.

3.6 Usage and operational records. To run, limit, bill and secure the Service we record:

• AI usage: for each piece of AI work, its kind, model, tokens, cost, duration, which AI account paid (Eddi's or the Organisation's), and the Organisation, brand and video;
• paid provider calls (voices, music, AI footage), their cost per video, the credits a provider reported for them, and the monthly limits the Organisation set for its own keys (Terms 6.4);
• renders, jobs and machine time: status, timings, errors, the machine used, and machine minutes per Organisation;
• waits and timings: when a video waited and why, and how long downloads and processing took;
• machine samples: CPU, memory, disk; no personal data;
• request logs: our web server logs each request: the time, method, address (which may contain ids of videos or files, but not their content), response code, time taken, and the IP address it came from. They may be stored with a monitoring provider (7.2).
• error reports: when something fails in the app or in your browser, an error report may be sent to our error-tracking provider so we can find and fix it: what failed and where in our code, the time, the page or request, your browser and device type, your IP address, and your account and Organisation ids. We set it up to leave out passwords, the content of requests, your videos and footage, and email addresses. Error reports are kept for 30 to 90 days.
• uptime checks: an outside monitoring service checks regularly that the app and website respond; it sees only our public addresses, not your data.

3.7 Records kept to improve Eddi. We keep structured records that let us (and AI tools we use for analysis) find where Eddi could do better, for example which automatic checks Eddi overrode and why, what the checks caught, how often files are fetched back from a drive, what happened when footage went missing, how comments were read, whether review suggestions were kept, and work notes (3.3). They carry Organisation, brand, video and draft ids and short text (such as a check's finding), and aren't shown to customers. We use them to improve Eddi for all customers (5.6), unless the Organisation has opted out. After an Organisation is purged, they are kept 12 months and then deleted (9.1).

3.8 Audit log. We record security- and administration-relevant actions with the user, Organisation, time and target: sign-ins, failed sign-ins (with the email address typed), invites, joining, role and brand-access changes, connections, Organisation changes, deletion, purge and erasure, and every visit by one of our administrators to an Organisation they don't belong to ("support visit", including what they changed).

3.9 Emails we send. Invitations, password resets and "you're in" emails when an Organisation is set up or approved; warnings to every member 30 days and 3 days before an idle free Organisation is deleted (9.1); and, to our own administrators, a note when someone asks to join, and performance alerts. The app sends no marketing emails; product updates and marketing emails go to the website's waitlist from our email service provider (2.1a). The app's emails are sent through our email provider (section 7).

3.10 Our administrators. Our own staff with administrative access (super-admins) can see Organisations and act in them to run, support, secure and bill the Service (Terms 4.6). Each visit to an Organisation they don't belong to, and each change they make there, is recorded in the audit log.

3.11 Billing and payments. Paid plans are bought by the Organisation's owner through our payment provider, which acts as our reseller and Merchant of Record, as subscriptions that renew monthly (Terms 6.3, 6.3a). The payment provider collects the payment details (card or other payment method, cardholder name, billing address) in its own checkout, and handles tax, invoices, receipts, refunds and disputes; we never receive or store card numbers or other payment credentials.

• What the payment provider sends us, and what we keep for each Organisation and payment: the buyer's name and email, company name, tax ID and billing country (or address) given at checkout; the payment provider's customer, payment and subscription identifiers; the plan, period, amount, currency and tax; the payment's status (paid, failed, refunded, disputed); renewals, plan changes and cancellations; refunds we asked the payment provider to make and why (Terms 6.6); disputes and the evidence we gave (Terms 6.8); and the Terms version accepted at checkout, with the time, user, IP address and browser's user agent.
• Dispute evidence: if a charge is disputed, we may give the payment provider the order record above and records of the Organisation's use of Eddi (for example sign-ins, videos made, renders and AI usage, as counts and dates, not the content of its videos) to show the Service was ordered and used (Terms 6.8).
• How long: as long as the law on tax records requires, including after an Organisation is purged or a person's account is erased (9.1).

4. People who appear in footage

4.1 Organisations upload or connect footage, photos and audio that may show or name people: creators and influencers, customers, staff, and sometimes their families and children. Eddi transcribes what they say, describes what the clip shows, and may note their name or handle and personal details they mention (3.4), so the Organisation can find and use the clip in its videos. Their faces and voices may then appear in the Organisation's ads and other videos.

4.2 The Organisation is responsible (Terms 7.6, 7.7 and 14.2). For this content the Organisation is the controller and we are its processor (1.3). It must:

• have a lawful basis, and the consent (and, where needed, signed releases) of every identifiable person to appear in, and be edited into, marketing videos, including AI processing of their image and voice, and for minors the consent of a parent or guardian;
• give those people any notice the law requires, including that their footage is processed by Eddi and its providers (section 7);
• have the rights to the footage itself (for example under its agreements with creators and agencies);
• not use Eddi to make synthetic media of real people without their documented consent (Terms 11.4);
• handle requests from those people, and tell us when content must be removed.

We don't check consents.

4.3 If you appear in an Organisation's footage and want to know what is held about you, or want it corrected or removed, please contact that Organisation first: it decides what happens to its content. You can also write to us at [email protected]; we'll pass your request to the Organisation (where we can tell which one) and help it respond, as the law requires. If you believe content infringes your rights in your image, voice or work, you can also use the complaints procedure in Terms 12.

5. AI processing

5.1 Our AI model provider does Eddi's AI work. Eddi's editor, clip reviews, ideas, fact checks, website reading and draft reviews run on AI models from an AI model provider (named in 7.2). The main path is the Organisation's own AI provider account (5.3): for example its own Claude through Eddi's connector, or its own Anthropic API key, under its own agreement with that provider. Eddi's own account with our AI model provider, under the provider's commercial terms, covers the work that runs without the Organisation's own account: background work (for example indexing and reviewing footage in the library, and checks), usage included in free plans, and work when none is connected. Either way, for each task Eddi sends the AI provider what the task needs, which may include:

• your messages, comments and briefs, and the video's chat so far;
• the brand's guide, products, facts and style notes, and text, images and logos read from the brand's website;
• transcripts of footage (what people in it say, and their names or handles if they say them);
• frames, contact sheets and stills of footage and of drafts, so the AI can see what a clip or draft shows;
• clip reviews and library search results (which describe who appears and what they say);
• file names and folder names (which may include a creator's name).

For work on Eddi's account, we use an AI model provider whose commercial terms say it doesn't train its models on content received through its API, and that keeps API inputs and outputs only for a limited time, longer where needed to enforce its usage policy. Where it processes this data is shown in 7.2.

5.2 What runs on our own servers. Some processing runs on our own machines with open models, and that content doesn't leave our servers.

Our servers download these models' files, and fonts for videos, from public hosts when first needed; that sends no customer data.

5.3 The Organisation's own AI provider account (the main path). Eddi is built to run on the Organisation's own AI provider account, for example Anthropic's Claude ("Bring your own Claude"). An Organisation may add its own API key with that provider (for example an Anthropic API key), so its work runs on its own account under its own agreement with the provider, or use Eddi's connector from its own AI assistant (for example in the Claude apps), so its own assistant reads and changes its videos through Eddi's tools. In both cases what is sent to that provider, and whether the provider may use it for training, is governed by the Organisation's own agreement with it (for example with Anthropic); a personal plan may allow training if its user has opted in.

5.4 Other AI and media providers, as listed in section 7: the AI footage, voice and music providers the Organisation chooses to use (for voices, sound effects, music, online transcription, and AI images and video), only on the Organisation's own key. Paid use of them stays within the monthly limits the Organisation sets in Settings (Terms 6.4). These receive script text and prompts, and, for transcription, the clip's audio, or, for AI video, a reference image (which may be a frame of footage).

5.5 No training of AI models on customer content. We don't use customer content to train AI models, and we don't let providers that work on Eddi's own accounts train on it (Terms 7.5). Work on the Organisation's own AI account or keys follows its own agreement with that provider (5.3).

5.6 Improving Eddi itself. Eddi learns within each Organisation (its brand's style notes, lessons from its feedback), as part of the Service; that stays with the Organisation. We also use what Eddi learned from that work to improve Eddi's editing for all customers (its styles, checks and instructions): Eddi's work notes, check results and usage metrics (3.3, 3.6, 3.7), not the videos and footage themselves, including with AI tools (such as our AI model provider's models, on Eddi's own account). We don't train AI models on customer content, and our AI model provider doesn't train on Eddi's usage (5.1). An Organisation can opt out by writing to [email protected]; we then stop using its records for this. When an Organisation is deleted, its videos and footage are removed as in 9.1; only the improvement records (3.7) outlive it, for 12 months.

5.7 Google Drive (Google user data). If an Organisation connects Google Drive, this section applies to what Eddi receives from Google, and it comes before anything else in this policy that says otherwise.

• What Eddi can reach: only the files and folders you choose in Google's own picker, and files Eddi creates in that Drive. We also receive the connected account's name and email.
• What we use it for: only to provide and improve the features you use in Eddi: bringing your footage into the library, transcribing and reviewing it, editing it into videos, checking drafts, and saving videos back to your Drive.
• Who receives it: the providers that run those features: the AI model provider (5.1), and the hosting and storage providers in 7.2. By connecting Google Drive and choosing files, you agree to that. We may also share it where needed for security or to comply with the law, and in a merger or sale of the business only with your prior consent.
• What we never do: we don't sell it, use it or transfer it for advertising, transfer it to data brokers or information resellers, or use it to decide credit-worthiness or for lending.
• No AI training: we don't use it to create, train or improve any AI or machine learning model. To improve Eddi for all customers (5.6), we use what Eddi learned from the work, not the files themselves. Eddi's learning within your Organisation (its brand's style notes and lessons from its feedback) stays with your Organisation.
• People reading it: nobody at Eddi reads it unless you've explicitly agreed for specific files, it's needed for security (such as investigating a bug or abuse), it's required by law, or it has been aggregated and anonymised for internal operations.
• Keeping and removing it: what you've imported stays until it's deleted (section 9). Disconnecting Google Drive stops Eddi's access from Eddi's side; you can also remove Eddi at any time in your Google Account's security settings.

Eddi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API User Data and Developer Policy.

No automated decisions with legal effects. Eddi's AI makes creative choices in videos and suggests which footage to use; it doesn't make decisions about people that have legal or similarly significant effects on them. Decisions about who gets access, where access needs approval, are made by a person.

6. Why we use personal data, and on what basis

We don't sell personal data for money. In the app, we don't share personal data for cross-context behavioural advertising. On the website, when advertising tools load (2.3), the advertising platforms and networks we use (2.3) receive data about your visit to show you ads elsewhere; some US state laws (such as California's) may call this "sale", "sharing" or "targeted advertising". To opt out of this, use "Cookie settings" in the footer or send a Global Privacy Control signal from your browser; we'll stop loading these tools for you, without needing an account.

7. Who sees it, and who we share it with

7.1 Inside Eddi.

• Members of the same Organisation, within the brands they may access.
• A drive's own file picker, when you save a draft to your drive: it gets a short-lived signed link to that draft's file.
• Our administrators, as in 3.10.
• Organisations never see each other's data, or that other Organisations exist.

7.2 Providers. We share personal data only with the providers that help us run the website and the Service (for the app, our "sub-processors"), with providers the Organisation chooses to connect, with the advertising platforms and networks we use (2.3) through their tools on the website, when the law requires, or, with notice, when we transfer Eddi to a company we form to run it, an affiliate or a successor to the business (for example in a sale, merger or reorganisation; Terms 23.2). Each gets only what its task needs. This list is where this policy names our providers; elsewhere it describes them by their role (for example "our AI model provider"). Each provider's own privacy and cookie policies apply to what it handles as its own controller. The app's providers below were checked against its code on 2026-10-30. Advertising platforms and networks have one row each for those we use; when we start or stop using one, its row is added to or removed from this list. This list may change; we keep it current at goeddi.com/providers. For providers that receive customer content in the app (sub-processors), we give notice of changes as described in Terms 14.4.

7.3 Not used in the app today: analytics, error-tracking, support-chat or advertising services. If we add product analytics or support chat, we'll ask for consent where the law requires it and list the provider in 7.2. Our own open-source models run on our own servers (5.2) and aren't providers.

The list in 7.2 is published at goeddi.com/providers and kept current there (decided 2026-10-31); changes to the app's sub-processors follow Terms 14.4.

8. International transfers

8.1 We are in the Philippines. Data is stored and processed on our servers and our providers' servers, which may be in the Philippines, Singapore, the United States, the EU or other countries; 7.2 shows each provider's location. Many of the providers in 7.2 process data in other countries, mostly the United States; the "Leaves PH/SG?" column there shows which. Data leaves the Philippines when, for example:

• Eddi sends work to our AI provider (5.1): this happens for every video;
• the off-site backup and footage copies go to our backup and storage provider;
• traffic to the app and to the website passes through our network, hosting and content delivery providers' global networks;
• request logs are stored with a monitoring provider;
• the website's booking tool and email service provider handle demo bookings and waitlist sign-ups;
• advertising or analytics tools load on the website, which send data to their platforms, mostly in the United States (2.3);
• the Organisation uses providers it connects (voice, AI media, drives), mostly in the United States;
• a buyer pays for a plan through our reseller and Merchant of Record (3.11), and we send it refund requests or dispute evidence.

8.2 Where the law requires, we rely on safeguards such as the provider's data processing terms and standard contractual clauses.

9. How long we keep it, and deletion

9.1 In the app. Accounts and Organisations are removed on request, by our administrators; there are no self-service delete buttons for them, and no automatic deletion timers except where shown. One such timer: an Organisation on a free (unpaid) plan that nobody has signed in to for 1 year is deleted automatically (Terms 16.6). The year counts from the later of the last sign-in by any of its members and the day it moved to the free plan. We email its members 30 days and 3 days before; a sign-in, or moving to a paid plan, stops it. Not paying, or cancelling, never deletes anything by itself: it only moves the Organisation to the free plan (Terms 6.3a). The deletion is a purge, as in the table below.

9.2 Deleting something in Eddi doesn't delete it from the Organisation's own drive or from providers it connected with its own account; manage those with the provider. Providers that worked on Eddi's account keep data under their own terms (for our AI model provider, see 5.1).

9.3 We may keep data longer where the law requires, or to resolve disputes or enforce our agreements.

10. Security

We protect personal data with measures that include:

• Sign-in: passwords stored only as salted hashes; the sign-in cookie protected against use by scripts and other sites, and sent only over HTTPS; sign-in, invite, reset and connector tokens stored only as hashes; everything in the app needs a sign-in except what must be reachable without one (signing in, invite and reset links, access requests, health checks, and short-lived signed links); anything new is closed unless opened on purpose.
• Sealed keys: API keys, bucket keys and drive tokens encrypted at rest; never shown back in full.
• Per-Organisation isolation: every request is checked against the Organisation and brands the person may access, and anything outside them answers "not found"; live updates go only to those allowed to see them; files are stored per Organisation; each AI session can be run in its own sandbox that sees only its Organisation's files. AI sessions are told that footage, websites and comments are data, not instructions.
• Connections: HTTPS to the app.
• Administration: our administrators' visits and changes in Organisations are recorded in the audit log; failed sign-ins are recorded.
• Payments: made in our payment provider's checkout; we never receive or store card numbers or other payment credentials, only the provider's identifiers and the payment's status; its webhooks are checked for their signature before the app acts on them.
• Backups: an off-site copy with our storage and backup provider.

No system is completely secure. If a breach affects your personal data, we'll notify you and the authorities as the law requires; where we are an Organisation's processor, we'll tell the Organisation without undue delay.

11. Your rights

11.1 Under the Philippine Data Privacy Act (RA 10173, Sec. 16–18) you have the right to: be informed that your data is processed; access it; object to processing (including withdrawing consent); have it corrected; have it erased or blocked; data portability (a copy in a commonly used electronic format); claim damages; and file a complaint with the National Privacy Commission (privacy.gov.ph).

11.2 Under the GDPR and UK GDPR, if they apply to you: access, rectification, erasure, restriction, objection (including to processing based on legitimate interests), portability, withdrawing consent, and complaining to your supervisory authority (in the EU, your local authority; in the UK, the ICO). California and other US state laws may give rights to know, delete, correct and opt out of sale or sharing (on the website, through "Cookie settings" or Global Privacy Control; see section 6), and not to be discriminated against for using these rights.

11.3 How to ask. Write to [email protected] (or another contact method we publish). We handle requests by email: we'll verify your identity, act on the request (for deletion, as in 9.1) and answer within 30 days.

11.4 If you appear in a business's footage, your request goes to that business first, as in 4.3; we'll pass it on and help it respond.

12. Children

Eddi and the website are for businesses and professionals and are not for anyone under 18 (Terms 3.2). We don't knowingly collect personal data from children through the website or app accounts. Children may appear in footage an Organisation brings in: the Organisation must have a parent's or guardian's consent (4.2), and the clip review notes when children appear so they can be avoided. If you believe a child has given us personal data, contact us and we'll delete it.

13. Changes to this policy

We may update this policy. We'll post the new version with its date, and for material changes we'll tell account holders by email or in the app at least 30 days before they take effect.

14. Contact

Vernard Alexis Luz, provider of Eddi (goeddi.com)
115 GF Future Point Plaza 2, Mother Ignacia Ave., South Triangle, Quezon City 1103, Philippines
Privacy contact: [email protected], or another contact method we publish
Data Protection Officer: Vernard Alexis Luz, [email protected]

Cookie notice

In the app: Eddi uses only the cookies and browser storage needed to run it: to keep you signed in and secure (strictly necessary), and to remember your preferences on your device. Today it sets only its sign-in cookie, and has no analytics, advertising or tracking cookies. If we later add product analytics or support chat to the app, we'll ask for your consent where the law requires it, and list the provider in 7.2.

When you pay: the checkout opens on our payment provider's own hosted page, and the billing portal is the provider's too; neither is embedded on our site or in the app. The checkout page sets the provider's own cookies, under its cookie policy (linked from 7.2), which may include strictly necessary cookies (security, sessions, fraud prevention) and advertising and marketing cookies. Eddi itself sets no cookie for payments.

On the website: goeddi.com uses cookies and similar technologies (such as pixels and browser storage) in the categories below. Where the law requires your agreement first (such as the EU and the rest of the EEA, the UK and Quebec), it asks for your choice in a consent banner (accept, reject, or choose). Elsewhere, or if we can't tell where you are, analytics and advertising tools load by default and you can turn them off (2.3):

• Strictly necessary (always on): what the site needs to work and stay secure, such as remembering your cookie choice and protecting the forms from abuse.
• Preferences (if any): remembering choices you make on the site.
• Analytics (with consent, where the law requires it): understanding how the site is used, if we use analytics.
• Advertising (with consent where the law requires it; elsewhere on by default, and you can turn it off): advertising and measurement tools (pixels, tags and similar) from the advertising platforms and networks we use: social, search, video and display advertising, including ads shown to you on other websites and apps (retargeting). They measure our ads and help show ads to people who visited (2.3).

Changing your choice: use the "Cookie settings" link in the footer, there while the site uses these tools, at any time; your choice is stored in your browser, and tools you turn off stop loading from the next page. A browser sending a Global Privacy Control signal is treated as having turned them off. The demo booking tool loads only when you open the booking page or start booking a demo, and then sets its own cookies. Each provider's own privacy and cookie policies describe its cookies; the providers are listed in 7.2 (also at /providers). Our payment provider's checkout isn't on the website (see "When you pay").