SX Consent Privacy Policy

Effective Date: July 12, 2026
Last Updated: July 12, 2026

SX Consent Application (“SX Consent,” “we,” “us,” or “our”) is operated by Beniquez Sanchez and Company LLC and was created by BS and Co AI Labs.

SX Consent is a private confidentiality, privacy, and contextual protected-records platform designed for verified adults. The platform helps verified adults document invitation-specific privacy expectations, private requirements, confidentiality commitments, readiness details, invitation status changes, post-invitation closure responses, and contextual protected records tied to specific private invitation workflows.

This Privacy Policy explains how we collect, use, process, disclose, retain, protect, and otherwise handle information when you access or use our websites, mobile applications, progressive web application, backend systems, APIs, protected-record services, communications, account features, and related services.

SX Consent is not a public matching service, public user-discovery platform, public social network, telemedicine provider, emergency response service, insurance product, financial institution, law firm, or legal services provider. SX Consent does not create future participation, permanent participation, legal immunity, guaranteed outcomes, or absolute proof of any real-world event.

1. Contact Information

Operator: Beniquez Sanchez and Company LLC
Product Creator: BS and Co AI Labs
Product and Brand: SX Consent Application and SX Consent™
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
Website: https://sxconsent.com

Related policies and resources include the Terms and Conditions, Sensitive Data Consent, Health Data Handling Policy, Refund and Returns Policy, SMS Terms, Account Deletion Policy, Data Deletion Policy, Contact and Support resources, and any in-app privacy, account-readiness, subscription, identity-readiness, agreement, or protected-record notices displayed to users.

2. Scope of This Privacy Policy

This Privacy Policy applies to information collected or processed through:

sxconsent.com and related SX Consent websites;
app.sxconsent.com;
the SX Consent mobile application, when available through Apple App Store or Google Play;
the SX Consent progressive web application;
SX Consent account registration and onboarding;
identity, adult eligibility, and account-readiness workflows;
phone, email, and device verification workflows;
private requirement profiles and private compatibility features;
private invitations, Cross-Intake, agreement generation, signature workflows, active invitation controls, closure workflows, Evidence Vault, and protected-record exports;
SMS, email, in-app, support, legal, privacy, and operational communications;
provider integrations used to operate, secure, support, audit, and improve SX Consent.

This Privacy Policy does not apply to third-party websites, services, app stores, payment platforms, identity verification providers, communication providers, hosting providers, or other platforms that we do not control, even if they are linked from SX Consent. Third-party providers may have their own privacy policies, security practices, and data-processing terms.

3. Eligibility and Adults-Only Use

SX Consent is intended only for adults who are at least 18 years old and who complete required identity, adult eligibility, account-readiness, and security steps.

SX Consent is not intended for minors. We do not knowingly permit minors to create accounts or use SX Consent. If we learn that a person under 18 has created an account or provided information, we may suspend the account, delete or restrict information, preserve limited records needed for legal, fraud-prevention, safety, security, or compliance purposes, and take other appropriate action.

If you believe a minor has submitted information to SX Consent, contact us through the applicable support, privacy, safety, or security channel listed in this Policy.

4. Categories of Information We May Collect

The exact information we collect depends on your use of SX Consent, the features available at the time, your jurisdiction, your plan, your device permissions, and the choices you make.

4.1 Account and Contact Information

legal first name and legal last name;
email address;
mobile phone number;
username or internal user identifier;
account credentials or authentication data;
account status and account-readiness status;
communication preferences;
support, legal, privacy, or security requests;
date and time of account creation;
account deletion or data deletion request status.

4.2 Identity, Adult Verification, and Account-Readiness Information

SX Consent may require identity, age, and adult eligibility verification. We may collect or process:

identity verification status;
adult verification status;
verification provider invitation ID or transaction ID;
verification timestamps;
verification results or limited verification metadata;
jurisdiction, country, state, territory, or region of primary use;
fraud-prevention indicators;
account trust, eligibility, and readiness status.

SX Consent may use third-party identity verification providers, such as Stripe Identity or similar providers, for official ID document review, selfie/liveness checks, and adult verification. Unless expressly stated otherwise, SX Consent does not intend to store full government ID images, selfie/liveness images, raw biometric templates, or official identity document scans directly in its own database. Those materials may be collected and processed by the identity verification provider under that provider’s own privacy terms and contractual obligations.

4.3 Profile, Eligibility, and Account Display Information

profile photo or profile photo status;
gender, relationship status, or profile information if voluntarily provided or required by a workflow;
“About Me” information, if enabled;
jurisdiction or region;
device-linked status;
PIN configured status;
biometric enabled status from the device or provider;
Sensitive Data Consent status;
Terms accepted date;
Privacy Policy accepted date;
onboarding step and onboarding status.

Some profile or eligibility information may be visible to another verified app user only when needed for a private invitation, identity confirmation, Cross-Intake, agreement generation, or invitation-specific workflow. SX Consent is not designed to publish public profiles or enable public user discovery.

4.4 Phone, SMS, and Messaging Information

mobile phone number;
SMS opt-in status;
SMS opt-out status;
verification code request metadata;
delivery status;
message type and template identifier;
message timestamps;
carrier-related metadata;
country or region;
HELP or STOP keyword activity;
notice logs;
provider delivery events.

SX Consent SMS messages are intended to be transactional, operational, account-related, verification-related, invitation-related, readiness-related, privacy-related, signature-related, or closure-related. We do not sell or share SMS opt-in information for third-party marketing or promotional purposes.

4.5 Email and In-App Notice Information

email verification status;
email delivery logs;
in-app notification logs;
notice acknowledgement status;
notice delivery status;
notice timing and retry metadata;
security, privacy, account, invitation, signature, closure, and app-readiness notice records.

Operational notices may be required for certain SX Consent features. Unless separately enabled and disclosed, SX Consent does not use native mobile notification delivery as an active notice channel for the current iOS app workflow described by this Policy.

4.6 Payment, Subscription, and Purchase Information

subscription status;
plan type;
purchase history;
transaction identifiers;
renewal status;
cancellation status;
app store receipt or entitlement metadata;
provider identifiers from Apple, Google, RevenueCat, Stripe, or other payment providers.

We do not intend to store full credit card numbers or full payment card security codes. Payment information may be processed by Apple, Google, RevenueCat, Stripe, or another payment processor according to their own privacy and security practices.

4.7 Private Requirement Profile Information

SX Consent may allow users to configure private requirements, preferences, privacy expectations, readiness settings, location-readiness details, and related invitation conditions. This information may include:

privacy agreement requirement;
identity discretion preference;
location-readiness requirement;
notification-readiness requirement;
post-invitation closure requirement;
device and recording restriction preferences;
photo, video, screenshot, screen-recording, or social media restriction preferences;
identity disclosure restriction preferences;
private requirement notes;
trusted contact configured status where enabled;
private phrase configured status where enabled;
other invitation-related readiness or privacy conditions.

SX Consent treats this information as sensitive. It is intended for private, invitation-specific compatibility, privacy, and agreement workflows, not public discovery, public posting, or public profiles.

4.8 Optional Personal Health-Related Information

SX Consent is not a healthcare provider, telemedicine provider, medical practice, laboratory, insurer, pharmacy, testing service, or medical advice platform. SX Consent does not provide medical advice, diagnosis, treatment, testing, clinical interpretation, or medical clearance.

Depending on available features and user choices, SX Consent may process optional personal health-related information or health document status information, such as:

health-readiness setting or requirement status;
optional personal health document status;
document upload status, review status, current/expired status, rejected status, or not-provided status;
vaccination-readiness selections if enabled;
user acknowledgments related to health-related disclosures;
confirmation that a health-related document was uploaded, reviewed, current, expired, rejected, or not provided.

If health-related document upload is enabled, SX Consent may require explicit consent and may apply separate visibility, storage, retention, and access controls. Health-related information may be subject to additional rules described in the Health Data Handling Policy and Sensitive Data Consent. SX Consent does not encourage users to provide more health-related information than necessary for the specific feature they choose to use.

4.9 Invitation Context Information

inviter and invitee identifiers;
invitee email, phone number, or user identifier;
invitation ID;
invitation status;
proposed location label;
proposed location address;
scheduled start date and time;
expected end date and time;
time zone;
invitation purpose type;
custom purpose text if “Other” is selected;
multi-participant requested status if enabled;
acceptance, decline, cancellation, or expiration timestamps;
optional decline reason or message;
invitation lifecycle status.

SX Consent does not provide public user search, public matching, swiping, feeds, public browsing, or public discovery.

4.10 Cross-Intake, Compatibility, and Agreement Information

Cross-Intake results;
matched requirements;
review items;
blocking items;
compatibility status;
agreement draft data;
accepted requirements;
excluded or declined items;
invitation-specific privacy expectations;
agreement text;
agreement version;
agreement status;
signature status;
signature timestamps;
signer identifiers;
signature metadata;
hashes and integrity values;
PDF-ready or protected-record-ready agreement records.

The agreement is intended to be invitation-specific and contextual. It does not create future participation, permanent participation, legal immunity, guaranteed outcomes, or absolute proof of any event. Cross-Intake results are provided for informational and contextual purposes only. They do not guarantee that any user will participate in, continue, or complete an invitation.

For the purpose of protecting confidentiality and privacy, by accepting an invitation and continuing to view the Cross-Intake information submitted by the inviting user, you acknowledge and agree that you may be entering into the applicable One-Time Private Invitation Agreement between the parties. That agreement may include obligations related to confidentiality, non-disclosure, non-disparagement, social media restrictions, device and recording restrictions, and protection of image, likeness, and voice. If you do not wish to be bound by the One-Time Private Invitation Agreement, you should not accept the invitation, view the inviting user’s Cross-Intake information, sign any related agreement, or continue the invitation workflow.

4.11 Active Invitation and Closure Information

During an invitation lifecycle, SX Consent may collect or generate:

active invitation ID;
start time;
Log Early Event Departure timestamp;
Temporarily Leave Event timestamp;
Returned to Event timestamp;
End Manually timestamp;
closure status;
closure response;
private note status;
help requested status;
notice counts;
invitation state changes;
audit records;
workflow integrity events;
Evidence Vault status.

SX Consent may preserve logs showing what actions were taken inside the app workflow. SX Consent does not guarantee that app records reflect every event or action outside the app.

4.12 Location and Invitation Zone Information

approximate location;
precise location with device permission;
location permission status;
invitation zone coordinates;
location validation result;
distance from agreed invitation zone;
inside/outside zone status;
arrival confirmation;
location integrity status;
location failure events;
IP-derived approximate location;
geocoding or address validation metadata.

SX Consent location features are intended for contextual invitation integrity, readiness, timing, and protected recordkeeping. They are not intended for permanent tracking, ongoing surveillance, public discovery, advertising, or unrelated monitoring.

4.13 Evidence Vault, Protected Record, and Export Information

agreement metadata;
signed agreement data;
document hashes;
manifest hashes;
protected record package IDs;
timestamps;
audit events;
workflow integrity events;
notice events;
closure records;
location integrity events;
export events;
verification events;
Evidence Vault status.

Evidence Vault records and protected record exports are contextual. They are not legal conclusions and are not absolute proof of any event. Users may choose to export or share certain records with legal counsel, subject to applicable law, contractual obligations, and user responsibility.

4.14 Device, Security, and Technical Information

IP address;
device identifiers;
device model;
operating system;
browser type;
app version;
user agent;
language;
time zone;
crash logs;
diagnostics;
security logs;
fraud-prevention signals;
authentication timestamps;
invitation tokens;
cookie identifiers;
audit trail metadata.

4.15 Website, Cookies, and Analytics Information

On our websites and web application, we may use cookies, pixels, web beacons, local storage, invitation storage, or similar technologies to enable core functionality, authenticate users, maintain login state, remember preferences, improve performance, detect fraud or abuse, understand website traffic, support security, and measure usage.

We do not intend to use sensitive SX Consent invitation data for targeted advertising. If we later use advertising or tracking technologies that require consent or opt-out rights, we will update this Privacy Policy and provide required disclosures and choices.

5. How We Collect Information

We may collect information:

directly from you when you create an account, complete onboarding, configure settings, create invitations, sign agreements, complete closure responses, or contact support;
automatically from your device, browser, or app usage;
from another SX Consent user when they invite you, identify you as a participant, or include you in an invitation-specific workflow;
from service providers such as identity verification providers, SMS providers, email providers, payment processors, app stores, subscription providers, crash monitoring providers, hosting providers, analytics providers, compliance providers, and security tools;
from your device permissions, such as location, notification settings, or biometric authentication status;
from legal, security, fraud-prevention, provider, app-store, or compliance processes.

6. How We Use Information

We may use information to:

provide, operate, maintain, secure, and improve SX Consent;
create and manage user accounts;
verify identity, adult eligibility, and account readiness;
verify email and mobile phone numbers;
authenticate users;
manage subscriptions, payments, refunds, chargebacks, and entitlements;
enable private requirement profiles;
enable private invitations and Cross-Intake workflows;
generate invitation-specific agreements;
record signatures and signature metadata;
enable active invitation controls;
enable post-invitation closure;
create, seal, export, and verify contextual protected record packages;
provide SMS, email, and in-app operational notices;
support readiness and privacy workflows;
prevent fraud, abuse, unauthorized access, exploitation, and misuse;
enforce Terms and Conditions and incorporated policies;
respond to support, privacy, security, legal, app-store, and provider requests;
maintain audit logs, system integrity, and protected-record integrity;
comply with legal obligations;
protect rights, privacy, safety, property, brand integrity, intellectual property, and security;
improve reliability, performance, accessibility, and usability;
develop new features with appropriate safeguards.

We do not use SX Consent to sell public user profiles, public user discovery, public social feeds, public content feeds, or paid-interaction marketplace features.

7. Sensitive Data and Explicit Consent

SX Consent may process sensitive data only as needed to provide specific features, satisfy legal or operational requirements, verify eligibility, document invitation-specific records, support user-selected workflows, protect users, enforce agreements, preserve records, or comply with applicable law.

Sensitive data may include:

government ID verification status;
adult verification status;
biometric-related verification status from a provider or device;
precise location;
optional personal health-related information;
relationship status if provided or required by a workflow;
private requirements;
privacy expectations or invitation-related requirements;
trusted contact information where enabled;
contents of sensitive communications submitted by users;
Evidence Vault records and protected record exports;
signed agreement records.

Where required by law, platform policy, or provider requirement, we will request explicit consent before collecting or using sensitive data. You may withdraw consent where applicable, but doing so may prevent use of certain SX Consent features or may affect an existing workflow. Withdrawal of consent for future processing does not necessarily require deletion of records that must be retained for legal, security, protected-record, fraud-prevention, multi-party, or compliance purposes.

8. Optional Personal Health-Related Information

SX Consent may include optional or user-directed health-readiness features if enabled by the user or required by another user’s private requirements. SX Consent does not provide medical advice, testing, diagnosis, treatment, interpretation of medical documents, clinical recommendations, medical clearance, or medical guarantees.

When you upload, submit, enter, or otherwise provide optional personal health-related information or health document status information within your Requirement Profile or a protected private-invitation workflow, you understand that such information may be made visible through the Cross-Intake workflow to an invited participant only when you choose to disclose it or when the relevant workflow requires disclosure and you proceed with that workflow.

Cross-Intake visibility may not be reciprocal. Another participant may be able to view health-readiness information that you choose to disclose even if that participant has not provided comparable information. You should not upload, submit, or include optional personal health-related information unless you are comfortable with the invitation-specific visibility described in the app and applicable policies.

Health-related information may be subject to separate controls under the Health Data Handling Policy and Sensitive Data Consent. Where applicable, SX Consent may require explicit consent before collecting, displaying, storing, or sharing health-related information. We do not intend to sell consumer health data. We do not use consumer health data for targeted advertising. We do not use health-related information to make medical decisions.

9. Biometric Information

SX Consent may support identity verification, selfie/liveness checks, or device biometric authentication through third-party providers or device operating systems.

Unless expressly stated otherwise:

SX Consent does not store raw biometric templates in its own database;
official ID images, selfie/liveness images, and biometric verification materials are intended to be processed by identity verification providers;
device biometrics such as Face ID, Touch ID, or Android biometrics are processed by the device operating system, not by SX Consent;
SX Consent may store only status, verification invitation identifiers, timestamps, provider result metadata, and account-readiness indicators.

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

10. Location Information

SX Consent may use location information when required for invitation readiness, location integrity, invitation zone validation, arrival confirmation, fraud prevention, workflow integrity, and protected record metadata.

Location use is intended to be contextual and invitation-related. SX Consent is not designed for permanent tracking, ongoing surveillance, public discovery, advertising, or unrelated monitoring.

You may control location permissions through your device settings. However, if location is required for a specific feature or invitation, disabling location may prevent you from starting or continuing that feature or may affect the completeness of related app records.

11. Communications, SMS, Email, and In-App Notices

SX Consent may send account verification messages, phone verification SMS, email verification messages, security notices, app readiness notices, invitation status notices, review and signature notices, closure reminders, privacy request notices, account deletion notices, data deletion notices, subscription or payment notices, legal notices, and support communications.

SX Consent attempts to avoid exposing sensitive invitation details in SMS messages, email subject lines, or other operational notices. Users should open the app to review sensitive details and remain responsible for securing their devices, lock screens, email accounts, and notification settings.

SMS Notices

By providing your mobile number and opting in, you authorize SX Consent to send transactional and operational SMS messages related to account verification, account security, invitation readiness, invitation status, review and signature workflows, closure reminders, privacy requests, account notices, and other app-related operational alerts. Message and data rates may apply. Message frequency may vary.

You may opt out by replying STOP where supported. You may request help by replying HELP where supported or by contacting SX Consent support. Opting out of SMS may prevent use of features that require transactional or operational notices.

SX Consent does not sell, rent, trade, lease, disclose, or share SMS opt-in consent, mobile numbers, or SMS consent records with third parties or affiliates for their own marketing or promotional purposes.

12. When We Share Information

We may share information only as described in this Privacy Policy, with your consent, as necessary to provide SX Consent, with service providers and professional advisors, with other verified participants where needed for a protected private-invitation workflow, or as required or permitted by law.

We do not publicly publish private invitation records, private requirements, signed agreements, Evidence Vault records, health-readiness information, precise location information, or Cross-Intake details as public profiles or public content feeds.

13. Sharing With Other Verified Participants

Certain information may be shared with another verified app user only when needed for private invitation, Cross-Intake, agreement, signature, active invitation, closure, protected-record, or Evidence Vault workflows. This may include:

legal name or verified identity indicators;
profile photo or profile status;
adult verification status;
gender or relationship status if part of the profile/agreement workflow;
invitation details;
selected requirements;
accepted or declined terms;
agreement clauses;
signature status;
invitation status changes;
closure status;
limited health-readiness status if explicitly enabled and required;
location readiness status if required;
protected record package metadata.

SX Consent is not designed to publicly publish this information. Users who receive another user’s private information are responsible for complying with the Terms and Conditions, confidentiality obligations, privacy obligations, and applicable law.

14. Sharing With Service Providers and Professional Advisors

We may share information with vendors, contractors, consultants, and service providers that help us operate, secure, support, or improve SX Consent, including:

hosting and infrastructure providers;
database and backend service providers;
identity and age verification providers;
SMS providers such as Twilio;
email service providers;
payment processors, app stores, and subscription providers;
RevenueCat or similar subscription infrastructure;
Stripe or similar payment/identity providers;
Google Maps, Mapbox, or address validation providers;
Sentry or similar crash/error monitoring providers;
analytics and performance providers;
security and fraud-prevention providers;
customer support providers;
legal, compliance, accounting, tax, forensic, and professional advisors.

Service providers and advisors are expected to process information only for authorized purposes and protect information according to applicable obligations. We may also share limited information with contractors, employees, directors, officers, owners, managers, members, agents, affiliates, and authorized representatives where reasonably necessary for operations, legal compliance, security, support, or enforcement.

15. Legal, Safety, Security, and Compliance Disclosures

We may disclose information if we believe disclosure is necessary or appropriate to:

comply with law, legal process, subpoenas, court orders, or governmental requests;
enforce our Terms and Conditions or incorporated policies;
respond to claims, disputes, chargebacks, payment disputes, provider inquiries, or app-store requests;
prevent fraud, abuse, unauthorized access, exploitation, or security incidents;
protect the rights, safety, privacy, property, intellectual property, brand integrity, or security of SX Consent, Beniquez Sanchez and Company LLC, BS and Co AI Labs, users, providers, or others;
investigate policy violations;
preserve protected records, Evidence Vault records, or audit records;
comply with app store, payment processor, identity verification, messaging provider, hosting provider, or legal requirements.

16. Business Transfers

If SX Consent, Beniquez Sanchez and Company LLC, BS and Co AI Labs, or related assets are involved in a merger, acquisition, financing, restructuring, bankruptcy, sale of assets, transfer of operations, corporate transaction, assignment, or similar transaction, information may be transferred as part of that transaction, subject to appropriate confidentiality and privacy protections where required.

17. No Sale of Personal Information and No Sensitive Advertising Use

SX Consent does not sell personal information for money.

SX Consent does not sell or share SMS opt-in data, mobile numbers, or SMS consent records for third-party marketing or promotional purposes.

SX Consent does not intend to use sensitive invitation records, optional health-related information, Evidence Vault records, signed agreement data, Cross-Intake data, private requirements, or location integrity events for targeted advertising.

If our practices change in a way that is considered a “sale,” “sharing,” targeted advertising, or profiling under applicable law, we will update this Privacy Policy and provide required opt-out mechanisms.

18. Data Retention

We retain information for as long as reasonably necessary to provide SX Consent, maintain security, comply with legal obligations, resolve disputes, enforce agreements, preserve protected-record integrity, support user rights, prevent fraud, defend against claims, and protect the Company, users, providers, and related parties.

Retention periods depend on the type of information, purpose of collection, legal requirements, user account status, protected-record status, subscription status, provider requirements, and whether information involves multiple participants.

Examples include:

Account information may be retained while your account is active and for a reasonable period after account deletion.
Verification status and provider metadata may be retained as needed for compliance, security, fraud prevention, and account integrity.
SMS opt-in, opt-out, and delivery logs may be retained as needed for messaging compliance.
Agreement, signature, Evidence Vault, audit, and closure records may be retained longer where necessary to preserve contextual protected records, support legal claims, protect participants, comply with law, or maintain integrity of multi-party records.
Location integrity records may be retained as part of the invitation record or protected record package when location was required for that invitation.
Security logs may be retained as needed for fraud prevention, investigation, system integrity, and legal compliance.
Optional health-related information may be retained according to the Health Data Handling Policy, user choices, and applicable law.

When information is no longer needed, we may delete, de-identify, aggregate, archive, restrict, or securely retain it where permitted or required by law.

19. Account Deletion and Data Deletion

You may request account deletion through the Account Deletion process. You may request deletion of eligible personal data through the Data Deletion process.

Deletion requests may be subject to verification. Some information may not be deleted immediately or may be retained where necessary to:

comply with law;
protect against fraud, abuse, security threats, or chargebacks;
resolve disputes;
enforce agreements;
preserve Evidence Vault or protected record packages;
maintain signed agreement integrity;
maintain multi-party invitation records;
protect the rights, privacy, safety, property, intellectual property, or security of users or SX Consent;
comply with tax, accounting, regulatory, provider, or app-store obligations;
comply with legal holds, court orders, lawful requests, or law enforcement requests.

Deleting your account may limit or terminate your ability to access SX Consent. Deleting one participant’s account may not automatically delete records involving another participant, signed agreements, Evidence Vault records, protected record packages, legal records, audit logs, or records required for legitimate legal, security, fraud-prevention, provider, or compliance purposes.

20. Security Safeguards

We use reasonable administrative, technical, organizational, and contractual safeguards designed to protect information against unauthorized access, loss, misuse, alteration, disclosure, or destruction.

These safeguards may include:

encryption in transit;
access controls;
authentication requirements;
audit logs;
security monitoring;
least-privilege access;
provider controls;
separation of sensitive storage;
incident response procedures;
logging and integrity checks;
internal policy controls;
contractor and service-provider confidentiality obligations.

No system can be guaranteed completely secure. You are responsible for protecting your account credentials, device access, email account, mobile phone, and lock-screen settings. If you believe your account or information has been compromised, contact SX Consent through the appropriate security or support channel.

21. User Choices and Controls

Depending on feature availability and applicable law, you may be able to:

access your account information;
update or correct account details;
manage notice settings;
manage SMS opt-in/opt-out;
manage device permissions;
withdraw consent for certain processing where applicable;
request account deletion;
request data deletion;
request access to personal information;
request correction;
request portability;
restrict or object to certain processing;
limit use of sensitive personal information where applicable;
opt out of sale, sharing, targeted advertising, or profiling where applicable.

Some choices may limit the availability of SX Consent features. For example, if you disable required SMS, email, in-app notices, location readiness, identity readiness, or required account-readiness features, you may be unable to start or continue certain invitation workflows.

22. U.S. State Privacy Rights

Depending on your state of residence, you may have privacy rights under applicable state laws, which may include the right to:

confirm whether we process your personal information;
access personal information;
correct inaccurate personal information;
delete personal information;
obtain a portable copy of personal information;
opt out of sale of personal information;
opt out of sharing or targeted advertising;
opt out of certain profiling;
limit use and disclosure of sensitive personal information;
appeal a privacy request decision;
not be discriminated against for exercising privacy rights.

To exercise rights, contact SX Consent through the applicable privacy request channel or use the appropriate request page. We may need to verify your identity before responding. If your request involves sensitive information, Evidence Vault records, protected record packages, multi-party records, or security-sensitive data, additional verification may be required.

23. California Privacy Notice

This section applies to California residents where the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies.

Categories of Personal Information We May Collect

We may collect identifiers, personal records, protected classification information where provided or required, commercial information, internet or electronic activity information, geolocation information, sensory information if future features involve profile photos, identity verification, support submissions, or permitted media, professional or employment-related information only if voluntarily provided in support, legal, or business contexts, and sensitive personal information where required for SX Consent workflows.

Sensitive personal information may include government ID verification status, precise geolocation, optional health-related information, relationship or private requirement information, account login credentials, contents of certain user communications, biometric-related verification metadata, and information concerning privacy expectations if provided as part of private invitation requirements.

Sources, Purposes, and Disclosures

We collect information from you, your device, other verified participants, service providers, app stores, payment providers, identity verification providers, communication providers, security systems, and support/compliance processes. We use information for the purposes described in this Privacy Policy, including providing SX Consent, verifying users, managing accounts, enabling invitation workflows, generating agreements, preserving protected records, sending notices, maintaining security, complying with law, and enforcing terms.

We may disclose categories of information to service providers, other verified participants as required for the invitation workflow, legal authorities, professional advisors, payment processors, identity providers, communication providers, and other parties described in this Privacy Policy.

Sale or Sharing

We do not sell personal information for money. We do not sell or share SMS opt-in data for marketing. We do not intend to use sensitive SX Consent records for cross-context behavioral advertising.

California Rights

California residents may have rights to know, access, delete, correct, opt out of sale or sharing, limit sensitive personal information, and non-discrimination. Requests may be submitted through the appropriate SX Consent request page or privacy contact channel.

24. EEA, UK, and International Privacy Rights

Where the GDPR, UK GDPR, or similar laws apply, Beniquez Sanchez and Company LLC may act as the controller of personal information processed through SX Consent.

Legal bases may include performance of a contract, user consent, explicit consent where required, compliance with legal obligations, legitimate interests, protection of rights, safety, security, fraud prevention, and establishment, exercise, or defense of legal claims.

Depending on your jurisdiction, you may have rights to access personal data, rectify inaccurate data, erase data, restrict processing, object to processing, receive data portability, withdraw consent where applicable, lodge a complaint with a supervisory authority, and object to certain automated decision-making.

International users understand that SX Consent is operated from the United States and information may be processed in the United States or other jurisdictions where service providers operate. Where required, we may use appropriate safeguards for international transfers.

25. Automated Processing and App Readiness Decisions

SX Consent may use automated systems to support account readiness, identity verification status, phone verification, security checks, fraud prevention, location integrity, notice readiness, invitation lifecycle status, protected-record integrity, policy enforcement, and provider workflows.

SX Consent does not use automated systems to make final legal conclusions about liability, truthfulness, wrongdoing, real-world conduct, or legal responsibility. App-generated records are contextual records, not legal determinations.

Some automated or provider-assisted decisions may affect whether an account, feature, invitation, or workflow can proceed. Where required by law, users may have rights to request review, appeal, or additional information about certain automated processing.

26. Artificial Intelligence and Data Use

SX Consent may use automation or AI-assisted tools in limited ways for security, fraud prevention, support classification, diagnostics, moderation, policy enforcement, product reliability, or internal operations.

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

SX Consent and Beniquez Sanchez and Company LLC reserve all rights in SX Consent agreement templates, workflows, legal architecture, proprietary wording, protected record architecture, privacy workflows, confidentiality workflows, and related materials. Users, providers, reviewers, vendors, contractors, competitors, AI systems, and third parties may not scrape, extract, reproduce, train on, model, reverse engineer, or create derivative products from proprietary SX Consent materials except as expressly permitted by the Terms and Conditions or written authorization.

If SX Consent introduces AI features that process user content or sensitive information in a materially different way, we will update this Privacy Policy and provide additional notices or consent where required.

27. Cookies, Analytics, and Tracking Choices

We may use cookies and similar technologies for essential functionality, authentication, security, fraud prevention, preferences, performance, and analytics.

You may control cookies through your browser or device settings. Some features may not work properly without essential cookies.

Where required by law, we will provide cookie consent or opt-out mechanisms. We may recognize Global Privacy Control or similar legally required opt-out signals where required by applicable law.

28. Third-Party Links and Providers

SX Consent may link to third-party sites or use third-party services. These third parties may have their own privacy policies, terms, data practices, and security practices.

Examples may include Apple, Google, Stripe, Twilio, RevenueCat, Firebase, Sentry, Google Maps, Mapbox, Postmark, SendGrid, hosting and infrastructure providers, identity verification providers, payment processors, subscription infrastructure providers, legal providers, security providers, and compliance providers.

We are not responsible for the privacy practices, security practices, policies, outages, decisions, denials, delays, billing, refunds, verification outcomes, app-store actions, or data practices of third-party services that we do not control.

29. Law Enforcement and Legal Requests

We may access, preserve, or disclose information if required or permitted by law, including in response to lawful requests, subpoenas, court orders, legal claims, arbitration requests, app-store inquiries, provider requests, or government inquiries.

We may also preserve information where necessary to protect users, prevent harm, investigate misuse, enforce terms, maintain protected-record integrity, preserve Evidence Vault records, defend against claims, cooperate with lawful investigations, or protect SX Consent’s rights, property, users, personnel, contractors, owners, and service providers.

30. Data Breach and Security Incidents

If we discover a security incident involving personal information, we will investigate and take appropriate steps. Where required by law, we will notify affected users, regulators, providers, or other parties.

Not every security event is a legally reportable breach. We evaluate incidents based on applicable law, risk, affected data, affected systems, available facts, provider obligations, and legal requirements.

31. Children and Minors

SX Consent is strictly limited to adults 18 years of age or older.

We do not knowingly collect information from minors. We may use identity, adult verification, or age eligibility providers to support this requirement.

If we discover that a minor has provided information, we may delete, restrict, suspend, preserve limited information, report, or take other appropriate action as necessary for legal, security, fraud-prevention, abuse-prevention, or safety purposes.

32. App Store, Google Play, and Subscription-Related Privacy Disclosures

If you access SX Consent through Apple App Store, Google Play, or another app marketplace, the applicable platform may collect, process, or retain information related to downloads, purchases, subscriptions, refunds, device information, diagnostics, crash reports, app-store receipts, entitlement status, and account management under that platform’s own terms and privacy policy.

SX Consent may receive limited app-store, subscription, receipt, entitlement, or transaction metadata from Apple, Google, RevenueCat, Stripe, or other providers to operate subscriptions, verify access, manage entitlements, process cancellations, respond to disputes, prevent fraud, and comply with app-store requirements.

We do not control Apple, Google, or other app-store privacy practices. You should review the privacy policies and account settings of the platform through which you download or purchase SX Consent access.

33. Identity Verification Provider Data

Identity verification providers may collect, process, store, or verify government ID information, selfie/liveness information, fraud-prevention indicators, device information, verification status, and related metadata under their own privacy terms and contractual obligations.

SX Consent may receive verification status, verification metadata, identity-readiness information, and limited provider identifiers needed to determine account readiness and prevent fraud. Unless expressly stated otherwise, SX Consent does not intend to store full government ID images, selfie/liveness images, raw biometric templates, or official identity document scans directly in its own database.

Verification providers may retain information according to their own retention practices and applicable law. SX Consent is not responsible for provider-side retention or processing beyond what applicable contracts or laws require.

34. Sensitive Invitation Records and Multi-Party Records

Some SX Consent records involve more than one participant. These may include invitations, Cross-Intake records, agreement records, signature records, closure records, Evidence Vault records, protected record packages, audit logs, notice logs, location-readiness events, and other multi-party workflow records.

Because these records may belong to or affect more than one participant, one user’s account deletion or data deletion request may not automatically delete or alter records associated with another participant, signed agreement, protected record package, legal claim, dispute, security event, audit requirement, or compliance obligation.

SX Consent may retain multi-party records where reasonably necessary to preserve record integrity, protect participants, enforce agreements, comply with law, prevent fraud, resolve disputes, investigate misuse, or defend the Company and related parties.

35. Evidence Vault, Protected Record Exports, and Integrity Metadata

SX Consent may create, preserve, seal, hash, audit, export, or verify Evidence Vault records, protected record packages, agreement metadata, signature metadata, timestamps, notices, closure responses, location-readiness events, and related integrity metadata.

These records are contextual app records. They are not legal conclusions, medical conclusions, emergency reports, law-enforcement reports, guaranteed proof, or guarantees of any legal outcome. They may be incomplete if users act outside the app, devices fail, providers fail, permissions are disabled, network connectivity is unavailable, or users submit inaccurate information.

Users remain responsible for deciding whether to share protected records with legal counsel, law enforcement, courts, arbitrators, insurers, employers, professional advisors, or third parties. Users must comply with applicable law, confidentiality obligations, privacy obligations, and the Terms and Conditions when sharing any record.

36. Contractor, Employee, and Internal Access Controls

Authorized employees, contractors, officers, directors, managers, members, owners, agents, affiliates, service providers, and professional advisors of Beniquez Sanchez and Company LLC, SX Consent, and BS and Co AI Labs may access information only as reasonably necessary for authorized operational, security, legal, compliance, support, engineering, billing, fraud-prevention, record-integrity, or business purposes.

We use reasonable internal controls designed to limit access based on role, need, confidentiality obligation, and operational purpose. No internal access-control program can guarantee that unauthorized access will never occur, but unauthorized access, misuse, disclosure, copying, or exploitation of SX Consent information, proprietary materials, user records, or protected records is prohibited and may result in account, employment, contractor, legal, or other remedies.

37. Confidentiality, Ownership, and Brand Protection

SX Consent™, BS and Co AI Labs™, SX Consent Application, proprietary agreement templates, privacy workflows, confidentiality workflows, legal-tech architecture, protected record workflows, interface designs, documentation, protected-record structures, agreement metadata structures, and related materials are owned by, licensed to, or controlled by Beniquez Sanchez and Company LLC d/b/a BS and Co AI Labs and/or its licensors.

Nothing in this Privacy Policy grants any person a license to copy, scrape, reproduce, extract, reverse engineer, publish, commercialize, train artificial intelligence systems on, or create derivative works from SX Consent proprietary materials, agreement templates, platform architecture, protected-record workflows, or confidential business information. Additional restrictions and remedies are set forth in the Terms and Conditions.

We may process information as reasonably necessary to protect SX Consent, Beniquez Sanchez and Company LLC, BS and Co AI Labs, their owners, officers, directors, contractors, employees, trademarks, service marks, copyrights, trade secrets, goodwill, reputation, providers, and business relationships.

38. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in law, technology, provider requirements, app store requirements, platform features, security practices, privacy practices, subscription operations, protected-record workflows, or business operations.

The “Last Updated” date indicates when this Privacy Policy was last revised. Material changes may be communicated through the website, app, email, in-app notice, account notice, or other appropriate method.

Continued use of SX Consent after an updated Privacy Policy becomes effective means you acknowledge the updated policy, where permitted by law. If legally required, we may request additional consent for materially different processing.

39. Contact Us

For privacy questions, legal questions, security questions, support requests, account deletion requests, data deletion requests, SMS help, or other inquiries, contact SX Consent through the applicable contact channel.

Support: Click Here

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