Early Invite privacy

Updated September 29, 2026.

What we use

When you sign in with X, Clover receives your X account ID and handle. We use your account to keep your application, original registration time and referral relationship consistent. We check whether you follow Clover, like the announcement, and posted the reply or quote you submit.

We store task verification results and the ID of your submitted response. We check your likes only to locate the campaign announcement; we do not store a copy of your likes timeline. We do not request your email, password, direct messages, or permission to publish or follow on your behalf.

Your application and referrals

Your application priority is calculated internally. We do not display a public applicant ranking or total applicant count. Your signed-in dashboard shows your own verified and pending invitations. If you join through an invitation, the person who invited you can see your handle, registration date and whether your tasks have been verified. Your referral relationship and first registration time are retained when you sign in again.

Cookies and access

We use necessary, secure cookies for sign-in and your Clover session. X access tokens are encrypted on the server, are not sent to the page, and expire after a short session. Signing out deletes that session. You can also revoke Clover’s access in your X settings. Revoking access or signing out does not automatically delete your application.

Storage and deletion

Application and referral records are used for Early Invite and access allocation. Hosting and database services process these records to operate Clover; X processes the sign-in and task-check requests. We do not sell your application data or use it for advertising profiles.

To ask about your data or request deletion, contact Clover at @cloverdotfamily on X. Do not post passwords, wallet keys or other private information. We may ask you to verify ownership of the X account before changing its records.

Technical error logs can contain request paths and failure information. Authentication credentials and X response bodies are not intentionally written to application logs.