Privacy

POSTPAD stores public post IDs, Twitter account IDs and handles, launch records, wallet addresses, signed withdrawal requests and transaction references to operate the service.

Twitter sign-in and destination-wallet creation are provided by Privy. Privy and Twitter process authentication data under their own policies. The application verifies your Privy access token and linked Twitter ID on the server. Authentication SDKs may use browser storage and cookies.

Launch records, token metadata and blockchain transactions are public. Images and metadata published to IPFS may remain available after a post or account is removed. Do not include private information in launch metadata.

Private inbox keys remain on the worker. They are not sent to the browser. Service credentials are never exposed through public API routes.