Privacy Policy

Account data. Your email address and sign-in identifiers, so we can recognise you and restore your workspace.

Content you create. Conversations, prompts, uploaded files and generated media are stored so your history persists across devices.

Usage metadata. Counts of messages, images and tracks per day, used only to apply fair-use limits and credits.

Payment metadata. Order number, plan, amount, cryptocurrency and payment status. We never see or store your wallet keys, and we never handle card details.

When you sign in with Puter, Eweblb calls Puter.js directly from your browser. Your prompts, files, key-value data and AI usage run against your own Puter account and allowance. That traffic goes from your device to Puter — it does not pass through our servers, and we do not receive a copy of it.

Puter’s own privacy terms apply to that data. You can disconnect at any time from the studio header, and revoke Eweblb from your Puter account settings.

If you use the built-in engine instead of your Puter account, prompts are sent to our model providers solely to produce your answer. We do not sell your content, and we do not use your conversations to train models.

Crypto checkout is handled by Plisio. You are redirected to a Plisio-hosted invoice; the blockchain transaction happens between your wallet and Plisio. We receive only a signed status notification (order number, amount, status) at our Status URL, which we verify cryptographically before acting on it.

On-chain transactions are public and permanent by nature of the blockchain. Refunds are handled case by case — write to us with your order number.

If you connect GitHub, your personal access token is stored in your own Puter key-value store, encrypted in transit and never transmitted to Eweblb servers. Publishing pushes only the files you choose, from your browser directly to GitHub’s API.

Conversations live until you delete them; deleting a conversation removes its messages and attachments. Closing your account removes your profile, conversations, files and usage records. Payment records are kept as long as required for accounting.

Transport is encrypted end to end (TLS). Database access is protected by row-level security so one account can never read another’s rows. Merchant secrets — including our payment provider key — live only in server-side environment variables, and the payment API is additionally restricted by IP allow-list.

You may request access, correction, export or deletion of your data, and you may object to processing. Contact us and we will respond within 30 days.

Eweblb is not directed to children under 13, and we do not knowingly collect their data.

Material changes will be announced in-app before they take effect. Questions or requests: dahdouhn74@gmail.com.