Privacy Policy

Separately from the product described below: yedran.com itself collects one thing — the email address you enter to join the closed-beta waitlist. The site sets no cookies and runs no analytics or tracking scripts, so that email is the only data it has about you.

That address is relayed by email to an internal Deep Blue Coding inbox so we can invite you when there is room for your team. It is not written to a database, not shared with any third party, and not used for anything beyond that invite. Write to hello@deepbluecoding.com to have it deleted before we’ve been in touch.

Everything from here on describes how the Yedran product itself handles data once a business has an account and connects a channel — not this website, which has neither.

Yedran is used by businesses. A business that connects a mailbox or a messaging account is the controller of the conversations that flow through it; Deep Blue Coding processes that data on its instructions. If you are an end customer who wrote to a business using Yedran, address requests about your data to that business.

• Messages. The content of messages sent to and from the connected account, with sender name, address or handle, timestamps and attachments.
• Account holders. Name, email address and role of the agents who sign in to Yedran.
• Connection credentials. OAuth refresh tokens and channel secrets, encrypted at rest.
• Knowledge base. The documents a business uploads so the assistant can answer from them.
• Operational records. Logs and metrics about requests, model calls and errors. These record that a message was handled, not what a customer said, beyond what is needed to debug a failure.

When a business connects a Gmail or Google Workspace mailbox, it grants Yedran the https://mail.google.com/ scope. We use it for exactly two things: reading incoming mail in that mailbox so the assistant can answer it, and sending replies from that mailbox. Message content is stored in the business’s Yedran workspace so the conversation history is available to its agents. The refresh token is encrypted before it is written to our database and is never displayed, exported or logged.

We do not use Gmail data for advertising, we do not sell it, we do not use it to train generalised machine-learning models, and no human at Deep Blue Coding reads it except with the business’s explicit permission to resolve a specific support issue, or where required by law.

Yedran’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

A business can disconnect a mailbox at any time from its Yedran channel settings, or revoke Yedran’s access directly at myaccount.google.com/permissions. Revoking access stops all further reading and sending immediately.

Message content is sent to third-party language-model providers to generate a reply, and to a vector database to retrieve relevant knowledge-base passages. These providers process the content to return a result and are contractually barred from using it to train their models. We do not share data with anyone else except where the law requires it.

Conversation data is retained for as long as the business keeps its Yedran workspace. On termination, or on written request, we delete the workspace and its conversation data within 30 days, except where a legal obligation requires us to keep a record for longer. Credentials are deleted as soon as a channel is disconnected.

Credentials are encrypted at rest with keys held outside the database. Access to production systems is limited to the engineers who operate the service and is authenticated individually. Data is transmitted over TLS.

Depending on where you live you may have the right to access, correct, export or delete your personal data, and to object to its processing. Write to us and we will answer within the period the applicable law allows. If you are an end customer of a business using Yedran, we will forward your request to that business.

Deep Blue Coding — hello@deepbluecoding.com