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

This Health Data Handling Policy (“Policy”) 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 safety-tech, privacy-tech, legal-tech and evidence-tech platform for verified adults. SX Consent helps verified adults document session-specific consent context, boundaries, privacy expectations, safety steps, session status changes, closure responses and contextual evidence records.

SX Consent is not a healthcare provider, telemedicine provider, medical practice, clinic, laboratory, pharmacy, health insurer, medical device, diagnostic tool, treatment platform, public health authority, emergency medical service or substitute for professional medical advice.

This Policy explains how SX Consent may collect, process, display, store, restrict, share, retain, delete or otherwise handle health-related information if health-related features are enabled or used.

This Policy supplements and is incorporated into our:

• Privacy Policy;
• Terms and Conditions;
• Sensitive Data Consent;
• SMS Terms;
• Account Deletion Policy;
• Data Deletion Policy;
• in-app health-related disclosures;
• identity and eligibility disclosures;
• agreement acknowledgments;
• session-specific disclosures;
• evidence vault notices;
• any provider-specific notices.

If you do not agree to this Policy, you must not use SX Consent features that request, display, process or rely on health-related information.

1. Important Health Disclaimer

SX Consent does not provide medical advice.

SX Consent does not diagnose, treat, cure, prevent, test for, monitor or manage any disease, infection, condition, exposure, pregnancy, fertility issue, mental health condition, physical condition, sexually transmitted infection, sexually transmitted disease or medical risk.

SX Consent does not interpret laboratory results.

SX Consent does not verify the clinical validity, authenticity, completeness, accuracy, freshness or medical meaning of any test result, health declaration, vaccination record, STD/STI document, user statement, provider document, uploaded file or metadata unless we expressly state otherwise in writing.

Any health-related feature in SX Consent is intended only to support private documentation, user disclosure, compatibility review, session readiness, agreement context, privacy expectations and evidence metadata between verified adult app users.

You should consult a qualified healthcare professional for medical testing, medical advice, diagnosis, treatment, prevention, counseling, risk assessment, vaccination guidance, STD/STI interpretation, reproductive health guidance, medication guidance or any health-related decision.

If you believe you may have a medical emergency, call 911 or your local emergency number immediately.

2. Adults-Only Health Data Processing

SX Consent is strictly limited to adults who are at least 18 years old.

Health-related features are intended only for verified adults. Minors must not use SX Consent and must not submit health-related information.

By using any health-related feature, you represent and warrant that:

• you are at least 18 years old;
• you are legally permitted to provide the information;
• the information you provide is your own information or information you are legally authorized to submit;
• you are not submitting false, altered, forged, misleading, stolen, fabricated or unauthorized health-related information;
• you are not using health-related features to coerce, pressure, shame, threaten, extort, blackmail, discriminate against, harass or mislead another person.

We may suspend, restrict or terminate accounts and preserve relevant records if we believe health-related features are being misused.

3. Scope of This Policy

This Policy applies when SX Consent processes health-related information through:

• account onboarding;
• private requirement profiles;
• health declaration settings;
• STD/STI document status workflows;
• last tested date fields;
• vaccination-related selections;
• health practices selections;
• barrier protection requirement fields;
• private boundary matrix and session requirement workflows;
• cross-intake compatibility;
• one-time session agreement generation;
• evidence package metadata;
• active session readiness;
• closure workflows;
• support requests;
• data deletion requests;
• account deletion requests;
• privacy, legal or security requests.

This Policy applies to SX Consent websites, PWA, mobile apps, APIs, backend systems, storage systems, provider integrations and evidence-related workflows.

4. Health-Related Information SX Consent May Handle

Depending on available features and your choices, SX Consent may collect or process the following health-related information.

4.1 Health Declaration Requirement

SX Consent may allow a user to indicate whether a health declaration is:

• required;
• optional;
• not required.

If a user requires a health declaration from another user, SX Consent may require the requesting user to provide an equivalent health readiness item first, where applicable, to support fairness and reduce misuse.

4.2 Last Tested Date

SX Consent may collect or display a “last tested date” for health-related readiness workflows.

The last tested date is user-provided or document-associated information. SX Consent does not guarantee that the date is truthful, complete, medically sufficient or clinically meaningful.

4.3 STD/STI Document Status

SX Consent may collect or process information related to STD/STI document status, such as:

• not provided;
• pending upload;
• uploaded;
• pending review;
• current;
• expired;
• rejected;
• unavailable;
• self-declared only;
• provider-verified, if a qualified provider integration exists in the future.

Unless expressly stated otherwise, SX Consent does not clinically verify test results or guarantee authenticity.

4.4 STD/STI Document Metadata

SX Consent may process metadata related to a document, such as:

• upload timestamp;
• document status;
• expiration or recency status;
• user acknowledgment;
• file name or file reference;
• document hash;
• evidence package metadata;
• review status;
• visibility status;
• deletion or retention status.

SX Consent may avoid displaying raw medical documents in public or unnecessary areas of the app. Where possible, SX Consent may display only limited status indicators, such as “Provided,” “Not provided,” “Current,” “Expired,” “Pending,” or “Configured.”

4.5 Vaccination-Related Selections

If enabled, users may select vaccination-related information, such as:

• COVID-19 vaccination status;
• mpox vaccination status;
• meningitis vaccination status;
• other user-selected vaccination readiness information.

SX Consent does not verify vaccination status unless a qualified verification workflow is expressly offered.

4.6 Health Practices Selections

SX Consent may allow users to select health practices or prevention-related disclosures, including but not limited to:

• barrier protection preferences;
• condom-related selections;
• PrEP-related disclosures;
• doxyPEP-related disclosures;
• HIV undetectable disclosure;
• “prefer to discuss” selection;
• other user-provided health practice indicators.

These selections are user-provided disclosures. SX Consent does not verify the medical accuracy, sufficiency, consistency, truthfulness or current status of these disclosures.

4.7 Health-Related Acknowledgments

SX Consent may collect acknowledgments that a user:

• understands that SX Consent is not a medical provider;
• understands that health information is user-provided unless expressly verified;
• understands that health-related features do not replace medical testing or advice;
• agrees not to rely on SX Consent as medical advice;
• agrees to consult qualified healthcare professionals;
• accepts health-related limitations.

4.8 Health-Related Evidence Metadata

Health-related settings, statuses or acknowledgments may be included in a session-specific agreement or evidence package when relevant to the session workflow.

SX Consent may preserve this information as contextual evidence metadata, subject to privacy, retention and evidence integrity rules.

5. What SX Consent Does Not Collect or Do by Default

Unless a specific feature is enabled and the user provides express consent, SX Consent does not intend to:

• collect full medical records;
• collect full clinical histories;
• collect complete laboratory files;
• collect insurance records;
• collect prescription records;
• collect provider chart records;
• collect diagnostic information from healthcare providers;
• collect genetic information;
• collect reproductive health records;
• collect mental health treatment records;
• access Apple HealthKit or Google Health Connect;
• write data to Apple HealthKit or Google Health Connect;
• diagnose any condition;
• interpret STD/STI results;
• provide medical recommendations;
• provide testing services;
• prescribe medication;
• connect users with doctors;
• operate as telemedicine;
• function as a medical device.

If SX Consent later adds any such feature, we will update this Policy and request additional consent where required.

6. Purposes for Handling Health-Related Information

SX Consent may process health-related information only for limited purposes, including:

• private requirement setup;
• private compatibility review;
• cross-intake workflows;
• user-selected health disclosure;
• fairness enforcement when a user requires a health-related item from another user;
• agreement drafting;
• session-specific privacy and consent documentation;
• active session readiness;
• evidence package metadata;
• dispute documentation;
• legal compliance;
• safety-related review;
• fraud prevention;
• preventing misuse;
• account enforcement;
• responding to user requests;
• processing account deletion or data deletion requests;
• complying with provider, Apple App Store or Google Play requirements.

SX Consent does not use health-related information for public profiles, public discovery, public matching, targeted advertising, social media feeds, adult content monetization or sale of health data.

7. Explicit Consent for Health-Related Features

Certain health-related features require explicit consent.

By enabling, requiring, submitting, uploading, displaying, sharing, accepting, viewing or relying on a health-related SX Consent feature, you expressly consent to SX Consent processing health-related information as described in this Policy, the Privacy Policy, the Sensitive Data Consent and the Terms and Conditions.

You may withdraw consent where applicable. However, withdrawing consent may:

• disable health-related features;
• prevent you from requiring health information from others;
• prevent you from accepting invitations where health readiness is required;
• prevent generation of certain agreements;
• block active session readiness;
• limit evidence package completeness;
• restrict your account;
• preserve prior records where retention is required or permitted.

Withdrawal of health data consent does not automatically delete records already generated, signed, sealed, shared with another participant, retained for legal reasons or preserved for evidence integrity.

Withdrawal of consent does not create a refund right.

8. Health Data Is Not Medical Advice

You agree that health-related information in SX Consent:

• is not medical advice;
• is not a diagnosis;
• is not treatment;
• is not prevention guidance;
• is not a substitute for testing;
• is not a substitute for professional care;
• is not a clinical recommendation;
• is not a guarantee that a person is free from infection;
• is not a guarantee that a person’s statements are true;
• is not a guarantee that a document is authentic;
• is not a guarantee of safety.

You should consult licensed medical professionals for all health decisions.

9. No Verification Guarantee

SX Consent may display health-related information submitted by users or generated by the app workflow, but SX Consent does not guarantee:

• authenticity of documents;
• accuracy of test results;
• freshness of test results;
• truthfulness of user statements;
• completeness of disclosures;
• validity of vaccination claims;
• effectiveness of prevention practices;
• absence of STD/STI risk;
• absence of disease transmission;
• absence of pregnancy risk;
• absence of reproductive health risk;
• absence of any medical condition;
• legal sufficiency of health disclosures.

If SX Consent later integrates a qualified third-party verification provider, the provider’s verification may reduce risk but will not eliminate risk or create a medical guarantee.

10. User Responsibility for Health Decisions

You are solely responsible for:

• deciding whether to disclose health-related information;
• deciding whether to request health-related information;
• deciding whether to accept another user’s health disclosure;
• deciding whether to participate in a session;
• obtaining your own medical testing;
• consulting medical professionals;
• understanding health risks;
• practicing prevention;
• complying with applicable laws;
• respecting another user’s boundaries;
• respecting another user’s withdrawal of consent.

SX Consent does not assume responsibility for your health decisions, another user’s health decisions, or consequences arising from user interactions.

11. Fairness Rule for Required Health Declarations

If a user marks a health declaration or STD/STI readiness item as “required,” SX Consent may require that user to provide their own equivalent readiness item before imposing that requirement on another user.

For example, if User A requires User B to provide a recent STD/STI readiness item, User A may be required to provide User A’s own recent readiness item first.

This rule is intended to reduce asymmetry, misuse, coercion and unfair data demands.

SX Consent may block, restrict or flag health-related requirements if the requesting user does not satisfy reciprocal readiness requirements.

12. Visibility of Health-Related Information

Health-related information may be visible to another verified participant only when necessary for a private workflow, such as:

• invitation review;
• cross-intake;
• health requirement matching;
• agreement generation;
• session readiness;
• evidence package metadata.

SX Consent may limit visibility to status indicators rather than raw documents.

For example, another participant may see:

• “Health declaration required”;
• “Document provided”;
• “Current”;
• “Expired”;
• “Not provided”;
• “Pending review”;
• “Last tested date provided.”

SX Consent should not publicly display raw medical documents, STD/STI reports, lab results or detailed health records.

You must not screenshot, copy, publish, threaten to publish, disclose, share, sell, misuse, shame, blackmail, extort or weaponize another user’s health-related information.

13. No Public Health Profiles

SX Consent does not create public health profiles.

SX Consent does not allow public browsing of health status.

SX Consent does not allow health data to be used for public matching.

SX Consent does not allow users to search publicly by health status.

SX Consent does not allow health-related information to be marketed as adult content, dating content or public profile content.

Health-related information is intended only for private, session-specific, verified-user workflows.

14. Health Data and One-Time Session Agreements

Health-related information may be included in a one-time session agreement only when relevant to the session-specific workflow and accepted by the participants.

The agreement may include:

• whether health declaration was required;
• whether a status was provided;
• last tested date if supplied;
• health-related acknowledgments;
• accepted or declined health-related requirements;
• limitation disclaimers;
• health-related evidence metadata.

A one-time session agreement does not verify health truth, eliminate health risk, create medical advice or guarantee legal enforceability.

15. Health Data and Evidence Packages

SX Consent may include health-related metadata in an evidence package if health-related items were part of the session workflow.

Evidence packages may include:

• status values;
• timestamps;
• acknowledgments;
• document hashes;
• visibility status;
• agreement references;
• audit events;
• cross-intake items;
• closure records.

Evidence packages are contextual records. They are not medical records, legal conclusions, proof of infection status, proof of non-infection status, or absolute proof of any event.

16. Health Data Retention

SX Consent may retain health-related information for as long as reasonably necessary for:

• providing health-related features;
• account readiness;
• agreement integrity;
• evidence integrity;
• legal compliance;
• fraud prevention;
• abuse prevention;
• dispute resolution;
• chargeback defense;
• user safety;
• audit records;
• provider compliance;
• app store compliance;
• enforcing Terms and Conditions.

Retention periods may vary based on:

• whether data is part of a signed agreement;
• whether data is part of a sealed evidence package;
• whether data involves multiple users;
• whether there is a dispute;
• whether there is a legal hold;
• whether there is fraud or abuse;
• whether deletion is technically or legally possible;
• applicable law;
• provider requirements.

Health-related raw documents, if enabled, should be retained only as long as reasonably necessary and should be subject to restricted access and enhanced controls.

17. Data Deletion and Health Data

You may request deletion of eligible health-related information through the Data Deletion process.

SX Consent may deny, delay, limit or partially fulfill deletion where retention is necessary to:

• preserve signed agreements;
• preserve evidence package integrity;
• protect another participant’s rights;
• comply with law;
• respond to legal process;
• resolve disputes;
• prevent fraud;
• investigate abuse;
• maintain audit logs;
• comply with provider requirements;
• defend legal claims;
• maintain multi-party records;
• enforce Terms and Conditions.

Where deletion is not possible or not appropriate, SX Consent may restrict, archive, de-identify, hash, segregate or limit access to the data where feasible.

18. Account Deletion and Health Data

Account deletion does not automatically delete all health-related information.

If health-related information is included in a signed agreement, evidence package, audit log, safety record, dispute record, provider record or multi-party session record, SX Consent may retain it where reasonably necessary.

Deleting your account does not create a refund right.

Deleting your account may prevent future access to certain records, but it may not erase records lawfully retained for evidence, legal, security, compliance or multi-party purposes.

19. Health Data Security

SX Consent uses reasonable administrative, technical and organizational safeguards designed to protect health-related information.

Safeguards may include:

• encryption in transit;
• restricted access;
• access logging;
• role-based controls;
• limited visibility;
• separate handling for raw documents where feasible;
• document hash or metadata handling;
• provider controls;
• audit logs;
• security monitoring;
• least-privilege access;
• incident response procedures;
• retention controls;
• deletion or restriction workflows.

No system can be guaranteed completely secure.

You are responsible for securing your device, email, phone number, password, PIN, biometric access, lock screen and notification settings.

20. Health Data Breach and Incident Handling

If SX Consent discovers a security incident involving health-related information, we will investigate and take appropriate steps.

Where required by applicable law, we may notify affected users, regulators, providers, app stores, payment processors or other required parties.

Not every incident is a legally reportable breach. SX Consent will evaluate incidents based on applicable law, affected data, risk, scope, security measures and available facts.

21. Consumer Health Data Laws

Some U.S. states have laws that regulate consumer health data beyond HIPAA.

Depending on your location and the data involved, you may have rights related to access, deletion, withdrawal of consent, restriction, correction, portability or additional disclosures.

SX Consent may provide separate notices or rights where required by applicable consumer health data laws.

Where state consumer health data laws apply, SX Consent may require express consent before collecting or sharing certain health-related information and may provide separate processes for consumer health data rights.

22. HIPAA Status

SX Consent is not intended to be a healthcare provider, health plan, healthcare clearinghouse or business associate solely by offering SX Consent’s private documentation features.

Unless SX Consent expressly enters into a written business associate agreement or otherwise becomes subject to HIPAA through a specific relationship, SX Consent does not represent that it is a HIPAA covered entity or business associate.

Even where HIPAA does not apply, SX Consent may still handle health-related information under this Policy, the Privacy Policy, the Sensitive Data Consent, applicable consumer privacy laws, app store rules, provider rules and contractual safeguards.

23. HealthKit, Health Connect and Health Platform Data

SX Consent does not currently intend to access Apple HealthKit, Apple Health, Google Health Connect or similar health data platforms unless clearly disclosed.

If SX Consent later requests access to such health data, SX Consent will:

• provide additional notice;
• request user permission;
• explain why access is needed;
• limit access to necessary data;
• honor platform restrictions;
• update App Store and Google Play disclosures;
• update this Policy where required.

SX Consent will not use HealthKit, Health Connect or similar health platform data for advertising, public discovery, public matching or adult content monetization.

24. Sharing Health-Related Information With Other Users

Health-related information may be shared with another verified participant only when necessary for a private, user-initiated SX Consent workflow.

Examples include:

• when you require a health declaration;
• when another user requires a health declaration;
• when health-related readiness affects cross-intake;
• when health-related status is included in the one-time session agreement;
• when health-related status is part of evidence metadata.

You are responsible for deciding whether to share health-related information.

Do not share health-related information unless you understand the risks and consent to the specific disclosure.

25. Sharing Health-Related Information With Providers

SX Consent may share limited health-related information with service providers only as necessary to operate the platform, protect security, process records, store data, provide support, comply with law, or maintain evidence integrity.

Providers may include:

• hosting providers;
• storage providers;
• security providers;
• legal and compliance advisors;
• app infrastructure providers;
• crash/error monitoring providers;
• document handling providers;
• identity verification providers;
• support tools;
• SMS/email/push providers, but only limited operational metadata unless necessary;
• payment or subscription providers, if needed for account management.

SX Consent does not sell health-related information.

26. No Health Data for Targeted Advertising

SX Consent does not intend to use health-related information for:

• targeted advertising;
• behavioral advertising;
• public matching;
• public discovery;
• marketing of adult content;
• sale to data brokers;
• third-party promotional use;
• cross-app tracking.

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

27. User Prohibited Conduct Involving Health Data

You must not:

• upload false health documents;
• alter test results;
• impersonate a medical provider;
• misrepresent vaccination status;
• misrepresent STD/STI status;
• submit another person’s health data without authorization;
• coerce another user into disclosing health data;
• threaten to reveal health information;
• shame or harass someone based on health information;
• publish another user’s health information;
• use health data for blackmail or extortion;
• use health data to discriminate unlawfully;
• bypass reciprocal health readiness requirements;
• manipulate health status fields;
• misuse screenshots;
• upload malware or hidden content in documents;
• use SX Consent as a substitute for medical testing or advice.

Violations may result in suspension, termination, evidence preservation, legal reporting, provider reporting or other enforcement action.

28. Health Data in Support Communications

Do not send unnecessary health-related information through email, SMS, chat or support forms.

If you contact support about a health-related issue, include only the minimum necessary information.

SX Consent may preserve support communications for legal, security, fraud-prevention, compliance and evidence purposes.

SMS and email may not be secure channels for sensitive health information. Sensitive details should generally be reviewed inside the app.

29. Notices and Health Privacy

SX Consent attempts to avoid exposing health-related details in SMS, push notification previews or email subject lines.

Operational messages may say something like:

• “Open the app to review an account action.”
• “Open the app to review session readiness.”
• “Open the app to complete a pending response.”

They should not reveal sensitive details such as STD/STI status, diagnosis, test result, private boundary selections or intimate health disclosures.

Users are responsible for securing device notification previews and lock screen settings.

30. No Emergency or Public Health Reporting Service

SX Consent is not a public health reporting system.

SX Consent is not an emergency medical service.

SX Consent is not a disease surveillance system.

SX Consent does not automatically report health conditions to public health authorities, except where required by law, court order, subpoena or valid legal process.

If you need emergency medical assistance, call 911 or your local emergency number.

31. User Acknowledgment of Risk

By using health-related features, you understand and agree that:

• health information may be sensitive;
• another user may provide inaccurate information;
• documents may be outdated, forged, incomplete or misunderstood;
• test results may not cover all risks;
• timing of tests may matter;
• there may be window periods or limitations;
• vaccination status may not eliminate risk;
• prevention practices may not eliminate risk;
• SX Consent cannot guarantee health safety;
• SX Consent cannot guarantee another user’s honesty;
• SX Consent cannot guarantee legal outcomes;
• you remain responsible for your own medical decisions.

32. No Reliance on SX Consent for Health Safety

You agree not to rely solely on SX Consent to determine whether a session is medically safe.

SX Consent health-related features are private documentation tools. They are not medical safety clearance.

Any decision to participate in a session is made by you at your own risk.

33. Relationship Between Health Data and Consent

Health-related disclosures do not replace consent.

Health-related disclosures do not create permanent consent.

Health-related disclosures do not create future consent.

Health-related disclosures do not prevent withdrawal of consent.

Health-related disclosures do not waive legal rights.

Consent remains continuous, contextual and revocable at all times.

34. Enforcement

SX Consent may suspend, restrict, disable or terminate accounts or features if we believe health-related information is being misused.

We may also preserve records, investigate activity, block users, report to providers, respond to law enforcement or take legal action where appropriate.

35. Changes to This Policy

We may update this Health Data Handling Policy from time to time to reflect changes in:

• law;
• Google Play requirements;
• Apple App Store requirements;
• health app declaration requirements;
• consumer health data laws;
• FTC rules;
• provider requirements;
• SX Consent features;
• security practices;
• evidence workflows;
• health-related feature design.

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

Continued use of health-related features after the updated Policy becomes effective means you acknowledge and accept the updated Policy, where permitted by law.

36. Health Data Consent Checkbox

For onboarding or health feature activation, SX Consent may use language such as:

“I confirm that I am at least 18 years old. I understand that SX Consent is not a healthcare provider, telemedicine provider, laboratory, medical device, medical advisor or emergency service. I expressly consent to SX Consent processing health-related declarations, document status, last tested date, vaccination-related selections, health practices selections and related metadata as described in the Health Data Handling Policy, Sensitive Data Consent, Privacy Policy and Terms and Conditions. I understand that SX Consent does not verify medical truth, does not provide medical advice, does not guarantee health safety, and does not create future or permanent consent.”

37. Contact Us

For questions about this Health Data Handling Policy:

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