PALETTA / PRIVACY

Privacy, clearly.

This page covers Paletta’s public website, early-access waitlist, private tester workspace, and developer hub. File uploads, repository connections, and code execution are not available.

Waitlist information

If you join the waitlist, we collect your email address, optional developer role, signup time, and consent to receive early-access updates. We use this information to manage interest and contact you about Paletta. We do not sell waitlist information or use it for advertising profiles.

Tester invitations and sessions

The operator can issue an individual invitation with a tester name, expiry, access duration, and daily message allowance. An invitation PIN can be redeemed once. We store a keyed hash of the PIN, not the readable PIN. The hashing key stays in protected server configuration. Tester sessions use random tokens, with only their hashes stored in the database, and last for up to seven days. Revoked or expired access blocks further workspace requests.

Your conversations

The tester workspace stores conversation titles, messages, timestamps, and reply status in Cloudflare D1. Each conversation is associated with its tester identity, and requests are checked against that identity. You can rename or delete a conversation, or clear your conversation history in account settings. Deleting history removes its stored titles and messages; usage counters and request metadata needed for abuse and spending controls remain.

On-device replies are generated in your browser using your prompt and a limited portion of the current conversation. Paletta sends the prompt and reply to its database to save them in your private history. Your browser may need to download its AI model before you can use this feature. If Paletta enables hosted replies in the future, your prompt and relevant conversation context may be sent to Cloudflare Workers AI for generation. The model has no repository access or code-execution tools. Keep credentials, API keys, personal records, and other sensitive information out of messages.

Feedback and operator access

If you submit beta feedback, we store the text, type, timestamp, and tester name for the Paletta team to review. Your chat history is not automatically attached to feedback. The developer hub provides invitation controls and submitted feedback; it has no conversation-browsing endpoint. The operator and infrastructure providers can access stored information as needed to maintain, protect, and operate the service.

Infrastructure and essential cookies

Paletta uses Cloudflare for hosting, its database, security, and the optional AI model connection. Cloudflare may process technical information such as IP addresses and request details to deliver and protect the service. Automatic browser-analytics script injection is disabled. Paletta sets no advertising cookies.

The tester workspace uses an essential, secure session cookie for up to seven days. The developer hub uses a separate essential cookie for up to eight hours. Both are HttpOnly and SameSite=Strict, and sign out revokes the relevant server session. Signing out of tester access requires a new one-use invitation to return. Clipboard buttons use your browser’s clipboard permission.

Security and retention

We use HTTPS, server-side validation, permission checks, and request limits. Temporary abuse counters use hashed identifiers and time windows instead of storing raw IP addresses in the application database. Expired counters are cleared as requests are processed. Prompts, PINs, and session tokens are excluded from application error messages and deliberate application logging.

Conversation content stays until you delete it or the operator removes it. Waitlist details are retained while needed to manage early-access interest, unless removed below. Invitation records, submitted feedback, and usage metadata remain while needed to operate the beta, handle feedback, and control abuse and spending. If your tester session has expired and you need help removing information, contact the person who invited you.

Remove a waitlist signup

Use an email address you control. This deletes its waitlist entry and optional role. The response does not reveal whether the address was on the list.

Developer access

The developer password is verified on the server against a salted hash stored in protected configuration. Authorized developers can view progress, create and revoke tester invitations, and review submitted beta feedback. The hub does not expose waitlist email addresses, stored PIN hashes, or the model’s credentials. Keep developer credentials private.

Paletta logo

PALETTA / PRIVATE BETA

Your next build.
Your invitation.

Enter the four characters from your tester invitation. We’ve filled in the first part.

One-use invitation. Your private session lasts up to seven days.

Don’t have a PIN? Request an invitation

Returning tester? Open your workspace

Paletta logo

PALETTA / EARLY ACCESS

Be here
for the beginning.

We’re building something for developers. Get on the list for Paletta’s next chapter.

Free to join. No launch date announced yet.