Privacy Policy

Desktop application

Web application and cloud projects

ChatGPT, Codex and MCP connections

Users aged 13–17 and parental consent

Who We Are and What This Policy Covers

Information We Handle

• Account information, including name, email address, authentication identifiers, account settings, plan, and acceptance records.
• Billing information, including subscription status, invoices, payment-provider customer identifiers, credits, usage totals, taxes, refunds, and payment history. Card details are handled by payment providers rather than stored directly by Embedr.
• Project content, including source code, schematics, PCB layouts, project files, documents, prompts, tool results, AI responses, and other context submitted to the service.
• Technical and operational metadata, including timestamps, selected model, token and cost totals, request status, error status, account identifier, application version, device and browser information, IP address, and security or abuse signals.
• Analytics and diagnostics, including feature usage, navigation, performance information, crash reports, console errors, and session recordings where enabled.
• Support and communications, including contact-form submissions, support tickets, bug reports, feedback, attachments, and transactional or marketing-email records.
• Publishing and sharing information, including project visibility, invited collaborators, public attribution, remix settings, and user-selected open-source or content licenses.

Free: Mandatory Improvement and Training Use

• Eligible content includes cloud-stored project files, prompts, code, project context, tool results, AI responses, and other AI traces.
• Embedr removes account links and personal details from eligible content before placing it into improvement or training workflows. Users should still avoid placing passwords, private keys, regulated data, or unnecessary sensitive personal information in training-eligible content.
• Authorized Embedr employees and contractors may review de-identified samples for labeling, evaluation, debugging, safety, and quality control.
• Eligible content is used only to improve Embedr and train Embedr-owned AI systems. It is not sold, and third-party model providers are not permitted to use it to train their general models.
• Training is mandatory for Free and cannot be disabled while remaining on the Free plan.
• Support tickets, contact messages, bug reports, and feedback attachments are not treated as training content unless the user separately and expressly submits the same material as project or AI content.

Hobby and Pro: No AI Request Logging or Training

• Prompt bodies, source code, project context, tool results, and AI response bodies sent through Hobby or Pro AI requests are not retained in AI request logs and are not used for model training or product improvement.
• Limited non-content metadata may be retained for billing, cost accounting, security, abuse prevention, reliability, and legal compliance. This can include timestamps, model, token or cost totals, status, errors, and account identifiers.
• Cloud project files remain stored and accessible until the user deletes them. Hobby and Pro protect those private cloud files from training while the plan remains active.
• Session recording is disabled completely on Hobby and Pro.
• Hobby and Pro content is treated as confidential and is disclosed only to service providers needed to operate the service, to people authorized by the customer, or where disclosure is legally required.

What Happens When a Paid Plan Ends

• Embedr will provide at least seven days’ notice before a scheduled paid-plan expiration. Failed payments receive a seven-day grace period.
• Hobby and Pro protections remain in effect until the plan actually expires. After expiration and downgrade to Free, all cloud project files remaining in the account—including files created while the paid plan was active—become eligible for Embedr improvement and training use.
• A user who does not want existing paid-plan project files to become training-eligible must delete those files before the plan expires.
• Content from AI requests made while a paid plan was active is not retroactively logged because Embedr did not retain those request bodies.

Publishing, Private Sharing, and Marketing

• Projects shared only with specific invited people remain private and are not training-eligible while protected by a paid plan.
• A project deliberately published to the public becomes training-eligible regardless of plan.
• Embedr may feature public projects in galleries, newsletters, social media, and other marketing with attribution.
• If a user unpublishes or deletes a project, the public copy is removed and Embedr stops using it in future marketing. Previously published social posts, newsletters, archived campaigns, and de-identified training artifacts may remain.
• Other users may copy or remix a public project only when the publisher enables remixing and selects a license that permits it. If no license is selected, no permission to copy or remix is granted.

Session Recording and Analytics

• Session recording is enabled by default for Free. The onboarding flow presents the setting, and users may turn it off in the application settings.
• Recorded areas are configured so that project source code, project names, file paths, terminal output, and user prompts are not visible. AI responses may be visible.
• Session recordings are used for product quality and debugging, not AI training, and are retained for 30 days.
• Session recording is disabled for Hobby and Pro.
• Embedr uses analytics and diagnostic services, which may include Firebase/Google Analytics and PostHog depending on the product surface and version. These services help measure usage, performance, failures, and feature adoption.

How We Use Information

• Provide, authenticate, personalize, maintain, and secure the service.
• Store and synchronize cloud projects and carry out sharing or publishing choices.
• Route AI requests, run tools, calculate usage, and provide model output.
• Administer subscriptions, credits, overages, invoices, refunds, and taxes.
• Investigate failures, prevent abuse, monitor security, and improve performance.
• Provide support and respond to legal or privacy requests.
• Comply with law, enforce agreements, and establish or defend legal claims.
• Improve Embedr and train Embedr-owned AI systems where the applicable plan or publication choice permits it.

Service Providers and International Processing

Email Communications

• Account, security, billing, usage, cancellation, and service emails are transactional and may be sent when needed to operate the account.
• Users are added to Embedr marketing communications by default. Every marketing email includes a one-click unsubscribe mechanism.
• Unsubscribing from marketing does not stop transactional messages.

Retention and Account Deletion

• Account data and private cloud projects remain available until the user deletes them or deletes the account. Paid-plan cancellation alone does not delete projects; users may continue using the platform manually.
• Self-service account deletion is scheduled for the end of the current paid billing period. Support can process immediate account deletion on request.
• After deletion takes effect, personal data and private cloud projects are removed from active systems. Backup copies expire within 30 days, unless a longer period is legally required.
• For Free users, and for training-eligible public projects, de-identified prompts, code, project context, outputs, AI traces, evaluation records, and model improvements may be retained indefinitely after account or project deletion. They are no longer linked to the deleted account.
• Session recordings are retained for 30 days; crash reports for up to six months; console and debugging logs for up to 30 days; and product analytics for up to 12 months unless de-identified earlier.
• Billing, tax, fraud-prevention, security, consent, and legal records may be retained for the period required by law or reasonably needed to resolve disputes and enforce agreements.

User Choices and Rights

• Users can correct profile information, manage sharing, delete projects, disable Free session recording, unsubscribe from marketing, and request account deletion.
• Depending on applicable law, users may request access, correction, deletion, restriction, objection, consent withdrawal, or portability of personal data and may lodge a complaint with an appropriate regulator.
• Embedr may verify identity before completing a request and may retain information where required by law. Privacy rights do not require Embedr to remove de-identified AI traces or reverse model learning where applicable law does not require that result.

Security

Age Eligibility and Policy Changes

• Users aged 13–17 require an adult parent- or guardian-managed account and consent, as described above. Users under 13 are not permitted.
• We may update this policy as the service or law changes. Material changes will be communicated through the service, by email, or both before they take effect where required.
• We will not retroactively expand training rights over content that was protected by a paid plan while that plan was active. Content remaining in the cloud can become training-eligible only after the paid plan actually ends under the plan-transition rules above.