This explains what Docxoft stores about you, who else sees it, how long it is kept and how to get rid of it. It is written to be read, not to be survived.
Last updated
Playxoft operates the hosted service at docxoft.playxoft.com and is the controller of the personal data described here. For the content you put inside a workspace, you are the controller and Playxoft is your processor: we hold it and serve it back on your instructions, and we do not use it for anything else.
If you run Docxoft yourself, none of this applies to your instance. The software sends nothing to Playxoft; you are the operator, and the sub-processors are whichever ones you chose.
| What | Why | How long |
|---|---|---|
| Account details — your email address and, if your provider supplies one, your display name | To sign you in, to show other members of your workspace who you are, and to send you service email about your account | While your account exists; removed when you ask us to delete it |
| Workspace content — the documents you publish, their versions, changelogs, dependency declarations and search index | It is the service: storing it and serving it back to the people and tokens you have authorised | Until you delete it, or until you ask us to remove the workspace; provider backups age out on their own schedule |
| Audit logs — who changed what, when, and with which credential | Security and accountability. Every mutation writes one, and a workspace owner can read their own | For the life of the workspace, and removed with it on request |
| Operational telemetry — counts of reads per workspace, error rates, rate-limit hits | To keep the service up and to enforce plan limits. Aggregate counters, not a log of what you read | For the retention window our analytics store applies — currently 90 days |
| Billing records — your plan, subscription status and the provider’s reference for it | To give you the plan you paid for. The payment itself is handled by the merchant of record | As long as tax and accounting law requires |
We do not ask for a phone number, a postal address or a date of birth, and there is nowhere in the product to give us one. We never receive your card number: payments go to our merchant of record.
These are the sub-processors for the hosted deployment. Each one is used for one job and receives only what that job needs.
| Sub-processor | What it does | What it holds |
|---|---|---|
| Cloudflare, Inc. | Application hosting (Workers), document storage (R2), network | Every request to the service, and the document bodies themselves |
| Neon, Inc. | Managed Postgres | Account records, workspace and project metadata, the version ledger, the search index and audit logs |
| WorkOS, Inc. | Authentication (WorkOS AuthKit) | Your email address, display name and sign-in events |
| Zoho Corporation | Transactional email delivery (ZeptoMail) | Your email address, and the contents of the notifications, invitations and contact-form messages sent to you or by you |
| Dodo Payments | Billing and payments, as merchant of record | Your billing details and payment method — Playxoft never receives your card number |
Email. The hosted service sends transactional email through Zoho ZeptoMail, listed above: publish notifications to people who subscribed to a document or a project, workspace invitations, and a copy of anything you send through the contact form. There is no marketing mail and no tracking pixel, and every notification carries a link to the page where you can stop it. A self-hosted deployment with no email provider configured sends nothing at all — the feature is off rather than broken.
Playxoft may add or change a sub-processor as the service changes. When that happens the table above is updated and the “last updated” date on this page moves.
The application runs on Cloudflare’s network, which is global; the database and the object storage are provisioned in a region chosen for the deployment. Data may therefore be processed outside your country, including in the United States, under the relevant transfer safeguards our providers offer. If your organisation needs data to stay in a specific jurisdiction, self-hosting gives you complete control of that, and it is one of the reasons the software is licensed the way it is.
Found a hole? Write to security@playxoft.com rather than opening a public issue. We acknowledge within two business days.
Depending on where you live you may have the right to access a copy of your personal data, correct it, delete it, restrict or object to how it is processed, receive it in a portable form, and complain to your data protection authority. You can exercise all of these by writing to support@playxoft.com.
We answer requests within 30 days. There is no charge, and we will not ask you to justify the request.
Docxoft is a tool for engineering teams and is not directed at children. We do not knowingly collect data from anyone under 16; if you believe we have, tell us and we will delete it.
When this policy changes materially we will update the date at the top and, for a change that affects how we handle data you have already given us, tell account owners — by a notice in the app and, where we have an address we can reach you at, by email. Continuing to use the service after a change means the updated policy applies.
Privacy questions and requests: support@playxoft.com. Security reports: security@playxoft.com. See also the cookie policy and the terms of service.