Your information, explained.
This notice covers the Rout preview website and email waitlist. It does not describe a launched financial product. Updated September 28, 2026.
What you share
If you join, we collect your email address, signup time and source. The form asks for permission to send product updates and early-access invitations. We use your permission to contact you about Rout; you can ask to leave the list at any time.
What the demo does
The walkthrough uses sample cards and purchases. Choices stay in the current browser session and are not submitted with your email. It does not collect real card numbers, balances, bank credentials or transactions.
The installable demo at /demo stores a demo sign-in flag in session storage and caches public app files for offline use. Demo credentials are checked in your browser and are not sent to a sign-in server. Sample payment history stays in memory and resets on reload or sign-out. You can remove cached demo files through your browser’s site-data settings.
How information is used and stored
Waitlist submissions are collected and stored using Netlify Forms, our hosting provider’s form service. The Rout team can view submissions and export them to manage the waitlist. The purpose is to maintain the list and contact people about Rout. The hosting provider may process technical request information such as IP addresses and server logs to operate and protect the website. Netlify may use spam filtering to help protect the form. A separate private store holds a hashed email identifier to count new verified website signups once. Only the total is public. Removal requests include this identifier.
If confirmation delivery is enabled, the email provider receives the recipient address and confirmation content. This website does not include advertising trackers or set advertising cookies.
Website analytics
We use Google Analytics to understand website and demo visits and measure successful waitlist form submissions. Google Analytics uses cookies and processes usage and device information. Our signup event does not send your email address, form contents, or demo credentials. Google Signals and advertising personalization are disabled in our tag configuration. You can block analytics through your browser settings or use Google’s Analytics opt-out browser add-on. Read Google’s privacy policy for information about its processing.
Your choice to leave
To leave the waitlist, ask about your information or request deletion, email co2656@columbia.edu from the address you used. Unsubscribe requests are handled by the team; leaving does not require a purchase or account. Email replies and related correspondence are also handled by the team.
How long information is kept
The waitlist is kept while it is used for the pre-launch program. You can request removal at any time. Provider backups and operational logs may follow their own retention periods. We will update this notice if the product or data handling changes.
Before connecting a financial account
Any future account connection will need its own clear permissions and information about the relevant providers. The architecture and security ideas shown elsewhere are development plans, not claims of completed certifications.