SX Consent Application Sensitive Data Consent

SX Consent Sensitive Data Consent

Effective Date: May 14, 2026
Last Updated: May 14, 2026

This Sensitive Data Consent (“Consent”) applies to the SX Consent Application (“SX Consent,” “we,” “us,” or “our”), operated by Beniquez Sanchez and Company LLC and created by BS and Co AI Labs.

SX Consent is a private invitation, confidentiality, privacy, reputation-preservation, and protected recordkeeping platform for verified adults. SX Consent helps verified adults create protected private-invitation workflows, review private requirements, document privacy expectations, support agreement-based confidentiality records, and preserve contextual invitation records.

Because SX Consent may process information that is private, sensitive, identity-related, health-related, location-related, agreement-related, account-related, security-related, or protected-record-related, we require users to review and accept this Sensitive Data Consent before using certain features.

This Consent is intended to protect users, SX Consent, Beniquez Sanchez and Company LLC, SX Consent(TM), BS and Co AI Labs(TM), and their owners, officers, directors, managers, members, employees, contractors, agents, affiliates, vendors, providers, successors, and assigns (collectively, the “Company Parties”).

This Consent supplements and is incorporated into our:

Privacy Policy
Terms and Conditions
Health Data Handling Policy
SMS Terms
Account Deletion Policy
Data Deletion Policy
Refund and Returns Policy
in-app disclosures
account-readiness disclosures
identity verification disclosures
private-invitation agreement acknowledgments
Evidence Vault notices
provider-specific notices, where applicable

If you do not agree to this Sensitive Data Consent, you must not use SX Consent features that require sensitive data processing.

1. Important Summary

By using SX Consent and accepting this Sensitive Data Consent, you acknowledge, consent, and agree that SX Consent may collect, process, store, analyze, display, transmit, verify, retain, restrict, disclose, export, or otherwise handle Sensitive Data as reasonably necessary to provide SX Consent and its protected private-invitation workflows.

Sensitive Data may include, depending on your use of the platform:

legal name.
profile photo or profile photo status.
identity verification status.
adult verification status.
selfie/liveness verification status.
phone number.
email address.
device-linked status.
location information.
invitation-zone or location-readiness information.
relationship status, where provided.
gender, where provided.
private requirement profiles.
privacy expectations.
agreement acceptance records.
optional personal health-related information.
optional personal health document status or metadata.
vaccination-readiness selections, where enabled.
trusted contact configuration status, where enabled.
readiness-setting configuration status, where enabled.
Cross-Intake results.
private invitations.
signed agreement data.
signature metadata.
closure responses.
private notes.
help requested status.
operational notice logs.
audit events.
Evidence Vault metadata.
protected record package metadata.
contextual protected records.

SX Consent does not create future participation, permanent participation, legal immunity, or a waiver of rights. SX Consent does not erase risk. SX Consent records are contextual records, not legal conclusions and not absolute proof of any event.

This Consent relates only to the processing of Sensitive Data by SX Consent. It does not mean that you consent to any real-world private or personal conduct, any future invitation, any permanent arrangement, any medical decision, or any waiver of your legal rights.

2. Operator and Contact Information

Operator: Beniquez Sanchez and Company LLC

Creator: BS and Co AI Labs

Product: SX Consent Application

Mailing Address: 1317 Edgewater Dr. Num. 7387, Orlando, FL 32804

Legal Contact: Click Here

Privacy Contact: Click Here

Security Contact: Click Here

Support Contact: Click Here

Application: https://app.sxconsent.com

Website: https://sxconsent.com

3. Scope of This Consent

This Consent applies when you:

create an SX Consent account.
verify your email address.
verify your mobile phone number.
complete identity, adult, or eligibility verification.
upload or submit profile information.
link a device.
configure private requirements.
configure readiness settings.
configure health-related readiness items, where enabled.
upload, reference, or confirm optional personal health document status if the feature is enabled.
create or accept a private invitation.
complete Cross-Intake.
review or sign a one-time private invitation agreement.
use invitation-event timeline or participation-status controls.
enable location or invitation-zone features.
receive or acknowledge SMS, email, or in-app operational notices.
complete post-invitation closure.
save a private note.
request help or support.
export, verify, or access protected records.
request account deletion.
request data deletion.
contact support, legal, privacy, or security.

This Consent applies to websites, the PWA, mobile applications, backend systems, APIs, protected-record systems, identity workflows, SMS workflows, subscription systems, provider integrations, and support processes associated with SX Consent.

4. Adults-Only Sensitive Data Processing

SX Consent is strictly for verified adults who are at least 18 years old and legally permitted to use the platform.

You must not use SX Consent if you are under 18 or if you are legally prohibited from using the platform.

By accepting this Consent, you represent and warrant that:

you are at least 18 years old.
you are using your own legal identity.
you are legally permitted to provide the information you submit.
you are not impersonating another person.
you are not submitting false identity, health, relationship, location, account, or readiness information.
you are not using SX Consent to coerce, pressure, deceive, entrap, silence, threaten, exploit, harass, defraud, retaliate against, or harm anyone.

We may suspend, restrict, delete, block, or preserve information as needed if we believe Sensitive Data was submitted by or about a minor, by an unauthorized person, by a fraudulent user, or for unlawful, abusive, exploitative, or harmful purposes.

5. Meaning of “Sensitive Data”

For SX Consent, “Sensitive Data” means information that may be considered sensitive, private, legally protected, identity-related, location-related, health-related, relationship-related, account-security-related, agreement-related, or protected-record-related under applicable law, platform policy, provider policy, or our internal risk standards.

Sensitive Data may include information that is considered “sensitive personal information” under certain U.S. state privacy laws, “special category data” under some international laws, consumer health data under certain state laws, or sensitive user data under Apple, Google, Twilio, Stripe, or other provider policies.

Sensitive Data includes information that may not be inherently sensitive in every context but becomes sensitive when combined with SX Consent’s purpose, protected private-invitation workflows, relationship context, identity verification, location integrity, agreement records, or protected records.

6. Categories of Sensitive Data SX Consent May Process

Depending on your use of SX Consent, we may process the categories below.

6.1 Identity, Adult Verification and Eligibility Data

We may process:

legal first name.
legal last name.
date of birth or adult verification status.
identity verification status.
adult verification status.
identity provider workflow ID.
verification timestamps.
verification outcome.
verification failure or retry status.
selfie/liveness verification status.
document verification status.
profile photo.
profile photo status.
fraud-prevention signals.
jurisdiction.
eligibility status.
account-readiness status.

SX Consent may use third-party identity verification providers, including Stripe Identity or similar providers. Unless expressly stated otherwise, SX Consent does not intend to store raw government ID images, raw selfie/liveness images, or raw biometric templates in its own database. Those materials may be collected and processed by the provider according to the provider’s terms and privacy practices. SX Consent may store limited provider metadata, verification status, timestamps, and audit information.

6.2 Contact and Communication Data

We may process:

email address.
mobile phone number.
SMS opt-in status.
SMS opt-out status.
HELP and STOP activity.
phone verification status.
email verification status.
in-app notice status.
communication delivery logs.
notice acknowledgement status.
support communications.
security communications.
privacy request communications.
account deletion communications.
data deletion communications.

Sensitive details should generally be reviewed inside the app. We attempt to avoid exposing sensitive private-invitation details in SMS messages or email subject lines.

6.3 Device, Authentication and Security Data

We may process:

device identifier.
linked device status.
app version.
operating system.
browser.
IP address.
user agent.
login events.
authentication events.
PIN configured status.
biometric enabled status.
security settings.
device permission status.
fraud signals.
audit logs.
security events.
failed login records.
provider logs.
authentication tokens or token metadata.

6.4 Profile and Personal Context Data

We may process:

profile photo.
gender, where provided.
relationship status, where provided.
height, weight, or body type if voluntarily provided.
About Me information, where enabled.
jurisdiction.
user-selected profile fields.
verified profile indicators.
internal trust indicators.

Some profile fields may be visible to another verified user only when needed for a private invitation, identity confirmation, Cross-Intake, agreement generation, or protected-record workflow.

6.5 Private Requirements and Readiness Data

We may process:

location-readiness requirement.
notice-readiness requirement.
privacy agreement requirement.
post-invitation closure requirement.
no photos requirement.
no videos requirement.
no social media requirement.
no identity disclosure requirement.
optional personal health-related readiness requirement, where enabled.
private requirement selections.
custom private requirement notes.
accepted, declined, excluded, or reviewed requirements.
requirement version history.
Cross-Intake matched requirements.
review items.
blocking items.
compatibility status.

Private requirement data may include personal, relationship, privacy, location, health-readiness, or invitation-related preferences. This information is sensitive. It is intended for private compatibility and invitation-specific agreement workflows, not public discovery, public profile browsing, marketing, advertising, or social posting.

6.6 Optional Health-Related Data

If health-related features are enabled or selected, we may process:

health-related readiness requirement.
optional last-tested date, where provided.
optional personal health document status.
optional personal health document metadata.
document uploaded status.
document reviewed status.
document current/expired status.
vaccination-readiness selections, where enabled.
health-readiness acknowledgments.
health-related requirement acceptance or decline.
health-related workflow status.

SX Consent is not a healthcare provider, telemedicine provider, doctor, clinic, laboratory, pharmacy, insurer, or medical advisor. SX Consent does not provide medical advice, diagnosis, treatment, testing, result interpretation, clinical recommendations, or medical clearance.

Health-related information is processed only for private readiness, disclosure, compatibility, agreement, protected record, or documentation workflows, subject to the Health Data Handling Policy.

6.7 Private Context and Invitation Data

SX Consent may process information related to private invitation expectations, relationship context, privacy commitments, private requirements, and invitation-specific expectations if you voluntarily provide or accept them through the app workflow.

This may include:

relationship status, where provided.
privacy expectations.
private requirements.
invitation type or purpose.
private invitation context.
user-selected requirements.
no social media expectations.
non-disparagement expectations.
non-disclosure expectations.
agreement acceptance context.
accepted or declined items.
invitation-specific clauses.

SX Consent does not use this information to create public profiles, public matching, public search, public feeds, paid-interaction marketplaces, or public content monetization.

6.8 Location and Invitation-Zone Data

If location features are enabled or required, we may process:

device location.
approximate location.
precise location with permission.
invitation zone.
proposed address.
geocoding result.
arrival confirmation.
inside/outside zone status.
distance from invitation zone.
location permission status.
location failure events.
location integrity status.
IP-derived location.
location timestamps.
location audit events.

Location is intended for contextual invitation integrity, readiness, timing, and protected records. It is not intended for permanent tracking, continuous surveillance, public discovery, advertising, or unrelated monitoring.

6.9 Invitation, Agreement and Protected Record Data

We may process:

private invitation data.
inviter and invitee identifiers.
invitation ID.
proposed start and end time.
invitation status.
Cross-Intake data.
one-time private invitation agreement data.
accepted clauses.
declined or excluded items.
signature metadata.
signed timestamps.
protected record package IDs.
document hashes.
manifest hashes.
closure records.
operational notice logs.
audit events.
export logs.
verification logs.

These records may be retained as contextual protected records, even if you later delete your account, where retention is reasonably necessary for legal, protected-record integrity, fraud-prevention, security, multi-party records, dispute, compliance, or integrity purposes.

6.10 Private Notes, Support Requests and Help Requests

If available, SX Consent may process:

private closure notes.
help requested status.
support tickets.
user-submitted descriptions.
abuse or incident reports.
support-related documents or screenshots voluntarily submitted to support.

Private notes may be restricted, sealed, limited in visibility, or used only for specific workflows, depending on the feature design and applicable law.

7. Purposes for Processing Sensitive Data

SX Consent may process Sensitive Data for the following purposes:

verifying identity.
verifying adult eligibility.
preventing minors from using the platform.
authenticating users.
linking devices.
verifying phone and email.
preventing fraud.
preventing abuse.
detecting unauthorized access.
enforcing Terms and Conditions.
supporting private requirement profiles.
supporting optional health-related readiness features, where enabled.
enabling private invitations.
enabling Cross-Intake.
generating one-time private invitation agreements.
recording signatures and acknowledgments.
enabling invitation-event timeline and participation-status controls.
enabling location integrity.
sending required operational notices.
enabling post-invitation closure.
generating contextual protected records.
exporting or verifying protected record packages.
responding to legal, privacy, security, or support requests.
processing account deletion requests.
processing data deletion requests.
maintaining audit trails.
complying with law.
responding to valid legal process.
protecting users, the platform, providers, and the Company Parties.
defending legal claims.
resolving disputes.
preventing chargeback fraud.
maintaining provider compliance.
meeting Apple App Store, Google Play, Stripe, Twilio, payment provider, identity provider, or app store requirements.

8. Legal Bases and Express Consent

Where required, we process Sensitive Data based on:

your explicit consent.
performance of a contract.
compliance with legal obligations.
legitimate interests.
protection of rights, privacy, safety, and security.
fraud prevention.
establishment, exercise, or defense of legal claims.
vital interests in limited circumstances.
other legal bases permitted by applicable law.

By accepting this Sensitive Data Consent, you expressly consent to SX Consent processing Sensitive Data as described in this Consent, the Privacy Policy, the Terms and Conditions, the Health Data Handling Policy, the SMS Terms, and applicable in-app disclosures.

You may withdraw Sensitive Data consent where applicable, but withdrawal may limit or disable features that require Sensitive Data and may not delete records already generated, signed, sealed, shared with another participant, retained for legal reasons, or preserved for protected-record integrity.

9. Consent to Data Processing Only

This Sensitive Data Consent is only consent to the processing of Sensitive Data by SX Consent for platform-related purposes.

This Consent is not:

permission for any real-world private or personal conduct.
permission for any future invitation.
permission for any permanent arrangement.
a waiver of legal rights.
permission to be recorded by another user.
permission to be photographed or filmed by another user.
permission for public disclosure.
permission for social media posting.
medical consent or consent to medical treatment.
permission for emergency dispatch.
legal advice.
proof of what occurred outside the app.
proof that any real-world permission existed outside the app.

Each user remains responsible for their own decisions, communications, conduct, and participation outside the app. SX Consent records app-based actions and user-submitted information; it does not control or determine the real-world facts of any private interaction.

10. Visibility of Sensitive Data to Other Users

Some Sensitive Data may be visible to another verified SX Consent user only when necessary for a private workflow.

For example, another participant may see limited information required to:

identify who sent or received an invitation.
confirm that a user is a verified adult.
review private requirements.
review accepted, declined, or required items.
complete Cross-Intake.
review a one-time private invitation agreement.
confirm signature status.
review invitation status.
complete closure.
review protected record package metadata.

SX Consent does not make Sensitive Data publicly searchable. SX Consent does not create public profiles. SX Consent does not create public feeds. SX Consent does not sell access to Sensitive Data as public content.

You must not screenshot, copy, share, publish, threaten to publish, distribute, sell, disclose, exploit, shame, blackmail, extort, or misuse another user’s Sensitive Data.

11. Data Shared With Service Providers

SX Consent may use third-party providers to operate sensitive workflows. These may include:

identity verification providers.
adult verification providers.
SMS providers.
email providers.
app stores.
payment processors.
subscription infrastructure providers.
hosting providers.
database providers.
security providers.
fraud prevention providers.
crash monitoring providers.
mapping, geocoding, or address validation providers.
legal, compliance, and professional advisors.
customer support tools.

Providers may process Sensitive Data only as needed to provide services to SX Consent, comply with law, prevent fraud, verify eligibility, send notices, process payments, operate infrastructure, support platform functionality, or protect the Company Parties.

Third-party providers may have their own terms and privacy policies.

12. Identity Verification Provider Consent

If SX Consent uses a third-party identity verification provider, you consent to the provider collecting and processing information necessary for identity, document, selfie/liveness, and adult verification.

This may include:

government-issued ID images.
selfie images.
liveness checks.
document authenticity checks.
biometric-related verification analysis.
name and date of birth matching.
fraud checks.
provider logs.
verification workflow metadata.

SX Consent may receive limited results or status information from the provider, such as verified, requires input, processing, canceled, failed, expired, mismatch, or similar statuses.

SX Consent does not guarantee that identity verification will detect every false identity, forged document, synthetic identity, impersonation, misrepresentation, or unsafe user.

13. Biometric and Device Biometric Information

SX Consent may support biometric-related workflows through third-party verification providers or device operating systems.

Unless expressly stated otherwise:

raw biometric templates are not stored by SX Consent in its own database.
selfie/liveness verification materials are processed by a verification provider.
Face ID, Touch ID, or Android biometric authentication is handled by the device operating system.
SX Consent may store only status indicators, provider metadata, timestamps, and audit records.

If SX Consent later collects or stores biometric identifiers directly, SX Consent will provide additional notice and obtain consent where required by law.

14. Health-Related Data Specific Consent

By enabling, requiring, submitting, uploading, displaying, accepting, viewing, or relying on optional health-related features, you acknowledge and consent that SX Consent may process health-related information as described in this Consent and the Health Data Handling Policy.

You understand and agree that:

SX Consent is not a healthcare provider.
SX Consent does not provide medical advice.
SX Consent does not diagnose, treat, test, monitor, or interpret medical conditions.
SX Consent does not provide medical clearance.
SX Consent does not guarantee that health information from another user is truthful, current, complete, or medically meaningful.
health-related declarations are user-provided or provider-status-based information.
you should consult qualified medical professionals for medical decisions.
you should not rely on SX Consent as a substitute for testing, medical care, diagnosis, treatment, prevention guidance, or professional medical advice.

If you require another user to provide a health-related readiness item, SX Consent may require you to provide your own equivalent readiness item before imposing that requirement on another user, depending on feature design.

15. Location Data Specific Consent

By enabling or using location features, you consent to SX Consent processing location information for invitation-zone, readiness, timing, integrity, audit, protected record, and app workflow purposes.

You understand and agree that:

location may be approximate or inaccurate.
GPS may fail.
device permissions may change.
network conditions may affect accuracy.
location may be spoofed or manipulated by users.
SX Consent cannot guarantee location accuracy.
location records are contextual signals, not absolute proof.
location is not used for permanent tracking, public tracking, unrelated surveillance, advertising, or public discovery.
disabling location may block or limit certain features where location readiness is required.

16. Trusted Contacts and Emergency-Adjacent Configuration Metadata

If SX Consent supports trusted contact, help-request, or emergency-adjacent configuration workflows, you consent to SX Consent processing related configuration status and limited metadata.

SX Consent should not display raw sensitive configuration information publicly or unnecessarily. The platform may process configured/not configured, status, hashed, or event-related information for privacy, account-readiness, support, protected-record, or workflow-integrity purposes.

You are responsible for selecting trusted contacts and any optional support-related configuration carefully.

SX Consent does not guarantee emergency intervention, live response, law enforcement contact, rescue, medical assistance, physical security, or prevention of harm.

17. SMS, Phone, Email and In-App Notice Consent

By providing your mobile number and opting in to SMS, you consent to SX Consent and its providers processing your phone number, verification status, message delivery data, opt-in status, opt-out status, and related logs.

SX Consent may send transactional and operational SMS messages, including:

verification codes.
account security notices.
app-readiness notices.
invitation status notices.
review and signature notices.
closure reminders.
privacy request updates.
account deletion notices.
data deletion notices.
support notices.

Message and data rates may apply. Message frequency may vary.

You may reply STOP to opt out and HELP for help, where supported. Opting out may prevent use of features requiring operational notices.

SX Consent does not sell or share SMS opt-in consent or mobile numbers with third parties or affiliates for their marketing or promotional purposes.

SX Consent may also send email and in-app notices for account, invitation, signature, readiness, closure, privacy, support, subscription, and security workflows. Sensitive details should generally be reviewed inside the app.

18. Protected Records and Sensitive Data

SX Consent may include Sensitive Data in contextual protected records when necessary to preserve the integrity of an invitation-specific record.

Protected records may include:

agreement metadata.
accepted terms.
signature records.
identity readiness indicators.
invitation status changes.
location integrity events.
operational notice logs.
closure responses.
audit events.
timestamps.
hashes.
Evidence Vault metadata.
protected record package metadata.

Protected records are contextual. They are not legal conclusions. They are not absolute proof. They do not guarantee admissibility, enforceability, legal outcome, or protection against claims.

You consent to SX Consent retaining Sensitive Data in protected records where reasonably necessary for protected-record integrity, legal claims, dispute resolution, fraud prevention, security, compliance, provider requirements, or multi-party record preservation.

19. Data Minimization

SX Consent intends to process Sensitive Data only as reasonably necessary for the purposes described in this Consent and related policies.

However, because SX Consent involves identity verification, private invitation records, signed agreements, protected record packages, and multi-party workflows, certain records may need to be retained to preserve integrity, defend claims, resolve disputes, comply with law, enforce Terms and Conditions, or protect users, the platform, providers, and the Company Parties.

Do not submit Sensitive Data that is not requested or necessary for the feature you are using.

20. Retention of Sensitive Data

Sensitive Data may be retained for different periods depending on the type of data, feature, legal need, protected-record status, account status, dispute status, provider requirement, security need, and applicable law.

We may retain Sensitive Data as needed to:

provide SX Consent.
maintain account readiness.
verify identity and age status.
maintain invitation records.
preserve signed agreements.
preserve protected record packages.
respond to disputes.
defend legal claims.
prevent fraud.
prevent abuse.
support chargeback defense.
comply with law.
maintain audit logs.
process deletion requests.
protect users, the platform, providers, and the Company Parties.

Deletion requests may not apply to all Sensitive Data, especially where records involve multiple users, signed agreements, sealed protected record packages, legal holds, fraud prevention, provider records, safety-related events, audit logs, or legal obligations.

21. Withdrawal of Sensitive Data Consent

You may withdraw Sensitive Data consent where applicable by:

disabling certain app features.
changing device permissions.
updating privacy settings.
contacting Click Here.
submitting a data deletion request.
deleting your account, subject to retention limitations.

Withdrawal of consent may result in:

inability to verify identity.
inability to verify adult eligibility.
inability to use private invitation features.
inability to send or accept invitations.
inability to use health-related features.
inability to use location integrity features.
inability to use active invitation features.
inability to receive required operational notices.
account restriction.
account suspension.
account deletion process.
preservation of prior records where required or permitted.

Withdrawal of consent does not automatically delete records already created, signed, sealed, exported, shared with another participant, retained for legal reasons, or needed for protected-record integrity.

Withdrawal of consent does not create a refund right.

22. Account Deletion and Sensitive Data

You may request account deletion through the Account Deletion process.

Account deletion may not delete all Sensitive Data. SX Consent may retain certain records where reasonably necessary for:

legal compliance.
protected-record integrity.
multi-party invitation records.
signed agreement history.
audit logs.
safety-related events.
provider compliance.
fraud prevention.
security investigations.
chargeback defense.
dispute resolution.
enforcement of Terms and Conditions.
tax or accounting obligations.
legitimate legal claims.

Deleting your account does not automatically cancel your subscription unless the applicable subscription process confirms cancellation. Deleting your account does not entitle you to a refund.

23. Data Deletion Requests

You may request deletion of eligible Sensitive Data through the Data Deletion process.

SX Consent may deny, delay, limit, or partially fulfill a deletion request where deletion would:

violate law.
interfere with protected-record integrity.
compromise another user’s records.
affect signed agreements.
affect sealed protected record packages.
compromise security.
prevent fraud investigation.
affect legal claims.
violate provider obligations.
be technically infeasible.
conflict with legitimate retention needs.

We may de-identify, restrict, archive, aggregate, hash, segregate, or preserve data instead of deleting it where permitted or required.

24. No Sale of Sensitive Data

SX Consent does not sell Sensitive Data for money.

SX Consent does not sell health-related information.

SX Consent does not sell private requirement profiles.

SX Consent does not sell protected records.

SX Consent does not sell location integrity records.

SX Consent does not sell SMS opt-in consent or mobile numbers.

SX Consent does not intend to use Sensitive Data for targeted advertising.

If our practices materially change, we will update our disclosures and provide legally required rights or choices.

25. Artificial Intelligence and Sensitive Data

SX Consent may use automation or AI-assisted systems for limited operational purposes, such as:

fraud detection.
security monitoring.
support routing.
diagnostics.
app-readiness evaluation.
policy enforcement.
protected-record integrity checks.
abuse detection.
system reliability.

SX Consent does not intend to use private invitation records, private requirement data, optional health-related information, signed agreements, closure notes, or protected record packages to train public AI models.

If SX Consent introduces AI features that materially process Sensitive Data in a new way, we will provide additional disclosures and obtain consent where required.

26. Security of Sensitive Data

We use reasonable administrative, technical, and organizational safeguards designed to protect Sensitive Data, including:

encryption in transit.
access controls.
account authentication.
role-based access restrictions.
audit logging.
security monitoring.
provider controls.
separation of sensitive storage where practical.
limited visibility.
event hashing or integrity checks where applicable.
incident response procedures.
least-privilege principles.
internal access restrictions.

No system can be guaranteed completely secure. You are responsible for securing your device, account, email, mobile number, password, PIN, biometric access, and notification settings.

If you believe Sensitive Data was compromised, contact Click Here.

27. User Responsibilities

You agree to:

provide accurate information.
not impersonate anyone.
not submit false health, identity, relationship, location, or eligibility information.
not misuse another user’s Sensitive Data.
not screenshot, share, publish, disclose, threaten, blackmail, or extort using another user’s Sensitive Data.
not use SX Consent to coerce or pressure anyone.
not use SX Consent to silence legitimate legal rights.
not manipulate protected records.
not spoof location.
not evade verification.
not bypass app controls.
respect another user’s decision to leave, stop, decline, or not participate.
comply with all applicable laws.
secure your device and account.
promptly report unauthorized access.

Violation of these responsibilities may result in account suspension, termination, record preservation, legal action, reporting to providers, or disclosure where required or permitted by law.

28. Provider and Platform Requirements

SX Consent may be required to process or disclose certain Sensitive Data to comply with requirements from:

Apple App Store.
Google Play.
Stripe.
Twilio.
RevenueCat.
identity verification providers.
payment processors.
SMS providers.
email providers.
hosting providers.
law enforcement.
courts.
regulators.
professional advisors.

Certain provider requirements may affect your access to SX Consent. For example, failure to complete identity verification, phone verification, SMS opt-in, app readiness, or required permissions may prevent use of certain features.

29. International Processing

SX Consent is operated from the United States. Sensitive Data may be processed in the United States or other jurisdictions where our service providers operate.

By using SX Consent, you understand that your information may be transferred to and processed in jurisdictions that may have data protection laws different from those in your location.

Where required by law, we may use appropriate safeguards for international transfers.

30. Law Enforcement, Legal Process and Safety Disclosures

We may access, preserve, or disclose Sensitive Data if we believe it is reasonably necessary to:

comply with law.
respond to subpoenas, court orders, or legal process.
respond to government requests.
enforce Terms and Conditions.
investigate fraud, abuse, or security incidents.
prevent harm.
protect rights, privacy, safety, or property.
preserve protected records.
defend legal claims.
respond to user disputes.
comply with provider obligations.

We may challenge or narrow requests where appropriate, but we are not required to do so in every case.

31. Sensitive Data in Multi-Party Records

Some SX Consent records may involve more than one user. Examples include:

invitations.
Cross-Intake records.
agreements.
signatures.
active invitation records.
closure responses.
location integrity events.
operational notice logs.
protected record packages.

Because these records may belong to or affect multiple users, one user’s deletion, withdrawal, account deletion, or objection may not automatically remove, alter, or delete multi-party records.

SX Consent may preserve multi-party records where necessary for protected-record integrity, legal claims, dispute resolution, safety, fraud prevention, compliance, or rights of another participant.

32. Limits of Consent and Platform Responsibility

SX Consent uses Sensitive Data to provide private documentation workflows. SX Consent is not responsible for:

another user’s false statements.
another user’s misuse of your information.
screenshots taken outside the app.
recordings made outside the app.
social media posts made outside the app.
legal outcomes.
medical outcomes.
relationship outcomes.
reputational outcomes.
emotional harm caused by another user.
failure of another user to comply with an agreement.
actions outside the SX Consent workflow.
device-level notification previews.
unauthorized access caused by your failure to secure your device or account.

SX Consent may take reasonable steps to protect data within its systems, but it cannot control every action taken by users, third parties, device operating systems, app stores, providers, or external platforms.

33. Changes to This Sensitive Data Consent

We may update this Sensitive Data Consent from time to time due to changes in:

law.
provider requirements.
Apple App Store requirements.
Google Play requirements.
Twilio requirements.
Stripe requirements.
app features.
identity verification workflows.
health-related features.
protected-record workflows.
security practices.
business operations.

Material changes may be communicated through the website, app, email, in-app notice, or other reasonable method.

Continued use of SX Consent features requiring Sensitive Data after the updated Consent becomes effective means you acknowledge and accept the updated Consent, where permitted by law.

34. Acknowledgment and Express Consent

By clicking “I Agree,” checking a consent box, signing electronically, completing onboarding, submitting Sensitive Data, enabling a sensitive feature, creating or accepting a private invitation, completing Cross-Intake, signing an agreement, using active invitation features, enabling location, enabling health-related features, submitting closure responses, exporting protected records, or otherwise using SX Consent, you expressly acknowledge and consent that:

You have read this Sensitive Data Consent.
You understand that SX Consent may process Sensitive Data.
You understand that some Sensitive Data may be visible to another verified participant only when necessary for a private workflow.
You understand that SX Consent may use third-party providers to process Sensitive Data.
You understand that SX Consent is not a public dating platform, public matching service, healthcare provider, law firm, emergency service, or public safety agency.
You understand that SX Consent does not create future participation or permanent participation.
You understand that this Consent applies to data processing, not real-world conduct.
You understand that SX Consent does not provide legal immunity.
You understand that SX Consent records are contextual, not absolute proof.
You understand that withdrawal of Sensitive Data consent may disable certain features.
You understand that account deletion or data deletion may not erase all records where retention is legally, technically, operationally, or contractually required.
You understand that deleting your account or withdrawing consent does not create a refund right.
You agree to comply with the Terms and Conditions, Privacy Policy, Health Data Handling Policy, SMS Terms, Account Deletion Policy, and Data Deletion Policy.

35. Contact Us

For questions about this Sensitive Data Consent:
Privacy: Click Here
Legal: Click Here
Security: Click Here
Support: Click Here

Mailing Address:
Beniquez Sanchez and Company LLC
1317 Edgewater Dr. Num. 7387
Orlando, FL 32804