Permissions and privacy

The consent screen

When an assistant connects, Packstack shows a page on app.packstack.io — never inside the assistant — naming the app that's asking and listing exactly two permissions:

• Read your trips, packs and gear. See your trips, packing lists, gear closet, kits and categories. Never your email, payment details or hiker body measurements.
• Make changes on your behalf. Create and edit trips, packs, gear and kits, and archive or restore gear. It cannot delete anything. Requires a Packstack subscription.

Some assistants also ask to "stay connected," which just means they'll refresh their access automatically rather than asking you to sign in again. You'll see the address the assistant will return to after you allow; for apps running on your own computer (like Claude Code) it will be a localhost address, and the page says so.

Free accounts and the subscription gate

You can grant both permissions on a free account. Reading works right away. When your assistant tries to change something, Packstack refuses and tells it that editing requires a subscription; the assistant will usually relay that and point you to app.packstack.io. The check happens on every change, so upgrading takes effect immediately, and a lapsed subscription is cut off immediately too — no reconnecting either way.

What your assistant never sees

• Your email address, sign-in method, or anything about payment.
• Body measurements on hiker profiles — only profile names, so it can tell whose pack is whose.
• Other users' data. Everything is scoped to your account.
• Your Packstack password or session. The connector uses its own short-lived tokens that are useless anywhere but the connector.

What's shared with the AI provider

Whatever your assistant asks Packstack for — your gear list, a trip's details — goes to that assistant's provider (Anthropic, OpenAI, and so on) as part of your conversation, under their terms and retention rules, not ours. Packstack only answers the specific requests the assistant makes; nothing is pushed to them on its own. If that matters for a particular trip or item, don't ask the assistant about it.

Taking access away

Open the Packstack web app → Settings → Connected apps. Each connected assistant is listed with what it can do, when it connected and when it was last used. Disconnect revokes every token it holds, effective on its next request. Removing the connector inside the assistant also works, though Packstack won't know until the next attempt fails.

How tokens work, briefly

Access tokens last one hour and are stored only as hashes. Assistants renew them with a refresh token that rotates on every use; a reused old token revokes the whole chain. Nothing about your account is encoded in the token itself. The full technical detail is on the developer page.

Questions

Email support@packstack.io. Our privacy policy and terms apply to the connector as they do to the rest of Packstack.