Hallway Waitlist Privacy Notice
Effective date: 12 October 2026 Version: 2026-10-12-v1
On this page
The essentials
Hallway's current service is an email waitlist for adults at eligible Ontario universities. We use your school email and campus to manage your registration and measure campus interest. There is no public member directory. Joining does not create a dating profile or enrol you in matching, SMS, or a paid service.
We keep optional communications separate from registration. You can manage your choices, request access or correction, and leave. Our primary database is in Canada, but some processing takes place outside Canada. Email verification proves access to an inbox, not a person's identity, age, enrolment, or safety.
The rest of this notice explains the information involved, who can see it, and the limits of deletion and confidentiality. Contact us if anything is unclear before you provide information.
1. Who is responsible
Tejass Kaushik, carrying on business as Hallway, is responsible for the personal information covered by this notice.
Privacy officer: Tejass Kaushik Privacy email: tejass@anticipy.ai Business mailing address: 3305 Westmount Rd West Vancouver, BC V7V 3G5, Canada
This notice covers the waitlist website, verification and member tools, waitlist emails, campus requests, ambassador-interest form, and related support. A future dating or matching pilot will require a separate explanation and any necessary new consent before we collect its information. Quebec campuses are closed in this release.
2. Information we collect and why
| Information | How we use it |
|---|---|
| School email, normalized email, campus, registration and verification status, dates, and your statement that you are at least 18 | Check eligibility, prevent duplicate registrations, verify inbox access, operate member tools, and measure interest |
| Language and records of the terms, notice, and choices presented or accepted | Show the appropriate language, honour choices, and document the applicable versions and decisions |
| Optional indication that you might want to participate soon | Understand potential demand; it does not enrol you in a pilot |
| Optional campus-opening, product-update, and ambassador-contact choices | Send only optional communications covered by the relevant choice |
| Referral code and which code was used to join | Attribute verified referrals and show limited referral totals |
| With analytics permission, campaign labels and landing-page version associated with a signup | Understand which outreach and page versions generate interest |
| Optional ambassador interests, a short note, and application status | Evaluate and contact people who ask about helping on campus |
| A requested campus name and information you include in support messages | Consider adding a campus and respond to your request |
| With analytics permission, limited client site events and a random browser identifier | Understand use and improve the website; the event identifier is not deliberately joined to your school email |
| Network and browser information, bot-check results, security counters, access records, and staff audit records | Deliver and secure the service, investigate abuse, and record sensitive staff actions |
| Email delivery results, bounce or complaint records, and limited suppression information | Diagnose delivery, avoid repeat sends after withdrawal or delivery problems, and document what happened |
Required registration information is identified on the form. You can skip optional questions and optional emails. If you do not provide the information needed to verify and maintain a registration, we cannot provide those waitlist functions.
The waitlist does not request a birth date, government ID, selfie, dating photo, gender, sexual orientation, religion, phone number, payment details, or precise location. Please do not put sensitive information, passwords, or information about other people in optional notes or campus requests. If you contact us about an incident, we may need information relevant to handling that request and will explain any additional collection.
Even without a dating profile, membership may reveal an interest in dating. This can be sensitive depending on your circumstances. We limit visibility and access for that reason.
We collect information from you, from the browser and service requests, and from our email or infrastructure providers. If someone types your email without your permission, you may receive a verification message, including a repeated request subject to our rate limits. An unverified request does not confirm membership. Ignore the link if you did not request it, or ask us to remove or suppress the address.
3. Choices about email
Verification and access messages respond to an action you request. We may also send a necessary security, legal, or material service message where permitted by law. We do not add promotional material to a message simply to avoid asking for marketing consent.
You may separately choose to receive one campus-opening announcement, occasional Hallway product updates, or contact about your ambassador application. These choices start unchecked and identify the sender and purpose. Choosing one does not authorize the others or authorize SMS. Declining them does not prevent you from registering or using member controls.
Applying to be an ambassador is optional. To submit that application, the form requires your separate permission for contact about it. This lets us review your submission and follow up on your request; it does not authorize general product updates. You can withdraw that permission and your application at any time.
Use the unsubscribe link or member controls to change optional email choices, including campus-opening notices. You can also contact us. We implement withdrawal without delay and no later than the deadline required by law, which for commercial email under Canada's anti-spam rules is ten business days. A message already sent cannot be recalled. Fresh, informed permission is needed before we resume optional messages you stopped.
Leaving the waitlist ends optional waitlist communications. We retain only the limited information needed for purposes such as honouring suppression, documenting consent, security, or legal obligations, as explained below.
4. Who can see information
Authorized team members access information only as needed for their duties. For example, support may look up an exact email to help with registration, and authorized staff may review ambassador applications. Sensitive administrative actions are logged. Access controls reduce risk; they do not make unauthorized access impossible.
There is no public list of waitlist members. Public campus totals begin only at a minimum group size of 25 and are rounded down. Personal referral totals appear only after three verified referrals and are delayed by at least 24 hours. We do not show the referrer the referred person's email. These limits reduce disclosure but cannot prevent every inference, especially among people who know each other.
We use providers for hosting, database services, bot protection, and email:
| Provider and service | Information and location |
|---|---|
| Supabase database | Registration and related service records. Primary project region: Canada Central (ca-central-1). Backups, support access, and subprocessors must also be considered. |
| Cloudflare Workers, Hyperdrive, and Turnstile | Website and API requests, traffic and security information, database connections, and bot checks. Processing may occur outside Canada, including in the United States. |
| Postmark | Recipient email, message content, delivery events, and suppression records. Email processing is in the United States. |
We remain responsible for information handled by providers on our behalf and use contractual and operational safeguards appropriate to that handling. Information processed abroad may be accessible to courts, law enforcement, or government authorities under applicable foreign law. A Canadian database location does not mean every copy or operation stays in Canada.
We do not sell waitlist personal information or disclose it to advertisers for behavioural advertising. We do not use waitlist submissions to train a general-purpose AI model. We may disclose information when legally required or permitted, for example to respond to valid legal process or address a serious security incident. We assess the authority and limit the disclosure to what is justified. Any business transfer remains subject to applicable privacy requirements and restrictions on materially different uses.
5. Browser storage and analytics
Member cookies support signed-in access, with sessions lasting up to 30 days unless ended sooner. A referral cookie lasts up to seven days. We store a browser analytics preference. With analytics enabled, campaign information may also be stored for the browser session. This release does not set a landing-page experiment cookie. You can clear this storage in your browser, but doing so may sign you out or remove referral attribution.
Our optional first-party analytics use limited events and a random identifier stored in your browser. They are off unless you enable them in Privacy choices. The identifier expires within 90 days of creation. You can turn analytics off at any time in Privacy choices, which stops these events and removes the identifier from that browser. Event records already collected have the retention period below. We do not deliberately attach this identifier to your membership record, but it is pseudonymous information, not a guarantee of anonymity.
When your browser sends Global Privacy Control, we stop creating or sending the client analytics identifier and associated client events. This does not disable necessary network processing, security controls, referral storage, or necessary server-side records. Clearing local storage also removes the identifier from that browser. Email open and link-click tracking are disabled in our mailer.
6. Retention and deletion
We keep identifiable information for a defined purpose and remove it through scheduled cleanup or a verified request. The following limits apply to this release:
| Record | Retention limit |
|---|---|
| Unverified signup | 30 days after the request was created |
| Verified waitlist registration | Until you leave, or no later than 24 months after email verification. If the campus closes, removal within 30 days after closure applies if earlier. Opening a campus does not extend the 24-month maximum. |
| Ambassador information | Removed when you withdraw or delete the registration; a declined application is removed within 90 days after decline if earlier |
| Campus requests | 365 days after submission |
| Site analytics events | 395 days after the event |
| Application rate-limit counters | Two days; this is not the retention period for every provider log |
| Staff audit records | 365 days, unless a documented incident or legal obligation justifies longer retention |
| Verification and emailed access-link token records | Links expire after 1440 minutes or on earlier use or revocation. Token records are removed within two days after expiry or use. |
| Member sessions | Up to 30 days after issuance, or earlier on revocation. Expired session records are removed within two days. |
| Support, privacy-request, and incident correspondence | Routine support and access requests: up to 730 days after closure. Incident files are reviewed at closure and annually; only information needed for a legal obligation or documented dispute is retained longer.. Required security-breach records are kept for at least two years after we determine that a breach occurred, with any additional retention separately justified. |
| Minimum evidence of consent and withdrawal | 1096 days after each event. The record contains a keyed email digest, purpose, action, version and timestamp, without a plaintext email address or profile answers.. Kept separately from a deleted active registration and used only for compliance or resolving a dispute. |
| Minimum suppression record | While needed to honour a withdrawal or delivery restriction, with necessity reviewed at least annually. A fresh verified choice can supersede an earlier optional-email withdrawal. |
| Backups and company-controlled exports | Up to 28 days. Working exports are deleted when their task ends and no later than this limit; a minimal copy required for a compliance case follows that case's retention period.. Backups are restricted to recovery and security. Exports for support, compliance, or an access request are limited to that purpose and its approved period. Copies you download are under your control. |
| Provider email, traffic, and security records | Postmark message content and activity: 45 days, plus deletion processing of up to seven days. Cloudflare Workers Logs: 7 days. Other provider security and suppression records follow their security, compliance and unwanted-send prevention purposes, with necessity reviewed.. Provider suppression histories have a separate lifecycle. |
Scheduled deletion is not deletion to the second. We monitor cleanup failures and address delays. Where information must be retained for a legal obligation, a documented dispute, or a security investigation, we restrict its use and delete it when the reason ends. We do not use a possible future dispute to retain everything indefinitely.
Deleting a registration removes its active membership information, linked member tools, referrals, and ambassador answers. It does not recall emails from recipients, immediately erase an existing backup, or necessarily identify and remove unjoined analytics events. On restoring a backup, we reapply deletion and suppression decisions before normal use resumes. Our privacy team can explain which additional records remain and why, subject to lawful exceptions.
7. Your rights and requests
Member tools let you view or download registration information, change available choices, and leave. The download is a convenient export of member records, not necessarily every record held by us or a provider.
Contact tejass@anticipy.ai to request access to personal information, ask about its use or disclosure, correct it, withdraw consent, request deletion, or raise a complaint. We may ask for proportionate evidence that the request is yours. Do not send government ID unless we explain why it is necessary and provide an appropriate method.
We respond within applicable legal deadlines. Under PIPEDA, access requests normally receive a response within 30 days; the law permits limited extensions, for which we provide required notice. If a lawful exception limits access or deletion, we explain the decision and available recourse where permitted. You can complain to the Office of the Privacy Commissioner of Canada or another authority with jurisdiction. Contacting us first is not a waiver of that right.
8. Security, age, and changes
We use controls appropriate to the information, including restricted staff access, protected access links, abuse controls, and audit records. No system eliminates every risk. If a breach requires notice to you or a regulator, we provide it as required by law. This notice does not promise incident-free operation.
The waitlist is for adults 18 and older. If we learn that an ineligible minor has registered, we restrict the registration and remove unnecessary information. We assess requests and safety concerns without treating an email domain or age checkbox as independent age verification.
We date and version this notice. We explain significant changes before they take effect and obtain new consent when a new purpose or other change requires it. Continuing to browse does not automatically authorize a materially different use of personal information. Past versions and information about a change are available from the privacy contact.