zDocket Privacy Policy

Version: 1.1.0
Effective Date: November 17, 2026
App: zDocket for Mac, iPhone, iPad, and Apple Watch, and its sync service at zdocket.cc
Developer: Bristlecone IT Services, LLC

This policy explains what zDocket keeps, where, for how long, who receives it, and how you can delete it.

The Short Version

  • zDocket works on your devices without an account. If you turn on sync, sharing, mail-in, or agents, your workspaces are also kept on our servers, so your devices can sync and the people, agents, and services you choose can work with you.
  • We keep no email address for your account. If you add a recovery address, we keep only a scrambled form of it that we can’t read back.
  • We use what we keep only to run zDocket. We don’t sell it, show ads, or use analytics or tracking.
  • We back up each workspace’s synced content once a night and keep backups for 30 days. See Backups.
  • You can delete a workspace you own, or delete your account and with it the workspaces you own.

Who We Are

zDocket is published by Bristlecone IT Services, LLC, a Tennessee limited liability company (“we”, “us”), as part of zSuite. We are based in Tennessee, in the United States. Our mailing address is at the end of this policy.

On Your Devices

Each device that opens a workspace keeps a full copy of it: its items, notes, comments, steps, links, tags, projects, areas, the people and agents you add to it, its intake rules, and the history of who changed what. zDocket works offline from this copy.

If you allow it, zDocket reads your calendars and reminders on your device to show events beside your items and to import reminders, and can add time blocks to a calendar you choose. What it reads from them stays on your device and isn’t put in a workspace or sent to us. An import from another app, and an export you make, also happen on your device.

On Our Servers

zDocket’s servers run on Cloudflare. When you turn on sync, we keep:

  • Your account. An account identifier, the name you give, and when you joined. zDocket signs in with passkeys or Sign in with Apple, and keeps no email address or password for your account. For a passkey we keep its public key, name, and use count; the secret part stays on your device. For Sign in with Apple we keep Apple’s identifier for you and the token Apple gives us, encrypted.
  • Sessions. For each signed-in device, a scrambled (hashed) session identifier, the device’s name and platform, and when it was used.
  • Your workspaces and shared projects. Everything your devices hold for each one (see On Your Devices), so they can sync, and who may open it and with what permission. Done items moved out of a full workspace are kept in its archive.
  • Your own list of documents. The workspaces and shared projects you hold, with their names and your role, and where shared projects show in your sidebar.
  • Attached files. Files you attach to items, in private storage with no public address.
  • What you turn on. The settings and records for the features below that you use, and the activity records described under Activity Records.

We use this only to sync your devices, to run the features you use, to keep zDocket secure, to provide support, and to comply with the law.

Account Recovery

You can add one recovery email address in Settings, so you can still sign in if you lose every passkey. It’s optional. We send a code to the address, and you type it back to confirm it.

We don’t store the address. We keep only a keyed scrambled form of it (a keyed hash), which lets us tell that an address someone types is the one you added, but doesn’t let us read the address back or write to it on our own. We use the address you type only to send the code you asked for at that moment. We keep each code only in scrambled form. A code works for 10 minutes and allows 5 tries, and we send at most 10 codes a day for an account. We also keep when each code was sent, for a day, to enforce that limit. If you lose every passkey, a code sent to your recovery address signs you in, and zDocket then has you add a new passkey.

When you remove the address, add another, or delete your account, we delete its scrambled form and any codes.

Where Your Data Is Kept, and Encryption

Cloudflare stores and processes zDocket’s data on its network, which may be outside your country. Your connection to our servers is encrypted. zDocket doesn’t use end-to-end encryption: our servers read your workspaces in order to sync them, back them up, and run the features you use, so people who work for us can reach them when that is needed for support, security, backups, or legal compliance.

Backups

zDocket keeps a backup of each workspace’s synced content (its items, projects, areas, tags, and people) once a night, in private storage with no public address, so a workspace can be restored after a fault. A night when a workspace hasn’t changed adds no new backup. Backups don’t include archived items or attached files.

Each backup is kept for 30 days, except a workspace’s newest backup, which is kept until a newer one replaces it. When a workspace is deleted, by its owner or with their account, its newest backup is deleted within a day and the rest within 30 days. Something you delete from a workspace can stay in its earlier backups for up to 30 days.

Only zDocket’s operators can restore a backup. Once a week we test a restore on a private copy that no one can reach, and delete the copy right after. We keep a record of each test (when, which workspace, whether it worked, and how many items), but none of its content.

People You Work With

  • People and agents in a workspace. You can add people and agents to a workspace, with a name and contact details you enter. Please add only what you need.
  • Shared projects. When you share a project, the members you invite can see and change it as their permission allows, and they keep their own copies on their devices. An invitation works once and for 7 days.
  • Hand-off links. When you hand an item to someone with a link, anyone with the link can see that item’s title, notes, dates, and brief, and answer as its holder, until the link expires (after 30 days unless you choose up to 90), you end it, or the hand-off ends. The page shows nothing else from your workspace and no email addresses.
  • Hand-off emails. If you choose to email a hand-off, or a reminder about it, we send the item’s title, brief, dates, and link, or the reminder’s note, to the address you give. A reply to that email becomes a comment on the item. We keep the address the email went to until the link expires, so replies can reach the item.

Agents You Connect

You can connect an agent, such as an AI assistant or a script you choose, to your workspaces. You approve it while signed in, and choose which workspaces and shared projects it may work in and what it may do there. When an agent reads your items, we send it what it asks for within what you allowed. Once the agent receives it, it and whoever provides it handle it under their own terms and privacy policies, not this one.

Everything an agent changes is recorded under its name. An agent can’t delete anything. It can read the activity and a daily summary of the items that are its work, and it can propose a setup (such as projects, addresses, and intake rules), which changes nothing until you approve it. We keep a proposal for 90 days after you approve or decline it. We also keep when each agent last checked for new work, so you can be told when one stops checking. You can end an agent’s access at any time.

If you give an agent a webhook, we send that address the docket number, identifiers, and type of each event, never titles or notes.

Mail-In, Webhooks, and Intake

  • Mail-in. You can make up to 50 mail-in addresses for a workspace. An email sent to one becomes an item, with the message’s subject, the sender’s name, its plain text, and a link with the sender’s address. We keep only a scrambled form of each address you make, with the name you give it.
  • Webhooks. You can make up to 50 webhook addresses. Anything posted to one becomes or changes an item, with the title, notes, dates, severity, and source address it sends. For an address you set up for a service, such as Stripe or Apple’s App Store notifications, we keep the secret the service signs with, and each message’s identifier for 4 days so a repeat counts once.
  • Intake rules. Your rules decide where an item from outside goes: its project, severity, tags, or an agent to hand it to. A rule can also remove an item it placed after a time you set, up to 365 days. Removal is for good, with its comments and history, except for copies in backups as described under Backups.
  • Check-ins and warnings. An item can expect check-ins from a service and open again if one doesn’t come, and can raise its severity as a due date nears.
  • Other people’s information. Mail and posts can hold information about people other than you. You choose which addresses to give out and to whom.

Email We Send You

  • Urgent items. When an item can’t wait, by its severity, or an agent’s access is about to end, we email the address you confirmed for your daily brief, with the item’s number, title, and brief. We keep when each email went, for a day, to limit how many we send.
  • Daily brief email. If you turn it on and confirm the address, we email the address you give your docket numbers, titles, and due dates each day.
  • Recovery codes, as described under Account Recovery.

We send email through Cloudflare’s email service, from zdocket.cc. We don’t send marketing email.

Other Features You Turn On

  • Calendar and brief feeds. If you turn on a feed, anyone with its secret address can see your docket numbers and titles, and for the brief feed, due dates and who holds each hand-off. Making a new address ends the old one.
  • Your brief in zFolio. If you connect zFolio, we write your daily brief (docket numbers, titles, due dates, who holds each hand-off, and which workspace each line is from) into one zFolio note each day. We keep zFolio’s sign-in token for it, encrypted, and the note’s identifier. We send zFolio nothing else and read only that note. zFolio keeps the note as yours, under the zFolio Privacy Policy. When you disconnect, we delete the token, and the note stays in zFolio.
  • GitHub. If you connect a GitHub repository, GitHub sends us updates on the pull requests and issues you link to items. We send GitHub nothing. Creating an issue from an item opens GitHub’s own page, filled in with the item, for you to submit.

Activity Records

We keep two records of activity, which only the hub writes and no one can change:

  • Access record. For your account: sign-ups, sign-ins (and refused passkey sign-ins), sign-outs, passkeys added or removed, Apple IDs linked, recovery addresses added or removed, recovery codes sent, requests to delete your account or a workspace (and their cancellation or completion), and feeds and brief emails turned on or off, with the device’s name and platform. For a workspace: who made it, invited, joined, left, changed a permission, connected an agent, or changed its addresses or connections. We keep these for 400 days.
  • Change record. For each workspace, unless its owner turns it off, who changed what, by the identifiers of the records changed. At the owner’s highest level, it also records reads, such as an agent’s reads and feed fetches. We keep it for 30, 90, or 365 days (the default), as the owner chooses.

Neither record holds your content (titles, notes, or messages), secrets, tokens, or IP addresses. A workspace’s owner can read and export its records, and you can read your account’s. When a workspace is deleted, its records are deleted. When your account is deleted, its records and its workspaces’ records are deleted. Records in other people’s workspaces that name you as the one who acted stay there by identifier only.

Logs and IP Addresses

  • Request logs. Cloudflare keeps logs of requests to our servers, which can include the IP address, the app or browser, an approximate location, the address requested, and the log lines our code writes, for up to 7 days. Our own log lines record only the kind of failure, never your content, names, or addresses. Only people who operate zDocket can see these logs.
  • IP addresses. We don’t store your IP address in our database. To limit repeated sign-in attempts, recovery codes, and agent registrations, we briefly use a scrambled (hashed) form of it in Cloudflare’s short-lived rate-limit counters. Cloudflare processes IP addresses to deliver and protect zDocket, under its own practices.
  • Cookies. zDocket uses no advertising or tracking cookies.

How We Share Information

We don’t sell your information, and we don’t share it for others’ marketing or advertising.

  • Cloudflare runs zDocket’s servers, storage, backups, email, and logs.
  • Apple receives what Sign in with Apple needs, if you use it, and we ask Apple to revoke its token when your account is deleted.
  • The people, agents, and services you choose receive what is described above.
  • Legal and safety. We may disclose information if the law requires it, or to protect our users, our services, or the public from fraud or serious harm.
  • Business transfer. If zDocket is transferred to a successor, information may be transferred with it, and this policy will continue to apply until it is changed as described below.

How Long We Keep Information, and Deleting It

  • Trash. An item in the Trash is deleted for good 30 days after it was trashed, the next time zDocket empties the Trash on one of your devices.
  • Attached files. We delete a file 7 days after it is removed from its last item, and with its workspace.
  • Sessions. A session ends after 30 days without use, and after 90 days at most, or when you sign out.
  • Links, addresses, feeds, and webhooks. We keep each one’s record until it expires or you end it or turn it off. Events waiting for an agent’s webhook are deleted once delivered, or after 5 tries.
  • Agents. We delete an agent’s access records after its access ends or you revoke it.
  • Shared projects. When you leave a shared project, it leaves your list of documents within 90 days. When a shared project is made private, its members can no longer open it after 14 days.
  • A workspace. The owner of a workspace can ask to delete it in the app, as long as they keep another workspace of their own. For your security, this needs a recent sign-in and the workspace’s name typed out. The workspace closes at once for everyone in it, including its agents, hand-off links, feeds, mail-in addresses, and webhooks, and its owner can restore it for 7 days. Until then we keep its list of members, so a restore can bring them back. We then delete the workspace with its files, archive, and activity records, its agents’ access to it, and its addresses and invitations. Backups are deleted as described under Backups. The owner’s access record keeps that it was deleted, by identifier only. We allow 3 requests a day for an account, and keep when each was made, for a day, to enforce that limit. Members keep their own copies, as described under On your devices.
  • Your account. You can ask to delete your account in the app. For your security, this needs a recent sign-in. We delete the account 7 days later, unless you cancel before then. We then delete the workspaces you own, with their files, archives, and activity records, your list of documents, your sessions, passkeys, recovery address, and Apple sign-in, any zFolio connection, and your memberships elsewhere. A shared project you own with other members goes to one of them, unless you choose to delete it when you ask. Backups are deleted as described under Backups.
  • Recovery copies. Our storage providers keep a recovery history of our databases for up to 30 days, so deleted information can remain in it for up to 30 days.
  • On your devices. Deleting something on our servers doesn’t remove copies already on your devices, on other members’ devices, in files you exported, or in a zFolio note. You delete those where they are kept. Signing out keeps unsent changes on that device.
  • What may remain. We may keep information that the law requires us to keep, or that we need to resolve disputes or enforce our terms.

Your Choices and Rights

You can use zDocket without an account; turn features on and off; end links, addresses, feeds, and agents’ access; choose your workspaces’ activity record level and how long it’s kept; export a workspace; delete a workspace you own; and delete your account. Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal information. We will also consider requests from anyone, as a goodwill practice and not as a legal obligation. Send requests by mail to the address in the Contact section. We may need to verify your identity, and we will respond within the time the law requires.

Security

We use reasonable safeguards, such as encrypted connections, passkeys, hashed tokens and codes, tamper-evident activity records, and access controls. No method of storage or transmission is completely secure, so we can’t guarantee security. If a breach affects personal information, we will notify affected people as the law requires.

Children

zDocket is for people 13 and older. We don’t knowingly collect personal information from children under 13. If you believe a child has given us information, write to us and we will delete it.

Where Information Is Processed

zDocket is operated from the United States. Cloudflare may process information in other countries where it operates. If you use zDocket from outside the United States, your information is transferred to us in the United States.

Changes to This Policy

Each version of this policy has a version number and an Effective Date at the top. If we change it, we will publish the new version at https://bristleconeit.com/policies/privacy/zsuite/zdocket/ with a new version number and Effective Date. zDocket is in beta. While it is, a material change may take effect as soon as we publish it, and we will tell you about it in the app or on that page. After zDocket leaves beta, we will give at least 7 days’ notice, in the app, on that page, or by email, before a material change takes effect, unless the law requires it sooner or it is needed to deal with an urgent security issue, and then we will tell you as soon as we can.

Contact

By mail only:

Bristlecone IT Services, LLC
PO Box 296
Townsend, TN 37882