Draft: this notice is awaiting legal review and may change before it becomes final.

Privacy

Last updated 30 October 2026

YourEngineers gives your team AI engineers that work alongside you: in chat, in your delivery workflow and in meetings. To do that we handle your team's work and some personal data. This page says what we hold, why, who else sees it, how long we keep it, and how you can take it with you or have it deleted.

Who we are

YourEngineers is run by Cofield AI Limited, a company registered in Nigeria. For anything about your data, email [email protected].

For the work your team does on YourEngineers, your organisation decides what goes in and we process it on its behalf. For running our own business (your account, billing, keeping the service safe) we are responsible for the data ourselves.

What we hold

  • Your account and team: names, email addresses, roles, and the Slack, GitHub, GitLab or Bitbucket usernames your admins add so engineers know who's who.
  • Your team's work: chats with engineers (in our portal and in Slack), deliveries and their steps, pull requests engineers open, meeting notes and follow-ups, workflows, settings, and the record of which files were shared.
  • Connections to your tools: the access each connection needs (tokens, keys, database connection details). These are encrypted when stored, and engineers use them through a vault without ever seeing them.
  • Feedback you send us: what you write, the rating you give, the page you sent it from, and your name and email so we can reply if you allow it.
  • Usage and billing: how much engineer time and AI use your workspace consumes, credits, plans and payment references.
  • Safety and audit records: a log of important actions (who approved what, connections made, settings changed), messages our safety checks flagged or blocked, and, for database queries an engineer runs, the query and how many rows came back.

What we don't keep

  • Meeting transcripts and shared screens. While an engineer is in a meeting, what's said and any screen shared are held in memory only, never written to our database. We keep the meeting notes and follow-ups the engineer writes.
  • Database query results. When an engineer reads from a database you connected, the rows go to the engineer, not into our storage.
  • Files you share are deleted from our AI provider once their conversation ends.
  • Card numbers. Payments are handled by Paystack and Stripe.

How we use it

  • To run your engineers and the work you give them.
  • To keep the service safe: every message to an engineer is checked for misuse, and the riskiest actions (deleting things, touching secrets or keys, changing who has access, billing) always need a person's approval. How much else needs one is your workspace's choice.
  • To bill you, and to tell you what you're spending.
  • To support you when you ask, and to keep the service working.

We never use your data to train AI models. Our AI provider processes it under commercial terms that don't permit training on it. We don't sell your data, and we don't use it for advertising.

Chat monitoring

Workspace monitoring is on by default. It reads the messages people send to engineers (not the engineers' replies) to spot off-topic use, abuse or waste, and emails your workspace's alert address with a short excerpt when something is flagged. Owners and admins can see flagged messages and the chat log on the portal's Monitoring page, and can turn monitoring off there. The separate safety check on every message can't be turned off.

Who else sees it

We use these providers to run the service. Each handles only what it needs:

ProviderWhyWhat it handles
AnthropicRuns the AI engineersWhat you and your engineers say and do in chats, deliveries and meetings; files you share; engineers' working memory; the credentials of tools you connect, held in a vault so engineers can use them without seeing them
RenderHosts our servers and databaseEverything we store (listed above)
VercelHosts this website and portalPages you load, and requests on their way to our servers
ClerkSign-in and organisationsYour name, email and sign-in details
Recall.aiJoins meetings you invite an engineer toThe meeting's audio, video and transcription while the engineer is in it
ElevenLabsGives engineers a voice in meetingsThe text an engineer says aloud
ResendSends our emailsYour email address and the email's contents (alerts, meeting notes, billing notices)
Paystack and StripePaymentsBilling details you give them; we never see or store card numbers

Tools you connect (Slack, GitHub, GitLab, Bitbucket, Jira, Confluence, Google Drive, Notion, Figma, cloud and monitoring services, databases) receive what your engineers do there, under your own accounts with those providers. Several of our providers are based outside Nigeria, mainly in the United States, so your data is transferred there, with the safeguards the law requires.

Your controls

  • Take a copy at any time. Workspace owners can download everything we hold for the workspace from Settings, as one file. Secrets (connection credentials, anything stored encrypted) are left out.
  • Disconnect any tool. Owners and admins can disconnect each integration from the Integrations page. We delete our copy of its access straight away; to remove an app from the provider's side as well, the page tells you where.
  • Leave, and have your data deleted. When an owner off-boards the workspace, engineers stop at once and every connection's access is revoked. Thirty days later the workspace's data is deleted. Until then you can ask us to restore it.

How long we keep it

  • While your workspace is active: for as long as you use it, so your team's history stays available.
  • After off-boarding: 30 days, then deleted.
  • Kept after deletion: billing and payment records, and a minimal record of billing and account events, for as long as tax and accounting law requires. We also keep a fingerprint (never the number) of cards used for free trials, to prevent trial abuse.
  • Files you share: deleted from our AI provider once their conversation ends.

How we protect it

  • Connection credentials are encrypted when stored, and engineers use them through a vault without seeing them.
  • Engineers are blocked from dangerous actions: force-pushing, pushing straight to main, merging pull requests, revealing secrets. Deleting things, touching secrets or keys, changing access and billing always need a person's approval, whatever the workspace's settings.
  • Secrets that turn up in an engineer's messages are masked before anyone sees them.
  • Access in the portal follows roles (owner, admin, member), and important actions are recorded in an audit log.

Your rights

Under Nigeria's Data Protection Act 2023 and, where it applies, the EU and UK GDPR, you can ask to see the personal data we hold about you, correct it, delete it, take a copy, object to or restrict how we use it, and withdraw consent where we rely on it. Email [email protected]; we'll reply within 30 days. If your data is part of your organisation's workspace, we may involve its owner. You can also complain to the Nigeria Data Protection Commission, or to your local data protection authority.

Changes

If we change how we handle your data, we'll update this page and its date, and tell workspace owners about significant changes before they take effect.