Privacy

This notice describes this early access website and its waitlist. Last updated September 28, 2026. The Pulse app has separate privacy information presented before account creation.

What you choose to share

When you join the waitlist, we store your university email, your optional first name, the school indicated by your email domain, a broad form source, and the time you joined. Joining does not verify enrollment or create a Pulse app account.

Why we keep it

We use waitlist information to plan campus launches and send Pulse launch and early access updates. Submitting the same email again does not create another subscription or replace your original information.

Simple website analytics

We record basic actions such as a page view, exploring the product preview, opening or closing the app demo, or submitting the waitlist. These events contain predefined categories, not your email, name, exact location, the text you enter, or anything you do inside the app demo. We do not use advertising pixels or cross-site tracking cookies. Analytics respects browser Do Not Track and Global Privacy Control signals.

Storage and protection

Supabase hosts the waitlist and event data. The website server can add waitlist entries but cannot retrieve the subscriber list. To limit automated abuse, the server uses daily rotating, keyed hashes of a trusted network address and your normalized email. Rate-limit records contain these hashes, not raw network addresses or emails. These records are pruned after 24 hours on subsequent requests.

Your choices

Submitting the form is optional. You may request removal by replying to a Pulse launch email when updates begin. We retain waitlist details until you ask for removal or the waitlist is retired.

Product previews

Campus geography and selected place positions come from reviewed public UMD place data. Names, counts, plans, and activity are fictional. Portraits are Unsplash photographs used as illustrations (see Credits); the people pictured are not Pulse users. All of it illustrates the product experience, and none of it is live student data. The current app pilot uses initials rather than student photos. This website, including the app demo, never requests your device location.

The app demo

The interactive app demo runs the Pulse app in your browser. The campus is real; the people, plans, clubs and events in it are fictional. What you do in it is never sent to Pulse: it is kept only in the page’s memory, and it is discarded when you reset the demo or leave the page. The demo never connects to the Pulse app’s servers or to a real account: you use it as a fictional student. Its only network requests download its own files from this website and the map tiles described below, which are for the part of campus the map shows. It downloads about 8 MB the first time, which your browser may keep in its cache.

Campus map provider

The interactive map, and the map inside the app demo, load public map tiles, styles, and fonts from OpenFreeMap. Your browser sends ordinary network requests, including its network address, to the map provider. Pulse does not send your email, student data, or device location with those requests. See OpenFreeMap’s privacy policy.

For the app’s school-email verification, location handling, and privacy controls, read how Pulse handles safety.