Privacy

Your work deserves clear boundaries.

This notice explains what Edy processes, why we need it, and what happens when AI services and connected tools help complete your work.

Effective August 23, 2026

In plain language

Edy needs to send relevant content to AI and integration services to do the work you request. Their policies vary, so avoid sharing information you do not need the service to process.

Information Edy handles

We process the information needed to operate Edy, including:

  • Account details such as your name, email address, and authentication records.
  • Prompts, chat history, uploaded files, project source code, generated output, and project settings.
  • Usage and technical data such as model choice, token usage, request timing, device information, IP address, errors, and security events.
  • Credit purchases and payment status. Payment credentials are handled by our payment service; Edy does not store full card or mobile-money credentials.
  • Connector authorization data, configuration, and service metadata for integrations you choose to connect.
  • Feedback you submit. If you choose anonymous feedback, we do not attach your Edy account to that submission.

How we use information

We use this information to provide and improve Edy, generate responses and software, save your work, operate integrations, process credit purchases, prevent abuse, diagnose failures, provide support, and meet legal obligations. We do not sell your personal information.

AI processing

When you use Chat or Code, Edy sends the prompt and the context needed to answer it—such as relevant conversation history, files, or project code—to the AI services needed to complete your request. Processing may take place in other countries.

Data practices differ between AI services. Depending on the selected model, endpoint, and privacy settings, inputs and outputs may be retained or logged for abuse monitoring, legal compliance, service operation, or model improvement.

We may use prompt caching to improve speed and cost. Cached prompt prefixes can be held temporarily by AI infrastructure. Do not submit secrets or sensitive personal information unless it is necessary for your task and you are authorized to share it.

Integrations and supporting services

When you connect services such as Supabase, GitHub, or Vercel, Edy uses the authorization you grant to perform the actions you request. Those services receive data according to the task and their own privacy terms. Edy also relies on infrastructure, database, hosting, security, analytics, and payment services that process limited data on our behalf.

Retention and deletion

We keep information for as long as needed to provide the service, maintain security and billing records, resolve disputes, and satisfy legal obligations. Retention periods vary by data type and service. Deleting a project or chat removes it from your active account, but backups, fraud-prevention records, payment records, or third-party logs may remain for a limited period.

Your choices

You can delete chats and projects, disconnect integrations, avoid uploading sensitive material, and submit product feedback anonymously. To request access, correction, export, or deletion of account information, use the in-product “Where can we improve?” control and clearly label the message as a privacy request. We may need to verify your identity before completing a request.

Security, children, and changes

We use technical and organizational safeguards designed to protect information, but no online service can guarantee absolute security. Keep your account credentials private and disconnect an integration if you believe access has been compromised.

Edy is not directed to children under 13, and users must meet the minimum age required in their country. We may update this notice as Edy, our supporting services, or legal requirements change. Material changes will be identified by a new effective date or an in-product notice.