About this list
This draft names the providers that the Dynodoc code and deployment configuration actually use. It was checked against the repository on 12 October 2026 and is not an executed agreement. A provider is listed only if it is configured; hosting details that the operator has not yet confirmed are marked as such rather than guessed.
“Subprocessor” here means a provider that handles information on the operator’s behalf to run the service. Providers you choose yourself, such as your sign-in provider, are listed separately. For how information is used and kept, see the privacy policy; for the draft processing structure, see the data processing terms.
Providers that handle data
| Provider | Role and purpose | Information involved | Location |
|---|---|---|---|
| Hosting provider of the workspace server (name awaiting confirmation) | Runs the workspace, API, database, document converter and backups on a rented virtual server. | All service data: account records, document content and history, original uploads, audit records, logs and backups. | Awaiting confirmation. |
| Vercel Inc. | Serves the public website at dynodoc.online. | IP address, requested address and browser details for public-page requests. The website deployment is configured with only the public workspace address and has no database. | Per Vercel. |
| Resend | Delivers transactional email: sign-in links and invitations. Used when configured. | Recipient address, the sender’s name and reply-to address for invitations, and the message, which contains a link and a file or project name. | Per Resend. |
| Google (your choice) | Optional sign-in with Google, limited to identity, email and profile; and the optional read-only Google Forms import. Not a Drive, Docs or Sheets integration. | Your Google account identifier, name and email address are passed to Dynodoc; for a Forms import, requests for the form you select. | Per Google. |
Editor platforms
The add-ins run inside products from Microsoft and Google. These are the host platforms you choose to use, not Dynodoc subprocessors, and they apply their own terms and privacy practices.
- Microsoft: Word, Excel and PowerPoint panes load Microsoft’s Office.js library from appsforoffice.microsoft.com and run in Office’s embedded web view. The page security policy permits only Microsoft’s Office.js hosts in addition to Dynodoc’s own origin.
- Google: Docs, Sheets and Slides add-ons run on Google Apps Script. Their stored queue and key sit in Apps Script user properties, requests leave only to the Dynodoc connector address, and Google may log execution errors because exception logging is enabled.
What each add-in reads, stores and sends is described under editor add-ins in the privacy policy.
Infrastructure that sees no content
- Let’s Encrypt: issues the TLS certificates for the workspace and administration hostnames. It receives domain names, not user information.
- Domain registrar and DNS: provider awaiting confirmation. It holds the domain records, not user information.
- GitHub: hosts the source code and runs the automated tests, which use synthetic data only. It receives no customer content.
What is not used
- Analytics, advertising networks, tag managers or social widgets.
- Third-party fonts, scripts, stylesheets or content delivery networks on the website; fonts, icons and artwork are served from Dynodoc itself.
- AI or language-model services; document content is not sent to one.
- A third-party document conversion service; the converter runs on the same private network as the application.
- Third-party error reporting or session replay.
- Separate object storage or a cache service for documents; documents, history and uploads are stored in the PostgreSQL database.
Changes and contact
Adding or replacing a provider that handles content changes this list and, before the service is adopted for customer data, must be announced in a way the final terms define. Until then this page is the single record. A document can also link to an image hosted elsewhere; that host is chosen by the author, not by Dynodoc.
- Legal operator
- Awaiting confirmation.
- Contact for questions
- Awaiting confirmation. See the privacy policy.
- Hosting provider
- Awaiting confirmation.