No tested restore
Open gateThere is no tested restore from a real managed backup. A restore drill is a recorded launch requirement that has not been met.
Security and trust
Where your Threads credential is stored, and every place it is never sent.
The boundary
Stays on this server
- Your Meta access token, encrypted per credential
- The data key that decrypts it
- Your session cookie
Never returned by the API, never returned in an MCP result, never written to a log, never placed in a URL we generate, and never shown in this interface.
What your assistant receives
- its own scoped keygranted
- capabilities you grantedgranted
- your Meta tokennever
- your sessionnever
- permission to widen itselfnever
An assistant cannot choose which workspace or account it acts on, cannot ask us to call an arbitrary URL, and cannot raise its own permissions. Limits are evaluated here, not by the model.
The credential never crosses this line
How each claim is enforced
| Claim | How it is enforced |
|---|---|
| Your Threads credential is encrypted at rest | One data key per credential, protected by a managed key service and bound to your workspace and that connection, so a record from one tenant cannot be decrypted in the context of another. |
| It is never shown, logged, or returned | Decrypted in memory only immediately before a call to Meta, with the plaintext buffer cleared afterwards. There is no “reveal token” button, because there is no code path that could implement one. |
| An assistant key is hashed, not stored | High-entropy, displayed exactly once at creation or rotation, and kept only as an Argon2id hash — so we cannot show it to you again, and neither can anyone who obtains the database. |
| Rotation and revocation are separate from your account | Rotation issues a new key with an overlap you choose. Revocation invalidates every version. Revoking an assistant does not disturb your Threads connection, and disconnecting Threads does not revoke assistants working on another connection. |
| Human and assistant sign-in cannot substitute for each other | You sign in through an identity provider and get a session cookie; an assistant authenticates with its own key. A browser session can never be used to act as an assistant. |
| Every operation is appended to a hash-chained record | What was attempted, the outcome, the reason, and a correlation identifier. Each entry carries a hash of the one before it, so a removed or altered entry breaks the chain detectably. Post text is not written to these records by default. |
The chain and its current anchor are stored in the same database. They are not externally anchored or independently timestamped, so this detects ordinary alteration but is not proof against an operator able to rewrite every stored event and anchor. Immutable external export remains a production control, not a repository claim.
Current deployment gates
These external checks must be completed against the production environment.
No Meta approval yet
Open gateThere is no approval yet from Meta for the permissions this product requests. Until there is, connecting may be limited to accounts already registered with the app.
No affiliation with Meta
Readyweek is not affiliated with, sponsored by, endorsed by, or partnered with Meta. It uses the Threads sign-in Meta operates, as any third-party application does, and requests six permissions, which are listed on the home page.