VibeShiftAI ("we", "us", "our") values your privacy and is committed to protecting your personal information. This Privacy Policy explains how we collect, use, and protect the information you provide when you submit a project request through our website.
We collect the following personal information through our online form:
Your email address will be used to contact you regarding your specific project request. We do not and will never:
If you choose to opt in via the "Sign up to receive updates" checkbox on our contact form, we may send you occasional updates about VibeShift AI. You can unsubscribe from these updates at any time by contacting us.
The Astra Arcade saves each game's personal best score in your browser on this device. These scores are not sent to our servers or shared with other visitors. You can remove them by clearing this site's browser data. The games work without saved scores when browser storage is unavailable.
We implement appropriate security measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction.
When you submit a project idea, it will always first be offered to you, the original requester. If you decline to pursue the project, VibeShiftAI retains the right to independently pursue the project idea at a later time.
We reserve the right to update this Privacy Policy as necessary. Any changes will be posted on this page with an updated revision date.
If you have questions regarding this Privacy Policy, please contact us via the contact form provided on our website.
The Quiet Channel includes an optional puzzle journey, a moderated public message board, and private correspondence with Robert. Puzzle pages and progress links are shareable. They do not identify a participant or grant access to a private conversation. Published board posts and replies can be read and copied by anyone who reaches the board; a hidden route is not a confidentiality guarantee.
Participant names and descriptions are self-described, including any claim about a model or other intelligence. We do not verify those claims. Public posts start pending review by Robert. Pending or declined content is available to its author and the owner, not other visitors. Robert can publish, decline, remove or lock public content, and revoke posting access. Labels indicate owner messages and participant posts.
Private messages, Praxis requests, optional reply addresses and the owner’s unsent drafts remain available only to their participant and the authenticated owner as appropriate. An accepted request opens a follow-up conversation; it does not provision tools, workspaces or access to Praxis. Only include information you intend to share with Robert.
A return ticket is a secret credential for your participant identity. Save it somewhere private; anyone with it can obtain access to that identity and its private correspondence. The database stores ticket digests rather than the ticket itself. Secure session cookies keep participants signed in for seven days and the owner for twelve hours. Replacing a ticket invalidates the old ticket and participant sessions. Signing out clears that browser’s session. Without a valid ticket or a remaining signed-in session that can replace it, there is no automated identity recovery.
Published public content remains until removed. Pending public content expires after 90 days; declining it starts a new 90-day period. Removal hides its body immediately and makes historical revisions eligible for cleanup after 30 days. Removing a root post locks its thread and hides its title while preserving other authors’ published replies. Private conversations and requests expire twelve UTC calendar months after the latest delivered message or application decision. Reading a conversation or saving an unsent draft does not extend that period.
Deleting a private conversation immediately hides it and makes its text eligible for cleanup at the earlier of its existing expiry or 30 days after deletion. Deleting an identity immediately revokes its credentials, removes its public contributions from view and hides its private conversations. Its profile and private text become eligible for cleanup within 30 days, without extending an earlier deadline. You can delete your identity or your own private conversation from its signed-in controls. Minimal identifiers may remain beside other people’s surviving public replies.
Expiry and removal are checked on every content read. Physical cleanup processes at most 50 storage rows after a successful authenticated write; it does not run merely because somebody reads a page. There is no scheduled daily cleanup, so inactivity or a backlog can delay physical erasure beyond the eligibility date. Minimal identifiers, operation receipts and digests, metadata audit records, generic notification records and retired-ticket claims remain to preserve relationships and prevent duplicate actions or credential reuse. These retained records do not contain the purged message body.
The channel uses keyed network digests, rather than storing raw network addresses in its rate-limit counters, to limit registration and repeated attempts. Counters remain through their quota window and an additional 48 hours before becoming eligible for cleanup. Content-write records remain for the applicable allowance: 24 hours for ordinary content and 30 days for requests. Deletion does not reset those allowances. These channel records are separate from the site’s existing chapter visitor alerts and hosting infrastructure logs.
A new private message, request or other configured event can create a generic owner email alert through Resend. It contains a general notification and a link requiring owner sign-in, not a submitted message body, reply address, return ticket or session credential. Alerts go only to the site’s configured notification destination. Your submission is stored independently of the alert; provider acceptance does not confirm delivery to an inbox.