PRINTDECKDOCS

Project

Privacy policy

Last updated: November 17, 2026.

This policy tells you what data Printdeck keeps, where it keeps the data, and how long. It also tells you how to delete your data.

Who runs the service

Jeremy Collins runs the Printdeck cloud service at https://printdeck.beetlebug.org. Printdeck is free software under the GNU AGPL, version 3. One person makes it and runs it.

The deck software is self-hosted. A person who runs a copy of the cloud service is the operator of that copy, and this policy does not apply to it.

You can check the claims of this policy:

The parts of Printdeck

The owner is the person who connects a deck to the cloud service. A member is a friend who joins a project of the owner with an invite.

What data we keep

The deck

The deck keeps its data on its own SD card. The data does not go to the cloud service until the owner connects the deck to it. The deck keeps:

The logs of the deck are in its memory only. A restart deletes them.

The deck connects to these servers with no action of the owner:

The deck sends data to other servers only when the owner turns on a feature:

The cloud service

The cloud service keeps no passwords and no email addresses. You sign in with a passkey.

When the owner connects a deck, the service keeps:

When the owner makes a share link of a print, the deck sends to the service, until the print ends:

When the owner uses projects, the service keeps:

The service writes logs. A log line has the type of request, the route with no IDs, the time it took and the count of storage calls. An error line can have the name of a GitHub repository and the number of a pull request. The service does not write your IP address to its logs.

The iPhone app and the Apple Watch app

The apps connect to the deck on your local network. The apps keep the address and the API key of each deck, and your session of the cloud service, in the iPhone keychain. The deck key never goes to the cloud service.

For push notifications, the app sends its device token to the push relay of the cloud service. The relay keeps no list of devices. The deck encrypts each message for your phone, and only the app can read it. The relay and Apple see the device token and the encrypted message only.

The app sends the photos that you take for a project to the cloud service.

The documentation site

GitHub Pages hosts the documentation site. GitHub gets the IP address of each visitor.

Why we keep the data

We keep the data only to run Printdeck for you:

We do not sell data. We show no ads. We do not track you. The service has no analytics and no trackers.

Who can see the data

The pages of the cloud service ask search engines not to show them in search results.

Third parties

How long we keep the data

DataHow long
A share link and its files24 hours after the print ends, or after "Ready to pick up". 3 days if the print never ends.
A share link of a print in a projectIts files go at the same time. The link then opens the page of the print.
An inviteUntil it is used or removed, at most 7 days.
A code to connect a deck1 hour.
A code for the owner passkey10 minutes.
A photo as uploadedUntil the service cleans it, at most 1 day.
A sign-in14 days. Sign out removes it from your browser.
The logs3 days.
The backups7 days.
Projects, prints, photos, plans and buildsUntil the owner deletes them.
A memberUntil the owner removes the member, or the member deletes their account.
A passkeyUntil the owner removes it or its member, or the member deletes their account.
The HTTPS name of a deck and its DNS recordUntil the owner disconnects or removes the deck. The names in the public logs of the certificates stay there.

The service makes a backup of all its data each day, and keeps each backup 7 days. A deleted file also stays as an old version for 1 to 2 days. After a delete, a copy of your data can stay in the backups and the old versions for up to 9 days. Then it is gone.

The network of AWS (CloudFront) keeps copies of the public files near the visitors. A copy of a deleted public file can stay there for a time after the delete.

Cookies and browser storage

The service sets no other cookies.

Your choices, and how to delete your data

The owner deletes data in the web app or on the deck:

A member deletes their account in the web app: sign in, then tap "Delete my account" on the page of the projects. The service deletes the passkeys and the photos of the member, and removes the member from each project.

When a member is deleted, the notes stay, because other people wrote them too. The name of the member on them changes to "A former member". The prints and the history of the project stay.

You can delete the data on your deck. Remove the deck from the cloud service, then write a new Printdeck OS image to the SD card.

If you do not have an account, or you want help, write to privacy@beetlebug.org.

Children

Printdeck is not for children under 13. We do not knowingly keep data of a child under 13. If you think that we have such data, write to privacy@beetlebug.org, and we delete it.

Security

Changes to this policy

We change this policy when Printdeck changes what it keeps. The date at the top tells you the date of the last change. The history of each change is on GitHub: https://github.com/beetlebugorg/printdeck/commits/main/PRIVACY.md.

Contact

Write to privacy@beetlebug.org.