Terms & Privacy

• Campaigns and responses are stored on Sui Testnet, which is periodically reset by the Sui Foundation: they may be deleted without notice. Data persistence is not guaranteed until mainnet launch.
• The contract is upgradeable during the beta, and Logbook holds the key that upgrades it. A fresh deployment of the contract starts with an empty history in the interface: earlier campaigns stay on-chain but are no longer shown.
• Features may be incomplete, change significantly, or be removed.
• Nothing here costs real money. If you sign in with Google, Logbook pays the gas fees for you, within daily limits per account and per IP address. With a wallet you pay gas yourself with test SUI, which is free: use “Get test SUI” on the Account page.

• A campaign and every response are transactions on the blockchain. A response cannot be changed or deleted, and each account responds once.
• A campaign can be edited or deleted until its first response; after that it cannot be changed. Deleting a campaign does not erase the transactions that created and edited it.
• Do not publish anything you might want to take back.

• That an address responded, and when, is always public: it is visible in the campaign's Responses tab and to anyone who views the blockchain.
• Who can read the answers depends on the campaign's “Answers visible to” setting, which is shown before you respond. With Everyone, answers are stored in plaintext on-chain. With Everyone with access, Voters only, Only creator or After the end date, answers are encrypted in your browser before they are sent, and only the readers allowed by that setting can decrypt them. You can always read your own answer.
• A campaign that is not open to anyone keeps its title, description and questions encrypted as well: they can be read with its password, by the addresses on its list, and by its creator.
• Encrypted or not, what is on the blockchain is public data: anyone can copy it, and it stays there.

• With Google (zkLogin), your blockchain address is computed from your Google account. Logbook never sees your Google password, and your email is not stored on the blockchain.
• With a wallet, your keys stay in the wallet: it asks you to approve every transaction and every message it signs.
• Signing out ends your web session in this browser. An AI agent you signed in separately keeps its own session until it expires or you end it; see Authentication.

On Sui Testnet: campaigns (their content, encrypted unless the campaign is open to anyone; who may take part and who may read the answers; the creator's address; the address list of address-list campaigns; the hashes of the documents a campaign is about) and responses (the respondent's address, the answers in plaintext or encrypted, the time).

On Walrus, with a copy in Logbook's cache: the documents a campaign is about, AI reports and results certificates. Their SHA-256 is recorded on-chain, and files of private campaigns are encrypted before they leave the creator's browser. Walrus storage is rented: during the beta, files are kept for at least 50 days after publishing, while the on-chain record stays. A file uploaded but never recorded on-chain is deleted from the cache after two days.

On Logbook's servers: no application database. Besides that cache, the servers keep only daily quota counters (per sender address, per IP address and per API key; they expire after two days), integrator API keys (hashed), and the sessions of apps connected through the remote MCP connector, with their signing keys encrypted. Error reports from the app go to the hosting logs (Cloudflare), with web addresses cut to their path.

With the AI provider: the AI features send data through Logbook's server to a third-party provider (DeepSeek), handled under that provider's terms: what you type to the campaign assistant, with the current form, and, when a creator runs AI Analytics, the questions and the answers they agree to send, without addresses.

In your browser: your Google sign-in (address, email, the session key and its proof), your preferences, the passwords of password campaigns you created or opened, and the campaign assistant's conversation; for the open tab only, campaign content keys, answers you are filling in while you sign in, and where to return after signing in. Signing out removes the sign-in, the stored passwords and keys, and the assistant's conversation.

The Data Storage and Beta Testing pages of the documentation go into more detail. Write to hello@logbook.zone, or find us on X and Telegram.