DATING BY BIDPOINTX LLC
Privacy notice
Questions? manuel@bidpointx.com
Your privacy, in plain language
BidPointX LLC operates Current Dating by BidPointX and is responsible for the personal information described in this notice. This notice covers our website waitlist and the information processed when you use the Current app. Contact manuel@bidpointx.com for privacy, access, correction or deletion requests. Contact connect@bidpointx.com for waitlist removal or launch-update preferences.
The public launch waitlist
The Current website collects the name and email you submit and your confirmation that you are at least 18 and want launch updates. This request does not create an app account or prove adulthood. We save it privately in the Current Google Cloud database, send a confirmation email to the address you provide, and notify connect@bidpointx.com through Microsoft Graph. Confirming the email adds you to the launch list; unconfirmed requests are excluded from launch email exports. Confirmation links expire after seven days. A successful form means the request was saved; email delivery can be delayed or retried. Repeated submissions do not create duplicate list entries, and confirmation resends are limited. Use the opt-out link in the email or contact connect@bidpointx.com to stop updates and remove your name and email from the active list. A limited, non-readable identifier and request-rate history can remain until the original retention deadline to prevent queued messages or old links from restoring your subscription. Rejoining requires a fresh request and email confirmation. Requests and suppression records are scheduled for removal after 180 days by routine maintenance. Sent messages and operator notifications are retained separately in the mail service for support and delivery records. We use limited request-rate information to protect the form and do not include advertising trackers or analytics in the landing page.
What Current processes
Account identifiers and sign-in information; birth date and an adult-assurance decision/reference; your profile, photo, intentions and preferences; coarse discovery area, its derived time zone, recent foreground availability and optional short Ghost Lounge visibility; invitations, conversations, reports and blocks; consent records; purchase identifiers, entitlements and accounting records; and limited operational security information. Discovery preferences and location can reveal sensitive information. We do not need background location or address-book access.
Location without a public map
A device location is used transiently to derive a coarse discovery cell. The API does not publish your raw coordinates, cell identifier, exact distance or movement history to other users. Approximate location is supported. An explicitly selected exploration area is labeled separately from device presence. Coarse location reduces precision but cannot guarantee anonymity, especially in sparse areas. You control discoverability and can pause. A time zone derived from the device discovery area is used for the optional evening check-in reward; manual exploration does not establish reward eligibility.
City lookup and optional Travel
Current resolves city labels using a bundled GeoNames catalog, without sending your location to a geocoding provider. We store a coarse physical area and, when selected, a separate Travel destination and its entitlement deadline. Discovery uses the effective area; the physical area alone establishes the local reward time zone. Search queries are not saved as a travel history. Removing location permission clears discovery in the app; the server clears physical and Travel discovery state when it receives the request, while short visibility leases limit stale displays if the device is offline. Existing conversations and settings remain accessible to eligible accounts. City data is derived from GeoNames (www.geonames.org), licensed under Creative Commons Attribution 4.0 (creativecommons.org/licenses/by/4.0/), with settlement filtering, rounded public city centers and normalized search aliases. GeoNames does not endorse Current.
Age assurance and photos
The selected verification provider receives the material needed for its disclosed check under its own processing terms; Current stores a minimal result and reference. A birthday, phone number or device unlock is not proof of adulthood. The secure verification flow identifies the provider and presents its data-use notices before you submit evidence. If a required check is unavailable or unresolved, discovery and messaging stay restricted. Profile photos are resized with metadata removed, stored privately and reviewed before discovery. Do not submit identity documents to general support or upload them as profile photos.
Corrections and review requests
An appeal records your account reference, chosen reason, optional proposed birthday, optional explanation, status, timestamps and the decisions needed to resolve it. Authorized reviewers see the minimum verification decision details needed for that review. Identity documents belong in the secure verification provider flow, never in a general support note or profile upload. Operator actions are audited. Appeal records and provider receipts are included in the account deletion workflow, subject to separately documented legal or safety holds. Editing an email requires verification of the replacement address. Setup drafts stay in app memory and may be lost if the operating system closes the app before they are saved.
Why and with whom
We process information to authenticate accounts, enforce adult-only access, match mutual discovery settings, deliver consented conversations, moderate abuse, fulfill purchases, respond to rights requests and operate the service. Google Cloud/Firebase provide hosting and authentication, Apple and Google process native purchases, and the selected age provider performs assurance. Authorized operators can access information needed for a specific support or safety purpose. No advertising pixels or sale of profile, preference, precise location or private-message data are part of this implementation.
Visibility and retention
Foreground eligibility is a short lease, not a record that you are definitely looking at the screen. Profile authorization expires rapidly when not renewed. Ghost Lounge is off by default. If you explicitly enable it, your profile may remain visible to mutually eligible people for up to three minutes after leaving the foreground; it is labeled separately from live profiles. Its countdown is a visibility deadline, not a promise that you are looking at the app. Pause, disabling Ghost Lounge, restrictions and blocks revoke eligibility without waiting for that deadline; already rendered views have a short authorization lease. The app does not collect background location for this feature. Messages are not automatically cryptographically erased at the end of a Spark timer. Reports may preserve restricted evidence after a conversation closes. Account deletion immediately hides the account and revokes access, followed by tracked removal of profile, media and service data. Storage recovery copies can remain within the configured seven-day soft-delete lifecycle. Necessary accounting records, abuse-prevention records and legal holds require a documented purpose and review date.
Your choices and requests
Use the app to pause discovery, adjust who can discover you, opt out of location by removing device permission, export your information and delete your account. Contact support to correct information that cannot safely be edited, request an age-review appeal or exercise applicable privacy rights. Authentication may be needed before disclosure or deletion. Safety controls remain free. Declining optional notifications or the evening reminder does not block the service or reduce your included allowance. Ghost Lounge visibility is separately optional; it is not required to earn rewards or use ordinary discovery.
Optional notifications
If you opt in, Current uses an installation identifier and a push-delivery token linked to your account. Google Firebase Cloud Messaging and Apple Push Notification service deliver generic alerts. Previews do not include another person’s name, message text, profile photo or location. Acceptance alerts may mention an earned Shot and invite you back to a Spark without identifying the other person. A separate opt-in evening reminder may be scheduled on your device. Its arrival can be delayed by phone settings; only a successful server check-in grants the bonus. You can switch notifications and reminders off in Current or your phone settings. Delivery and removal depend on network and operating-system behavior; an alert already delivered to a device cannot be recalled remotely.
Privacy requests and changes
Depending on where you live and the law that applies, you may have rights to access, receive a copy of, correct, delete or limit the use of your information, object to processing, withdraw optional consent, and appeal a denied request. We do not penalize you for exercising privacy rights. Email manuel@bidpointx.com; a representative can contact us with evidence of their authority. We may verify ownership in a way appropriate to the request and explain any exception or denial. We respond within the deadline required by applicable law. Where the California Consumer Privacy Act applies, access, deletion and correction requests generally receive a response within 45 calendar days, with notice if a permitted extension is needed. You may complain to your local privacy regulator. We date policy updates and request a new in-app acknowledgment when required; a policy change does not retroactively authorize a new use without any legally required notice or consent.
Sensitive information and service providers
Your preferences, conversations, photos and coarse location may reveal sensitive information about you. We use that information for the service, eligibility and safety purposes described here, not to build advertising audiences. Google Cloud and Firebase process hosted service data and authentication; Microsoft processes waitlist confirmation emails and operator notifications; Apple and Google process native purchases and platform notifications. An enabled verification provider processes identity evidence through its secure flow. Your chosen profile and status are visible to mutually eligible members while discoverable; invitations and messages go to their intended participants. Information may also be disclosed when reasonably necessary to meet a legal obligation, respond to valid process, or protect people from abuse. We do not sell personal information or share it for cross-context behavioral advertising.
Where data comes from and is processed
We receive information you provide, recent device/session information needed for the service, verification decisions and store purchase events, and reports from other members. Service data is hosted in Google Cloud in the United States; a provider may process information in other locations under its applicable terms and safeguards. Choosing a Travel destination does not move data hosting to that city or establish your physical presence there. You can decline optional notifications, stop launch emails, pause discovery or remove location permission without purchasing anything.
Retention and account records
We retain an active account’s service data while needed to provide the account and its conversations. Waitlist database records have the 180-day schedule described above. Deletion starts the removal workflow for account, profile, media, verification-reference and appeal data. Limited transaction/accounting records, pseudonymized audit references, deletion records and restricted safety evidence can remain for a legal, security or accounting purpose. The reason for retention and applicable legal requirements determine the period; these retained records do not remain visible on the grid. Provider copies are subject to the provider’s disclosed retention and deletion process. Ask support for the status of your request or the reason for a retention exception.
Children and unwanted collection
Current is for adults aged 18 or older. A waitlist age confirmation is not identity verification. If you believe a minor has submitted information or accessed the service, use the in-app report tool or contact manuel@bidpointx.com. Access can be restricted while the concern is reviewed. We remove information collected in violation of applicable child-privacy law, except for information lawfully preserved for safety or reporting obligations.