Effective October 31, 2026, 12:55 a.m. Eastern Time.
ROGUE DSP Waitlist Storage Notice
Effective on publication. The current legal page records when this version took effect.
Fluxcode Studio LLC, at 5240 Parkmoor Drive, Westerville, OH 43082, USA, runs these waitlist, legal and privacy-rights pages. This notice explains storage and connection information associated with them.
Forms and private links
The private place page, the leave page and the emailed privacy page use the __Host-be_waitlist_leave_csrf cookie to protect their forms. It contains a random signed code, lasts at most one hour and does not create an account. Blocking it stops those forms from working, including the leave page's button and the request for a fresh leave link. If that happens, reply to a waitlist email or write to [email protected] and a person will handle it. After you confirm a request for a copy of your data, the __Host-rogue_rights_export cookie holds a private download code in that browser until the copy expires, at most seven days. The scripts on our own pages store nothing in your browser.
Forms carry hidden fields for security, the wording shown and any referral or campaign code. The form proof lasts two hours; leave-form protection lasts at most one hour. Referral and campaign codes travel in the URL and form rather than a return-visit cookie. They may be saved with your signup and remain in browser or synced history. If a later release offers marketing, it will show a separate affirmative choice and update this notice before collecting that preference.
Confirmation, private place, leave and privacy-request links contain private codes. Someone holding one may be able to see its page or take its permitted action. Only referral links should be shared. A waitlist confirmation expires after 72 hours; a privacy-request verification link works once within seven days. Opening a confirmation link alone does not confirm the request. If you press the button in the confirmation email from the same network you signed up on, the page can confirm for you as soon as it is on screen; otherwise it shows a button to press.
If a security challenge is used, it can run scripts and store proof that your browser passed. Blocking that storage or those scripts may prevent access.
For published ROGUE addresses, an enabled ROGUE-only mail route can make a separate copy for automatic request handling. It uses delivery information to identify the destination ROGUE address, not visible message headers. An email alone cannot change a list or disclose information.
Connection information
Servers and network services handle connection details, including IP address and browser information, to deliver pages. Forms use keyed fingerprints for limited abuse checks, and the confirmation page compares a network fingerprint as described above. These codes remain personal information; browser cookie settings do not prevent the server from creating them. The signup record does not keep the raw IP address. A trustworthy approximate country code, when available, supports grouped signup reports; VPNs and travel can make it inaccurate.
Private links can remain in browser history and email systems. Clearing cookies does not erase that history or our database records. The Privacy Notice explains purposes, recipients, retention and rights.
Your choices
Browser settings let you block or delete cookies and clear history. Ask [email protected] about your information or use the rights page without an account. Use a waitlist email's link to leave, or ask us to remove you by replying to it or writing to [email protected]. Optional tracking must have any legally required choice before it begins; declining it will not affect your place.
Material changes follow the Terms and Privacy Notice. For help or an accessible copy, contact [email protected].