Privacy Policy

Duggie CMS is operated by Duggie Labs, LLC ("Duggie", "we", "us"). This policy explains what personal information the service handles and why. It covers duggiecms.com and the Duggie CMS application and API.

Two different roles

Duggie handles two kinds of information, and the difference matters because your rights differ between them.

• Your account information. We decide what to collect and why, so for this information we are the controller. This policy governs it.
• The content you store in Duggie. You decide what goes into your projects and why. If that content contains personal information about other people, such as your own clients or their customers, you are the controller and we are acting as a processor on your instructions. We do not decide what you store, we do not use it for our own purposes, and we do not share it with anyone except the providers listed below who are needed to run the service.

If you are subject to the UK or EU GDPR and you store personal information in Duggie, that second relationship normally requires a data processing agreement between us. Contact us and we will put one in place.

What we collect

Account information

• Username and email address.
• First and last name, if you provide them.
• A password, stored only as a salted hash. We never store your password in a readable form.
• A Google account identifier, if you sign in with Google. We do not receive your Google password.
• Your role, account status, display preferences, and the dates your account was created and last changed.
• A private note our support team may keep on your account, for example to record why a credit was given. It is not shown in the app, and you can ask us for a copy of it.

Other things you send us

• If you use the contact form: your name, email address and message, which are emailed to our support inbox.
• If you join the waiting list: your email address and where you signed up from.
• If you invite someone to a project: their email address, held with the invitation until it is accepted, declined, withdrawn or expires.

Content you store

The text, HTML, JSON, images and documents you upload to your projects, along with their version history, publication state, and the record of which account made each change.

Billing information

If you subscribe to a paid plan, payment is handled by Stripe. Card numbers go directly to Stripe and never reach our servers. We pass Stripe your account email address when you start a checkout, so the receipt goes to the address we already hold. We keep a record of what you have bought, which is project slots and storage, with its status and renewal date, any complimentary slots we have given you, and the customer and subscription identifiers Stripe gives us.

Technical information

Server logs, which include IP address and timestamps. Application logs, which record what the service did and can include the account identifier involved and, in some messages, an email address; these are sent to Better Stack, our logging provider. Activity records for your projects, which store what was done, when, and by whom, and do not include IP addresses. API usage counts used to enforce usage limits. If an error occurs, a diagnostic report is sent to Sentry, which may include the URL and the account identifier involved.

What we do not do

• We do not sell or rent your personal information, and we never have.
• We do not use your content to train machine learning models.
• We do not serve advertising and we do not share information with ad networks.
• We do not use advertising analytics, and there is no Google Analytics or tracking pixel on this site.
• We do not track you across other websites.

Scripts this site loads

Three pieces of software from other companies run in your browser on this site. None of them advertise to you or follow you elsewhere.

• Cloudflare Web Analytics counts page views so we know which pages are read. It sets no cookies, and it does not build a profile of you or track you across other sites.
• Cloudflare Turnstile checks that sign-up and contact form submissions come from a person rather than a bot.
• Google Identity Services powers the Sign in with Google button. It loads on pages where signing in is possible, whether or not you use it.

Cookies and browser storage

We use no advertising or analytics cookies. What we do use is limited to running the service:

• A refresh token, stored in a secure cookie that expires after 7 days. It keeps you signed in without asking for your password on every visit.
• A short lived access token and your interface preferences, such as light or dark theme, stored in your browser's local storage. Signing out removes the access token. Preferences stay in your browser until you clear its site data.
• While you edit, a copy of your unsaved work is kept in your browser's own storage so that a closed tab or a failed save does not lose it. It stays on your device, is never sent anywhere except when you save, and is removed once the save succeeds.

Service providers

We use a small number of providers to run Duggie. Each receives only what it needs.

Uploaded files are scanned for malware by software we run ourselves. Your files are not sent to a third party scanning service.

We may also disclose information if the law requires it, or to protect the rights and safety of our users. If Duggie is ever acquired, account information would transfer with the business, and we would tell you before that happened.

Where your information is held

Duggie is operated from the United States, and the providers above process information in the United States and other countries. If you are located elsewhere, using Duggie means your information is transferred to the United States.

How long we keep it

• Account information is kept while your account is open. Closing it removes it from the live service right away, and it cannot be undone. We never cancel a subscription or delete a project on your behalf, so you cancel and clear those yourself first, and closing the account removes what is left: your profile, your memberships of other people's projects, and your pending account activity. Three things outlast that, and are listed below: backups, logs, and our own record of support actions.
• Content is kept until you delete it. Older versions of an asset are kept up to a fixed number per asset, which is the same on every project, and are then removed automatically. A file deleted from Duggie may stay in a content delivery network cache at the edge for a period afterward.
• Backups. A copy of the database is taken every night and kept for 35 days, in storage separate from the live database. Anything you delete, your account included, leaves the live service at once and leaves the backups as each nightly copy reaches 35 days. Our database provider also keeps its own short-term snapshots.
• Activity records, the log of who changed what in a project, are kept for two years and are then removed automatically. On a paid project you can export the activity log at any time and keep your own copy for longer. Deleting a project deletes its activity log with it.
• Application logs are kept by our logging provider for a limited period and then deleted. They are not tied to your account record, so closing an account does not remove log lines that already mention its identifier.
• Support actions. When our team changes something on an account or a project, such as granting a complimentary slot, suspending an account, or signing in to look at a problem, we record who did it, when, to which account, and why. That record is kept after an account is closed, because it is how we account for what we did. It holds a username and, where an email address was changed, the addresses involved. It does not hold your content.
• Billing records are held by Stripe, who retain them to meet tax and accounting obligations. We keep only the record of what you have bought described above, and the customer and subscription identifiers Stripe gives us, for as long as your account is open.

Your rights

Whatever your location, you can ask us to give you a copy of your information, correct it, or delete it. You can change most of it yourself in your account settings, and you can delete your account from there at any time.

If you are in the UK, the EU, or a US state with its own privacy law, you may also have the right to object to or restrict certain processing, to receive your information in a portable format, and to complain to your local data protection authority. We do not charge for these requests and we will not treat you differently for making one.

Security

Traffic is encrypted in transit. Passwords are stored as salted hashes and are never recoverable in readable form. Project API keys are stored so that you can view them again in your project settings, and you can revoke or rotate any key at any time. Access to production systems is limited to people who need it. No service can promise perfect security, but if a breach affects your information we will tell you.

When our team looks at your account

To help with a problem, a member of our support team can sign in to the app as it appears to you. This is read-only unless there is a recorded reason to make a change, each session is time-limited and logged with who opened it and when, and the first time one opens a project it leaves a line in that project's activity saying that support viewed it, so the people who work there can see that it happened. Changes our team makes that affect what you can do, such as a suspension, a blocked project, a replaced API key or a complimentary slot, are normally emailed to the account they affect.

Children

Duggie is a tool for professional developers and is not directed at children. We do not knowingly collect information from anyone under 16. If you believe a child has given us information, contact us and we will remove it.

Changes to this policy

If we make a material change we will update the effective date above and tell account holders by email before it takes effect.

Contact

For any privacy question or request, including a data processing agreement, reach us through the contact page.