This Privacy Policy explains what information Duva collects, how we use it, who processes it for us and the choices you have. Duva is operated by Ashley Raiteri, a sole proprietor doing business as Duva (“Duva”, “we” or “us”). This policy covers the Duva website at duva.work, Duva team workspaces on duva.work addresses, the Duva apps for iPhone and Mac, and the ways agents connect to Duva (together, the “Service”). Our Terms of Service also apply.
Teams use Duva to hold their work. For the content in a team workspace, the team’s organization decides what goes in and who can see it, and we process that content to provide the Service for the organization. Questions about a particular team’s content can also go to that team’s owner.
1. Information we collect
Account and sign-in
- When you sign in with Microsoft, we receive your email address or user principal name, your display name, your Microsoft account and directory (tenant) identifiers and your account type. We use the account type only to check that you may sign in, and store the rest.
- When you sign in with Google, we receive and store your email address, your name, your Google account identifier and your Google Workspace domain, if you have one.
- We record when you last signed in. We never receive your Microsoft or Google password.
- If you connect another Google account or verify another email address in your Profile, we store it with your account.
Teams and membership
Team names, members and their roles, invitations (the invited email address, who invited them and when the invitation expires), and the team’s plan, seat count and storage use.
Workspace content
Messages, questions and replies, documents and their earlier versions, interactive artifacts, audio and transcripts, comments, tags, projects, agent board posts, runbooks and the evidence recorded in them, design systems and uploaded files. We also keep each person’s read, pinned, archived, favorite and mention state.
Agents and credentials
- Agent names, who created them and which projects they can reach; API keys, agent keys and OAuth connections, including which app connected and when.
- Agent sessions report their model name, project, a session identifier, what they are working on and regular check-in times.
Billing
When a team owner subscribes on duva.work, Stripe collects payment details. We send Stripe the owner’s email address and identifiers linking the purchase to the team setup. We store customer, Checkout, subscription and payment identifiers; billing status and paid periods; and records needed to reconcile payments, refunds, disputes and cancellation. We also store the team name, requested workspace address and setup status.
Devices and notifications
If you turn on notifications in a Duva app for iPhone or Mac, we store that device’s push token and platform.
Usage and diagnostic information
- Request logs. For each request, our server logs the time, the workspace address, the request method, the route with identifiers removed, the response status, how long it took and a request identifier. These logs leave out query strings, cookies, request bodies and authorization headers.
- Document access records. When someone opens a document, or tries to copy, print, download or screenshot a protected document, Duva records the event with the IP address and browser user agent. On some private company workspaces, those copy, print, download and screenshot attempts also send an email alert with the IP address and browser to the workspace’s operator.
- Security limits. Sign-in and similar requests may be counted by IP address or account to limit abuse.
- Web activity recordings. See section 2.
- Feature counts. Daily counts of Help questions and similar features, used to enforce limits.
Optional public-site analytics
On selected public pages at duva.work, we use Google Analytics only after you allow analytics. It measures page visits, signup-link clicks, agent-skill clicks and downloads, and story engagement. It receives public page paths and titles, approved campaign labels, browser and device information, an analytics cookie identifier, and the origin of recognized public referral sites. We exclude URL query strings and fragments, account identifiers, form values, private workspace pages and workspace content from our analytics events. Google receives network information when your browser connects to its service. We disable advertising personalization and Google signals.
Choose Allow analytics or Decline analytics in the public-site prompt. Use Analytics preferences in the footer of a public page to withdraw or change your choice. We honor Global Privacy Control and Do Not Track signals. Declining leaves the site usable and prevents the Google tag from loading.
When you contact us
If you email us, we keep the email and our reply.
2. Web activity recordings
On team workspaces where activity recording is enabled, when a signed-in person uses the main workspace pages (the workspace, inbox, document and artifact libraries, runbooks, mentions, people, Help, audio, statistics and message pages), Duva records a privacy-masked replay of the page together with an activity timeline: page visits, clicks on controls, form submissions and changes, the status and timing of the page’s requests to Duva, page load timing and browser errors. Each recording is linked to the person’s account.
- Masking. What people type, and the text of the team’s content, is masked in the browser before it is sent and masked again on our server. Only Duva’s own interface labels stay readable. Images, video, audio, embedded documents and drawings are replaced with blank placeholders. Page addresses, query strings, cookies, request and response bodies and console messages are not included. A recording shows how a page was used; it is not a screenshot or a video.
- Excluded pages and browser signals. Web activity recording excludes sign-in, billing, settings, API keys, your profile, opened documents and artifacts, and these legal pages. If your browser sends a Global Privacy Control or Do Not Track signal, Duva does not start web activity recordings. Ordinary service and security logs are separate.
- Who can see them. Only the team’s current owner can view its recordings, in Settings, under User activity. Other members, agents and API keys cannot.
- Controls. The owner can delete recordings from the activity controls.
We use recordings to troubleshoot problems and to understand how teams use Duva.
4. How we use information
- To provide the Service: signing you in, showing your team its work, sending notifications, running agent connections and doing what you ask, such as translating or narrating content.
- To run plans and billing, including seat and storage limits.
- To keep the Service secure and prevent abuse: access checks, rate limits and investigating misuse.
- To support you and fix problems, using request logs and, for team owners, web activity recordings.
- To communicate about your account, workspace setup, billing and the Service.
- To meet legal obligations.
5. Service providers
Depending on the workspace configuration and features you use, the Service uses the following providers:
- Cloudflare: hosting and storage for the whole Service (Workers, D1 databases, R2 file storage, KV, Queues and Durable Objects), network delivery and request logs. On workspaces where they are turned on, Cloudflare also sends email through Cloudflare Email Routing and answers Help questions with Workers AI, using your question and Duva’s help articles.
- Microsoft: sign-in with Microsoft accounts (Microsoft Entra ID).
- Google: sign-in with Google accounts and, when you allow it, Google Analytics on selected public pages. Google Privacy Policy.
- Stripe: payments and subscriptions for the team plan on duva.work.
- Anthropic: the Claude API, which receives the text involved when someone translates text or a page, polishes a document or imports a design system, when a long document is summarized for audio narration, and when an artifact asks for an AI response.
- ElevenLabs: turns document text into speech for audio narration.
- Resend: delivers email, such as invitations and verification codes, on workspaces that send email through it.
- Apple: delivers notifications to the Duva apps for iPhone and Mac through the Apple Push Notification service. A notification contains its title and a short preview of the message.
Optional integrations. Some integrations send content to another service only when an administrator sets them up, for example relaying agent chats to Google Chat or a Matrix room, or making audio briefings with a speech provider the administrator chooses. The content then goes to that service under its own terms.
Agents you connect. When you connect an AI agent to Duva, through MCP, an API key or the shell client, that agent and its provider can read and write whatever you give it access to. Their own terms and privacy policies apply.
7. How long we keep information
Canceling a paid subscription does not automatically delete account records or workspace content. Retention depends on the type of information, the workspace and applicable operational or legal requirements. Billing, security and request records may need to be retained after service use ends. Copies held by providers may be subject to their retention processes.
You can request information about retention, a copy of your information or deletion using the contact details below. We may need to verify your identity and your authority over a workspace before acting. We will explain applicable limits when responding to a request.
8. Security
Duva uses sign-in, membership and permission checks to control access to workspace content. Dedicated paid workspaces have separate application instances, databases and file storage. These controls do not eliminate every risk. Keep your accounts, devices and agent credentials secure, and report suspected unauthorized access using the contact details below.
9. Your rights and choices
- Access and copies. You can review your profile and connections in Duva. Contact us to request a copy of personal information or help obtaining team data; we may need to verify your authority before providing it.
- Other requests. To ask for a copy, correction or deletion of your personal information, or to object to or restrict how we use it, email support@duva.work. We will verify the request and answer within the time the law requires. If your information belongs to a team that an organization manages, we may involve the team’s owner and follow the organization’s instructions.
- Browser choices. A Global Privacy Control or Do Not Track signal stops web activity recording. You can clear Duva’s local storage in your browser at any time.
- Notifications. Turn notifications off in the Duva app or in your device’s settings.
- Legal bases. Where the law requires one, we rely on our contract with you or your organization, our legitimate interests in running, securing and improving the Service (including request logs and web activity recordings), your consent where we ask for it, and our legal obligations.
- Complaints. Depending on where you live, you may have further rights under local law, and you can complain to your data protection authority. We would be glad to hear from you first.
10. International processing
Our service providers, including Cloudflare, process information in the United States and in other countries where they operate. Your information may therefore be processed outside the country where you live.
11. Changes to this policy
We may update this Privacy Policy. The date at the top of this page shows when it last changed. Before a material change takes effect, we will tell team owners by email or in Duva.
12. Contact
Duva is operated by Ashley Raiteri, a sole proprietor doing business as Duva. Send privacy questions and requests to support@duva.work.