Last Website Waitlist Privacy Notice

Notice version: 2.2
Effective date: October 31, 2026
Operator: Elysian Studios LLC ("Last," "we," "us")
Privacy contact: [email protected]
Remove Me: https://lastdating.app/privacy-rights.html
Full Privacy Policy: https://lastdating.app/privacy.html

Last tracks and analyzes use of its website and waitlist. It counts visits through its source links, credits each waitlist submission that came through a source link to the first link it came through, and keeps totals by link, stage, gender, broad region and calendar month. Section 1 describes the cookie and the network-address code this uses, and Section 7 how long each is kept.

1. Information collected

The waitlist form collects the following:

• email address;
• phone number, normalized for contact, duplicate/fraud prevention, invitation binding, and later same-phone verification where applicable;
• exact age, collected as an integer rather than date of birth;
• gender;
• genders sought;
• region or other location information used for the pre-launch interest record;
• an optional coupon or invitation code, if the form offers one;
• the marketing source code carried by the link through which you reached the form, if any, and its human-readable source label; and
• consent/acknowledgment choice, notice version, and timestamp.

Network address. When you submit the form, your device's network address (IP address) reaches the servers that host the website and the waitlist database, as it does on any website. The waitlist database does not store the address. To limit the number of submissions from one address in a short period, it stores a code derived from the address, the current UTC date and a secret value with a one-way hash, together with the time window and a count of submissions. The code changes every day, cannot be turned back into the address without the secret value, and is deleted within about three hours. If a submission reaches the database without an address, Last records only a diagnostic code and the time.

Source links. Last's source links are web addresses that begin lastdating.app/r/, and a QR code may open one. Every source link opens the same homepage and the same waitlist form, and Last uses them to count how many visits and submissions each link brings. When you open an active source link, the website sets one cookie in your browser. The cookie holds the link's code, the time it was set, a random value and a check value made by the waitlist database, and it expires 30 days after it is set. If you open another source link while the cookie is still valid, the website keeps the first one. When you submit the form, the form sends the cookie's contents with your submission; the waitlist database checks them and records with your submission the link's code, its label as it stood when you opened the link, and the time you opened it. If there is no cookie, or its contents fail that check, your submission is recorded without a source, and in the second case Last records only a diagnostic code and the time. The website reads the cookie to keep the first link and to send it with a submission, and its contents go to the website and, with a submission, to the waitlist database. You can delete the cookie in your browser at any time; a submission made after that is recorded without a source unless you open a source link again.

Visits through source links. Last counts each visit through an active source link, by link and calendar month, whether or not you submit the form; the count keeps no network address, cookie or other detail about you. Visits by known link-preview services and other automated programs are not counted, and a retired, unknown or malformed link opens the homepage and records nothing. To limit how often one network address can open source links in a short period, your network address passes from Last's website host and network security provider to the waitlist database (run by Last's database provider), which keeps only a code derived from it in the way described above for the form and deletes that code within about three hours; if no address arrives, Last records only a diagnostic code and the time.

If the form changes, Last updates this Notice before accepting submissions through the changed form. Do not submit medical information, government-identification documents, payment-card information, passwords, precise member-location history, private-message content, or unnecessary information about another person through the waitlist form.

2. Sensitive inference notice

Your selection of the genders you are seeking describes who you may want to meet. Alone or together with your own gender selection, that information may reveal or allow Last to infer information about sexual orientation.

Last uses the intake fields for the specific waitlist/Beta purposes described below. Last will not silently repurpose them for an unrelated materially different use. A materially new use requires an updated notice and any consent or acknowledgment required by applicable law.

3. How we use waitlist and Beta intake information

We may use the information to:

• receive, validate, secure, and deduplicate your submission;
• contact you about the waitlist, launch, or closed Beta;
• prevent duplicate, fraudulent, or abusive submissions;
• compose and evaluate a functional closed-Beta group using the disclosed intake fields;
• determine Beta eligibility;
• validate an optional coupon or invitation code when the form offers that field;
• bind an invitation to the submitted phone number and require verification of the applicable phone before redemption;
• link your submission to a Last account: if your invitation is redeemed, to the redeeming account, which receives a copy of your submission's source code and label; otherwise, without copying anything, to an account that verifies the same phone number by one-time passcode at registration;
• administer Beta agreements, surveys, participation records, and any separately applicable reward eligibility if selected;
• measure intake, selection, cohort, and launch-interest outcomes;
• count visits, submissions and invitations by source link, as described in Sections 1 and 7;
• operate the pre-launch interest counter described below;
• respond to privacy/removal requests; and
• comply with law and protect the security and integrity of the intake process.

Submitting the form or entering a code does not create a Last account, create a paid Premium subscription, waive later identity/photo verification, bypass admission or safety rules, guarantee Beta selection, guarantee launch admission, or guarantee continuous access after launch.

4. Pre-launch exact 100-km interest counter

If the pre-launch interest counter is enabled, a validated waitlist/interest submission is written to the designated pre-launch interest dataset with the location used for that interest record.

The public pre-launch counter may display the exact number of qualifying pre-launch interest records within 100 kilometers of the counter location. The number is not rounded, suppressed, or hidden merely because it is small; the displayed count may be 1.

This counter measures pre-launch interest records, not active Last member accounts or profiles. It does not authorize Last to publish an exact 100-km count of active users after launch. Validated rows are counted under the intake system's ordinary validation and uniqueness rules rather than through a separate counter-specific identity system.

Your qualifying interest record may contribute to this aggregate exact count while the record remains eligible under the intake/retention rules. The public counter does not display your name, phone number, email address, gender, genders sought, age, or individual location record.

5. Phone-number use and invitation binding

The submitted phone number may be used as the binding identifier for a Beta or launch invitation where the invitation flow is enabled. If an invitation is bound to that number, redemption may require one-time-passcode verification using the same number.

A different phone number cannot redeem a phone-bound invitation unless Last approves a documented correction through a secure process. Last's website and support do not reveal to an unverified requester whether a particular phone number has an application, selection, invitation, or internal status.

6. Service providers and disclosures

We may disclose waitlist information to service providers that host the website or database, deliver email/SMS or verification codes, secure the intake system, provide analytics approved for this intake, or otherwise help operate the waitlist/Beta process. They may process information only for the authorized service and subject to applicable contractual and security restrictions.

Providers: Last's website host and network security provider; Last's database provider (waitlist database); a content delivery network that serves the open-source library your browser uses to send the form; Last's email provider (Last's email, including [email protected] and the invitation and waitlist emails Last sends); an AI service that sorts messages sent to [email protected] so they reach the right request process; a text-message provider, through the database provider, that sends the one-time code when you redeem an invitation; and a cloud hosting provider that runs Last's support services, including the support chat and the handling of messages sent to [email protected]. Each receives waitlist information only when Last uses it for the role listed. Your browser connects directly to the website host to load the website, to the content delivery network to fetch the library and to the database provider to send the form, so each of the three receives your network address in the course of serving that connection, as any server you connect to does, and may keep it in its own logs under its own privacy terms. Last does its own analysis of waitlist information, including the source-link counts described in Section 1, with the providers listed here.

We may also disclose information when required by valid legal process or reasonably necessary to investigate fraud/abuse, protect a person, or secure the intake system.

Under the current authorized model, Last does not sell waitlist information or share it for cross-context behavioral advertising.

7. Retention

Unless an applicable legal requirement or narrow documented preservation hold requires different treatment:

• Waiting submissions and their source: a submission is hard-deleted, together with its source code and label, 180 days after the latest of its submission, its latest affirmative consent refresh, and any invitation sent to it, unless the invitation is redeemed first.
• Consent refresh: before that deadline, Last may ask you to affirmatively refresh consent/acknowledgment. A refresh counts only if you give it affirmatively before the deadline; it records the notice version and time, keeps the submission's first-touch source, and is not a new submission.
• No refresh: at the end of the applicable 180-day period, Last hard-deletes the submission and its source unless its invitation was redeemed first or a narrow documented legal-preservation hold applies.
• Withdrawn submissions: deleted within 30 days after a verified withdrawal or Remove Me request, subject only to a narrow documented legal-preservation hold. A submission with a verified Remove Me request, or kept past its deadline by a legal hold, is withdrawn: its unredeemed invitation is revoked at once, and it is never invited, linked, or counted again. A submission covered by a narrow documented legal hold is kept only while the hold lasts; anything overdue is deleted when the hold is released.
• Selected submissions and redeemed invitations: if your invitation is redeemed, your submission's source code and label are copied to the resulting Last account, which keeps them until that account is hard-deleted under the account-deletion rules. The submission itself is hard-deleted when the account completes registration (every registration prerequisite met), when the account is hard-deleted, or 180 days after redemption, whichever comes first. A submission linked to an account by phone match is also hard-deleted when that account is hard-deleted. The account, verification, Beta, survey, and retention rules then apply to the account's records.
• Population-safe historical aggregates: may remain where they no longer identify or map back to you under the applicable retention policy.
• Source-link totals: Last keeps counts by source link (submissions without a source are counted together), by stage (a visit, a submission, and an invitation sent), by gender (for submissions and invitations), by broad region and by calendar month. Each counted visit adds one; a submission adds one when it is made and one more when an invitation is first sent to it. These counts hold no contact detail and no reference to a submission, are kept indefinitely, and are not reduced when a submission is deleted.
• Source-link cookie and codes: the cookie described in Section 1 expires in your browser 30 days after it is set. After a submission uses the cookie's contents, the waitlist database keeps the cookie's random value for 31 days, so that the same cookie cannot be counted for a second submission, then deletes it. The network-address code used for source links is deleted within about three hours of the visit.
• Rate-limit code and diagnostics: the network-address code described in Section 1 is deleted within about three hours of the submission; diagnostic codes (a code and a time, with no address or contact detail) are deleted after 90 days.
• Privacy-request records: Last keeps a record of each Remove Me or privacy request (its kind, a verification reference, and when it was received and completed, with no contact detail) and the request correspondence for 24 months after the request is completed, then deletes them.

Deletions run on an hourly schedule, so a submission whose deadline has passed is deleted within the hour unless a legal hold applies. There is no indefinite applicant pool under this Notice.

8. Remove Me and privacy requests

You may withdraw your waitlist/Beta submission through:

Remove Me: https://lastdating.app/privacy-rights.html

You may also contact:

[email protected]

Last may verify control of the submitted phone number or other intake contact information before acting. The removal process does not reveal to an unverified requester whether a record exists.

A verified Remove Me request changes the submission to withdrawn and schedules deletion within 30 days, subject only to a narrow documented legal-preservation hold. Last keeps a record of the request, without contact details, for 24 months as described in Section 7.

Depending on applicable law, you may also have rights to access, correct, delete, or limit certain uses of your personal information. The full Privacy Policy explains the available rights and request process.

9. Security

Waitlist records are stored in a restricted intake system. They are not publicly browsable, do not create a member profile, and do not bypass later account security, admission, or verification requirements.

No system is perfectly secure. Contact [email protected] if you believe the waitlist form or your submission has been compromised.

10. Changes to this Notice

We may update this Notice. The version and effective date identify the notice applicable to a submission. If Last wants to use existing waitlist information for a materially new purpose, extend retention beyond the disclosed rule, or collect a new sensitive category, Last will provide an updated notice and obtain any consent or acknowledgment required by applicable law.

Summary shown with the waitlist form

The waitlist form shows this summary next to its submit button:

Waitlist privacy: We collect your phone number and the form information you submit to contact you, prevent duplicate or fraudulent submissions, administer the waitlist/Beta, and bind any invitation to the applicable verified phone. Your gender and genders-sought selections may reveal or allow us to infer sexual orientation. If the pre-launch interest counter is enabled, your validated interest record may be included in the exact number of qualifying pre-launch interest records within 100 km shown publicly; this is not a count of active Last users or profiles. A waiting submission is deleted 180 days after the latest of its submission, its latest consent refresh and any invitation sent to it, unless the invitation is redeemed first; verified Remove Me requests are deleted within 30 days. To limit abuse, the database keeps a one-way code derived from your network address for up to about three hours, never the address itself. Last tracks and analyzes use of its website: if you open one of Last's source links (addresses beginning lastdating.app/r/), the website sets a cookie for 30 days that records which link you came through, the form sends it with your submission, and Last counts visits and submissions by link. Submitting does not create an account or guarantee Beta or launch admission. Read the Waitlist Privacy Notice · Remove me

Acknowledgment

Before you submit, the form asks you to check this box:

[ ] I have read the Waitlist Privacy Notice and understand the collection, sensitive inference, uses, pre-launch interest-counter use where enabled, retention, and Remove Me process.

Last keeps the notice version and the time of your acknowledgment with your submission.