Effective Date: July 13, 2026

Last Updated: July 13, 2026

This Data Deletion 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™.

This Policy explains how SX Consent users may request deletion of eligible personal data, what data may be deleted, what data may be retained, how deletion requests are verified and processed, and how data deletion interacts with account deletion, subscriptions, signed agreements, protected records, invitation-event timeline records, health-related records, sensitive data, SMS compliance records, payment records, legal obligations, security logs, provider obligations and multi-party invitation records.

SX Consent is a private invitation, confidentiality, privacy, reputation-protection and protected recordkeeping platform for verified adults. Because SX Consent may generate protected invitation records, one-time private invitation agreements, signatures, hashes, protected record package metadata, closure records, operational notice logs, audit records, location-readiness records and legally relevant contextual records, not all data can or should be deleted immediately upon request.

This Policy supplements and is incorporated into the SX Consent Terms and Conditions, Privacy Policy, Sensitive Data Consent, Health Data Handling Policy, SMS Terms, Payment, Cancellation and Refund Policy, Account Deletion Policy, in-app data deletion workflows, privacy request workflows, Evidence Vault notices and any provider-specific or app-store-specific requirements.

If you do not agree with this Policy, do not create or use an SX Consent account.

1. Company Information

For purposes of this Policy, “Company Parties” means SX Consent™, Beniquez Sanchez and Company LLC, BS and Co AI Labs™, their brands, owners, members, managers, officers, directors, employees, contractors, agents, affiliates, vendors, licensors, service providers, professional advisors, successors and assigns.

2. Purpose of This Policy

This Policy is intended to:

• provide a public web resource for data deletion requests;
• support Apple App Store privacy and account deletion expectations;
• support Google Play account deletion and Data Safety requirements;
• explain how users may request deletion of eligible personal data;
• distinguish data deletion from account deletion;
• distinguish data deletion from subscription cancellation;
• explain which records may be retained;
• preserve SX Consent protected record integrity;
• protect multi-party invitation records;
• protect signed agreements and related agreement metadata;
• protect legal, security, fraud-prevention, payment, provider and compliance obligations;
• explain retention exceptions and verification requirements;
• explain how data deletion requests may be denied, delayed, limited or partially fulfilled.

3. Data Deletion Is Not Account Deletion

Data deletion and account deletion are related but different.

Data deletion is a request to delete, restrict, de-identify, anonymize or otherwise process eligible personal data associated with your SX Consent account or use of the service, subject to this Policy and applicable law.

Account deletion is a request to delete, deactivate, disable or close your SX Consent account, subject to the Account Deletion Policy and applicable retention exceptions.

If you want to delete your account, you should also review the Account Deletion Policy at: https://sxconsent.com/account-deletion/.

If you request data deletion but do not request account deletion, SX Consent may be unable to continue providing some or all features because required data may be deleted, restricted or unavailable.

If you request account deletion but do not separately request data deletion, some eligible personal data may still be deleted as part of the account deletion process, while other data may be retained under this Policy, the Terms and Conditions and applicable law.

4. Data Deletion Is Not Subscription Cancellation

Requesting data deletion does not cancel your subscription.

If you purchased through Apple App Store, you must cancel through Apple subscription settings. If you purchased through Google Play, you must cancel through Google Play subscription settings. If you purchased through Stripe, web checkout or another authorized web payment method, you must cancel through the applicable SX Consent or provider cancellation process.

Data deletion does not create a refund right. Subscription payments remain subject to the SX Consent Payment, Cancellation and Refund Policy and any controlling app store or payment provider terms.

5. No Refund for Data Deletion

Submitting a data deletion request does not entitle you to a refund. This applies to:

• monthly subscriptions;
• quarterly subscriptions;
• annual subscriptions;
• trial conversions;
• subscription renewals;
• unused time;
• partial billing periods;
• premium features;
• protected record features;
• identity-readiness features;
• app-readiness features;
• account services;
• web purchases;
• Apple App Store purchases;
• Google Play purchases;
• Stripe purchases;
• any paid SX Consent service.

If data deletion makes certain features unavailable, you are not entitled to a refund unless a refund is required by applicable law or a controlling app store or payment provider policy.

6. How to Request Data Deletion

You may request deletion of eligible personal data through one of the following methods.

6.1 Web Data Deletion Request

You may request data deletion through: https://sxconsent.com/data-deletion/. This public resource is intended to support users who need a web-based deletion method, including users who no longer have the app installed.

6.2 In-App Data Deletion Request

When available, you may request data deletion inside the SX Consent app through Settings → Privacy → Data Deletion, or another similarly labeled privacy request workflow.

6.3 Email Request

You may email: Click Here

Your request should include:

• full legal name;
• SX Consent account email;
• mobile phone number associated with the account;
• country and state of residence;
• whether you also want account deletion;
• the categories of data you want deleted, if known;
• any request ID, if available;
• a clear statement that you are requesting deletion of eligible personal data.

Do not send sensitive invitation details, optional personal health documents, government ID images, private notes, protected record package contents or other highly sensitive information by email unless specifically requested through a secure process.

7. Identity Verification for Data Deletion Requests

SX Consent must protect sensitive information and multi-party invitation records. We may require verification before processing a data deletion request.

We may request or verify:

• legal name;
• account email;
• phone number;
• recent login;
• phone verification;
• email verification;
• device verification;
• PIN confirmation;
• identity verification status;
• transaction ID;
• support history;
• account metadata;
• signed statement;
• additional proof of authority if the request is made by an authorized agent.

We may deny, delay or limit a request if we cannot verify that the request comes from the account holder or authorized representative.

8. Authorized Agents

Where required by law, you may authorize another person to submit a data deletion request on your behalf. SX Consent may require:

• written authorization;
• proof of identity of the requester;
• proof of identity of the account holder;
• proof of authority;
• power of attorney where applicable;
• additional security checks.

SX Consent may deny requests from unauthorized persons, unverifiable agents or requests that create legal, security, privacy, operational or protected-record risk.

9. Categories of Data That May Be Eligible for Deletion

Subject to verification, retention exceptions and technical limitations, SX Consent may delete, restrict, anonymize, de-identify or archive eligible data such as:

• account profile fields;
• non-essential “About Me” information;
• non-essential profile preferences;
• user settings;
• certain device tokens;
• certain inactive authentication tokens;
• certain draft records not tied to multi-party workflows;
• certain support messages;
• certain unused onboarding data;
• certain non-finalized requirement profile drafts;
• certain non-essential analytics data;
• certain app preferences;
• certain notice preferences;
• certain non-essential cached records;
• certain data not required for legal, protected-record, security, fraud, payment, provider or compliance reasons.

Eligibility depends on context. Data that appears deletable in one situation may be retained in another if it is connected to a signed agreement, protected record package, dispute, legal hold, active protected invitation workflow, multi-party invitation record or provider obligation.

10. Categories of Data That May Be Retained

SX Consent may retain data after a deletion request where reasonably necessary or permitted, including:

• signed agreements;
• signature metadata;
• protected record packages;
• document hashes;
• manifest hashes;
• active invitation-event records;
• temporarily-left event records;
• returned-to-event records;
• early event departure records;
• manually-ended participation records;
• closure records;
• operational notice logs;
• SMS opt-in and opt-out records;
• email verification records;
• phone verification records;
• device security records;
• identity verification metadata;
• adult verification metadata;
• payment records;
• subscription records;
• app store receipt metadata;
• refund records;
• chargeback records;
• support records;
• legal records;
• audit logs;
• workflow integrity events;
• location-readiness events;
• invitation-zone records;
• fraud-prevention records;
• security logs;
• provider records;
• tax and accounting records;
• account deletion request records;
• data deletion request records;
• records involving another user;
• records required by law;
• records needed to enforce Terms and Conditions;
• records needed to protect rights, privacy, security, safety or property.

11. Reasons SX Consent May Retain Data

SX Consent may retain data where reasonably necessary to:

• comply with law;
• respond to legal process;
• preserve protected record integrity;
• preserve signed agreement integrity;
• preserve multi-party invitation records;
• protect another participant’s rights;
• maintain audit trails;
• investigate fraud;
• prevent abuse;
• prevent underage use;
• prevent repeat violations;
• defend legal claims;
• resolve disputes;
• comply with app store requirements;
• comply with provider requirements;
• comply with tax and accounting obligations;
• process subscriptions;
• defend chargebacks;
• maintain SMS consent evidence;
• maintain opt-out evidence;
• maintain security logs;
• preserve workflow integrity records;
• enforce Terms and Conditions;
• comply with legal holds;
• protect SX Consent, Company Parties, users, providers and the public.

12. Evidence Vault, Protected Records and Data Deletion

SX Consent may generate contextual protected records, protected record packages, protected record metadata, timestamps, hashes, signed agreement records, closure records, operational notice logs, workflow integrity events, location-readiness records and audit trails.

These records may be retained even after a data deletion request where needed for:

• protected record integrity;
• legal claims;
• dispute resolution;
• fraud prevention;
• multi-party invitation records;
• workflow review;
• compliance;
• enforcement;
• court, arbitration or legal proceedings;
• protection of another participant’s rights.

Protected records are contextual records. They are not legal conclusions and are not absolute proof. However, because they may be important to users and Company Parties, SX Consent may preserve them when deletion would compromise integrity, legal rights, compliance obligations or another user’s rights.

13. Signed Agreements and Data Deletion

If your data appears in a one-time private invitation agreement that was signed, accepted, generated, sealed, exported or otherwise preserved through SX Consent, SX Consent may retain that agreement and related metadata.

Signed agreements may include:

• participant identifiers;
• legal names or verified identity indicators;
• agreement version;
• accepted terms;
• privacy expectations;
• confidentiality provisions;
• non-disparagement provisions;
• social media restrictions;
• non-disclosure provisions;
• device and recording restrictions;
• image, likeness and voice protection language;
• optional personal health-related status indicators if included;
• location context if included;
• signature status;
• signature timestamps;
• document hashes;
• protected record metadata.

Deleting one participant’s data may not delete, invalidate, modify, remove, weaken or alter the signed agreement, associated records, integrity metadata, retention obligations or another participant’s rights.

14. Multi-Party Invitation Records

SX Consent records may involve more than one user. Multi-party invitation records may include:

• invitations;
• cross-intake results;
• requirement matches;
• accepted requirements;
• declined requirements;
• agreement drafts;
• signed agreements;
• invitation-event timeline records;
• location-readiness logs;
• operational notice records;
• closure responses;
• protected record packages;
• support records involving multiple participants;
• workflow integrity events;
• audit records.

One user’s deletion request may not delete data that belongs to, affects, protects, documents or preserves the rights of another user. SX Consent may retain multi-party invitation records where necessary to preserve protected record integrity, user rights, legal obligations, dispute records, workflow integrity records or platform integrity.

15. Active or Unresolved Protected Invitation Workflow Records

SX Consent may deny, delay, limit or pause data deletion if the account has an active or unresolved protected invitation workflow.

Unresolved lifecycle states may include:

• pending invitation;
• accepted invitation;
• cross-intake in progress;
• agreement created;
• pending signatures;
• signed agreement;
• protected record package pending;
• protected record package sealed;
• active invitation;
• temporarily-left event status;
• returned-to-event status;
• early event departure status;
• manual end status;
• closure pending;
• help requested;
• unresolved workflow integrity event;
• unresolved privacy request;
• unresolved data deletion request;
• unresolved account deletion request;
• unresolved legal hold;
• unresolved chargeback or payment dispute.

Data deletion may be processed after the lifecycle is resolved, subject to retention exceptions, provider limitations, legal holds, app store requirements, multi-party records and applicable law.

16. Health-Related Data and Data Deletion

If optional health-related features were used, health-related data may be deleted, restricted or retained depending on context.

Health-related data may include:

• health declaration requirement;
• last tested date where provided;
• optional personal health document status;
• optional personal health document metadata;
• vaccination-related selections where enabled;
• health-practices selections where enabled;
• health-readiness acknowledgments;
• health-related requirement acceptance or decline;
• health-related protected record metadata.

SX Consent may retain health-related data where it is part of:

• a signed agreement;
• a protected record package;
• a cross-intake result;
• an invitation-specific requirement;
• an audit log;
• a workflow integrity event;
• a legal record;
• a provider record;
• a fraud-prevention record;
• a multi-party invitation record.

SX Consent is not a healthcare provider, telemedicine provider, clinic, laboratory or medical service. Health-related data is handled according to the Health Data Handling Policy, Sensitive Data Consent, Privacy Policy and applicable law.

17. Sensitive Data and Data Deletion

Sensitive data may include:

• identity verification status;
• adult verification status;
• phone number;
• email address;
• profile photo;
• gender;
• relationship status;
• private requirements;
• private requirement selections;
• optional personal health-related information;
• readiness settings;
• location-readiness records;
• trusted contact configured status where applicable;
• support-path configured status where applicable;
• private note status where applicable;
• signature metadata;
• protected record metadata;
• closure records.

Sensitive data may be deleted where eligible, but SX Consent may retain sensitive data where necessary for legal, security, protected-record, fraud-prevention, multi-party invitation record, workflow integrity, provider, payment, tax/accounting or compliance purposes.

18. Identity Verification Data

SX Consent may use third-party identity or adult verification providers. A data deletion request to SX Consent may delete or restrict eligible SX Consent-held provider metadata, but may not delete data controlled by the provider.

Identity verification provider data may include:

• government ID images;
• selfie/liveness images;
• document authenticity checks;
• verification transaction IDs;
• biometric-related analysis;
• verification status;
• fraud-prevention metadata;
• provider logs.

Unless expressly stated otherwise, SX Consent does not intend to store raw government ID images, selfie/liveness images or biometric templates in its own database. You may need to contact the identity verification provider directly for provider-held data.

19. SMS and Messaging Data

SX Consent may retain SMS-related and operational messaging data for compliance and security reasons. SMS data may include:

• mobile number;
• opt-in record;
• opt-out record;
• HELP/STOP activity;
• SMS consent screen version;
• verification code request metadata;
• delivery logs;
• provider message IDs;
• carrier metadata;
• timestamps;
• audit logs.

SX Consent may retain SMS records for Twilio compliance, A2P 10DLC compliance, carrier compliance, TCPA compliance, consent evidence, opt-out evidence, fraud prevention, account security, dispute resolution and legal defense. SMS deletion may be limited where records are needed for compliance or proof of consent/opt-out.

20. Payment and Subscription Data

SX Consent may retain payment, billing and subscription records after a data deletion request. Payment-related records may include:

• transaction IDs;
• invoices;
• receipts;
• plan type;
• subscription status;
• renewal status;
• cancellation status;
• app store receipt metadata;
• Stripe metadata;
• RevenueCat metadata;
• refund records;
• chargeback records;
• tax records;
• accounting records.

These records may be retained for tax compliance, accounting, legal compliance, chargeback defense, fraud prevention, subscription administration, app store compliance and dispute resolution. Deleting payment-related data does not cancel subscriptions and does not create a refund right.

21. Security Logs and Fraud-Prevention Data

SX Consent may retain security and fraud-prevention data even after a deletion request. This may include:

• IP addresses;
• device identifiers;
• login records;
• failed login attempts;
• suspicious activity logs;
• rate-limit logs;
• fraud signals;
• abuse reports;
• duplicate account indicators;
• verification failure records;
• account takeover indicators;
• security event logs;
• ban or enforcement records.

These records may be retained to protect users, prevent fraud, prevent repeat abuse, secure the platform, enforce Terms and Conditions, protect Company Parties and comply with law.

22. Location Data and Data Deletion

SX Consent may delete eligible location data where it is not required for legal, security, protected-record or multi-party invitation purposes.

However, location-related data may be retained if it is part of:

• invitation-zone records;
• active invitation-event records;
• location-readiness events;
• arrival confirmation;
• protected record package metadata;
• workflow integrity records;
• audit logs;
• signed agreement context;
• legal hold;
• dispute record.

Location data is contextual. SX Consent is not designed for permanent tracking or ongoing surveillance, but invitation-related location-readiness records may be retained where necessary for legal, protected-record, security, multi-party invitation, provider or compliance purposes.

23. Private Notes and Closure Responses

If SX Consent supports private notes or closure responses, deletion depends on the context. SX Consent may delete eligible private notes where they are not part of:

• a signed agreement;
• a sealed protected record package;
• a help request;
• a workflow integrity event;
• a legal hold;
• a support case;
• a dispute record;
• a multi-party invitation record;
• an audit trail.

Closure responses may be retained where needed to preserve invitation-closure integrity, protected records, legal claims, user rights, workflow integrity records or compliance records.

24. Support, Legal, Privacy and Security Communications

SX Consent may retain communications with support, privacy, legal or security teams where necessary to:

• process your request;
• prove receipt;
• prove completion;
• resolve disputes;
• investigate fraud;
• investigate abuse;
• comply with law;
• defend legal claims;
• maintain security;
• enforce Terms and Conditions;
• comply with provider requirements;
• respond to regulators or app stores.

Support communications may be deleted, restricted, archived or retained when eligible or required by law, provider obligation, legal hold or operational need.

25. Backup Systems

Data deleted from active systems may remain temporarily in backups, archives, logs, disaster recovery systems or business continuity systems.

Backup data may not be immediately deleted if immediate deletion would compromise:

• security;
• disaster recovery;
• system integrity;
• protected record integrity;
• legal compliance;
• operational reliability.

Backup data is generally isolated from active use and may be overwritten or expired according to retention schedules. Restored backup data may be subject to re-deletion or restriction where appropriate.

26. De-Identification, Anonymization and Aggregation

Where appropriate, SX Consent may de-identify, anonymize, aggregate, hash, tokenize, archive or restrict data instead of deleting it.

De-identified, anonymized or aggregated data may be used for:

• security analysis;
• fraud prevention;
• system integrity;
• compliance reporting;
• usage analytics;
• reliability monitoring;
• product improvement;
• legal defense;
• audit purposes.

SX Consent will not attempt to re-identify de-identified data except where permitted by law for security, testing, compliance, legal, protected-record integrity or fraud-prevention purposes.

27. Service Providers and Data Deletion

SX Consent may use third-party providers to operate the platform. Providers may include:

• hosting providers;
• database providers;
• identity verification providers;
• SMS providers;
• email providers;
• payment processors;
• app stores;
• subscription infrastructure providers;
• error monitoring providers;
• mapping/geocoding providers;
• support tools;
• security providers;
• legal and compliance advisors.

When appropriate and required, SX Consent may instruct service providers to delete eligible personal data. However, providers may retain data under their own policies, legal obligations, security requirements, fraud-prevention rules, tax requirements, provider compliance obligations or contractual terms. You may need to contact certain providers directly for provider-controlled data.

28. App Store and Google Play Data Deletion

SX Consent provides this public data deletion resource to support app store expectations and user access.

SX Consent intends to provide, where required:

• a public web resource for data deletion requests;
• an in-app privacy request path;
• disclosures in the Privacy Policy;
• disclosures in Google Play Data Safety;
• disclosures in Apple App Privacy details;
• information about account deletion;
• information about retained data.

Nothing in this Policy limits any non-waivable rights required by Apple, Google, applicable law or controlling provider terms.

29. Legal Holds

SX Consent may delay, suspend, deny or limit data deletion when records are subject to a legal hold. Legal holds may arise from:

• litigation;
• arbitration;
• court order;
• subpoena;
• government request;
• law enforcement request;
• user dispute;
• workflow integrity event;
• privacy complaint;
• fraud investigation;
• chargeback;
• payment dispute;
• regulator inquiry;
• provider investigation;
• internal investigation.

Data subject to a legal hold may be preserved until the legal hold is lifted or until retention is no longer reasonably necessary.

30. Fraudulent, Abusive or Bad-Faith Requests

SX Consent may deny, delay, restrict or investigate deletion requests that appear:

• fraudulent;
• abusive;
• automated;
• excessive;
• repetitive;
• unverifiable;
• made by an unauthorized person;
• designed to destroy protected records;
• designed to evade payment obligations;
• designed to interfere with another user’s rights;
• designed to conceal misconduct;
• designed to obstruct legal process;
• connected to fraud, chargebacks, harassment, coercion, workflow integrity events or Terms violations.

SX Consent may preserve records necessary to investigate or prevent abuse, protect Company Parties, protect users, enforce Terms and Conditions, comply with law or maintain protected record integrity.

31. Timeframe for Processing Requests

SX Consent will attempt to respond to verified data deletion requests within the timeframe required by applicable law.

Processing time may vary based on:

• identity verification;
• request scope;
• account status;
• active protected invitation workflows;
• protected records;
• multi-party invitation records;
• provider dependencies;
• backup systems;
• legal holds;
• payment disputes;
• security investigations;
• technical complexity;
• applicable law.

If additional time is needed, SX Consent may notify you where required or appropriate.

32. Request Outcomes

After review, SX Consent may:

• approve the request;
• partially approve the request;
• deny the request;
• ask for more information;
• require identity verification;
• delay processing due to legal hold;
• restrict data instead of deleting it;
• anonymize or de-identify data;
• archive data;
• retain data under an exception;
• refer you to a provider-controlled process;
• close the request as unverifiable or duplicative.

Where legally required, SX Consent may explain the general reason for denial, delay or limitation.

33. Appeals

If your data deletion request is denied, limited or delayed, you may contact: Click Here with the subject line: Data Deletion Appeal.

Your appeal should include:

• full legal name;
• account email;
• mobile number;
• request ID, if available;
• reason for appeal;
• supporting documentation.

SX Consent will review appeals according to applicable law, internal procedures, operational capacity, security needs and protected record obligations.

34. Non-Discrimination

SX Consent will not unlawfully discriminate against users for exercising privacy rights.

However, if data deletion prevents SX Consent from providing required functionality, verifying identity, maintaining app readiness, processing operational notices, preserving protected record integrity, maintaining security or complying with law, SX Consent may restrict or disable features that require that data.

Feature loss caused by data deletion is not unlawful discrimination and does not create a refund right.

35. Children and Minors

SX Consent is for verified adults only.

If SX Consent learns that data was submitted by or about a minor, SX Consent may delete, restrict, preserve or report information as appropriate based on law, security, protected record integrity, legal obligations and platform integrity.

Parents, guardians or legal representatives may contact Click Here regarding suspected minor data.

36. Deceased Users

If a user is deceased, SX Consent may process data requests from an authorized representative where required or permitted by law. SX Consent may require:

• proof of death;
• proof of authority;
• government-issued identification;
• court appointment;
• executor documentation;
• legal authorization.

SX Consent may preserve records where necessary for legal, protected-record, multi-party invitation, payment, tax, security or compliance purposes.

37. International Data Deletion Rights

Depending on your jurisdiction, you may have rights to request deletion, erasure, restriction, objection, withdrawal of processing permission where applicable, correction, access or portability.

SX Consent will evaluate requests under applicable laws, including where relevant:

• U.S. state privacy laws;
• California privacy laws;
• consumer health data laws;
• GDPR;
• UK GDPR;
• other applicable privacy or data protection laws.

Rights may vary by jurisdiction and are subject to exceptions, including legal compliance, signed agreement integrity, provider obligations, protected record integrity, multi-party invitation records and fraud-prevention needs.

38. Data Deletion and Invitation-Specific Participation Records

Data deletion relates to information processing. Data deletion is not the same as participation in a real-world interaction.

Deleting data does not:

• create future participation;
• create permanent participation;
• waive legal rights;
• revoke or modify records already signed;
• erase another person’s rights;
• invalidate protected record packages;
• guarantee legal outcomes;
• remove all risk;
• guarantee deletion from third-party systems;
• guarantee deletion from another user’s device;
• guarantee deletion of screenshots or external copies.

Participation in any invitation remains voluntary and invitation-specific. SX Consent records do not create future participation, permanent participation, legal immunity or guaranteed outcomes.

39. Data Deletion and Third-Party Copies

SX Consent may not be able to delete data that exists outside SX Consent systems, including:

• screenshots taken by users;
• downloads made by users;
• exports provided to users;
• copies shared with legal counsel;
• copies shared with courts;
• copies held by payment providers;
• copies held by identity providers;
• copies held by app stores;
• copies held by SMS providers;
• copies held by email providers;
• copies held by other participants;
• copies stored on user devices;
• copies stored in third-party backups.

SX Consent may delete or restrict data in its own systems where eligible, but cannot guarantee deletion from third-party systems outside its control.

40. Data Deletion and User Responsibilities

Before submitting a data deletion request, you are responsible for:

• deciding whether you also want account deletion;
• canceling subscriptions if you do not want future billing;
• exporting eligible records you may need later;
• resolving active protected invitation workflows;
• completing closure responses;
• understanding that some data may be retained;
• understanding that deletion may disable features;
• understanding that deletion may be irreversible;
• understanding that deletion does not create a refund right;
• understanding that multi-party invitation records may remain.

SX Consent is not responsible if you delete data and later want access to records that were eligible and deleted.

41. Data Deletion Request Form Fields

The public data deletion form may request:

• full legal name;
• SX Consent account email;
• mobile number associated with the account;
• country and state;
• request type;
• whether account deletion is also requested;
• categories of data requested for deletion;
• purchase platform;
• active subscription status;
• active or unresolved protected invitation workflow status;
• optional message;
• identity verification confirmation;
• acknowledgment checkbox.

Do not submit unnecessary sensitive data in the form.

42. Required Acknowledgment for Data Deletion Requests

Before submitting a data deletion request, SX Consent may require you to acknowledge:

• data deletion is not account deletion unless requested;
• data deletion is not subscription cancellation;
• data deletion does not create a refund right;
• some records may be retained;
• signed agreements may be retained;
• protected record packages may be retained;
• multi-party invitation records may be retained;
• SMS compliance records may be retained;
• payment records may be retained;
• identity verification metadata may be retained;
• data deletion may disable features;
• deletion may be irreversible;
• SX Consent may verify your identity;
• SX Consent may deny or limit deletion where permitted or required.

43. Changes to This Policy

SX Consent may update this Data Deletion Policy from time to time to reflect changes in:

• law;
• Apple App Store requirements;
• Google Play requirements;
• privacy laws;
• consumer health data laws;
• provider requirements;
• account deletion workflows;
• data deletion workflows;
• Evidence Vault architecture;
• SMS compliance requirements;
• identity verification requirements;
• payment provider requirements;
• platform features;
• security practices;
• business operations.

The “Last Updated” date indicates when this Policy was last revised. Continued use of SX Consent after an updated Policy becomes effective means you acknowledge the updated Policy where permitted by law.

44. Final Data Deletion Acknowledgment

By submitting a data deletion request, you acknowledge and agree that:

1. Data deletion is not the same as account deletion.
2. Data deletion is not subscription cancellation.
3. Data deletion does not create a refund right.
4. You are responsible for canceling subscriptions through the platform where you purchased.
5. Some data may be deleted, restricted, archived, de-identified or retained.
6. SX Consent may verify your identity before processing the request.
7. Signed agreements may be retained.
8. Protected record packages may be retained.
9. Multi-party invitation records may be retained.
10. Operational notice logs may be retained.
11. SMS consent and opt-out records may be retained.
12. Payment and tax records may be retained.
13. Identity verification metadata may be retained where necessary.
14. Health-related metadata may be retained where necessary.
15. Location-readiness records may be retained where necessary.
16. Workflow integrity events and audit logs may be retained.
17. Legal holds may delay deletion.
18. Fraud or chargeback investigations may delay deletion.
19. Provider-held data may require provider-specific requests.
20. Deletion may disable features.
21. Deleted data may not be recoverable.
22. SX Consent may deny, limit or delay deletion where permitted or required by law.
23. This Policy is incorporated into the SX Consent Terms and Conditions.

45. Contact Information

For data deletion questions:
• Privacy: Click Here
• Support: Click Here
• Legal: Click Here
• Security: Click Here
• Mailing Address: Beniquez Sanchez and Company LLC, 1317 Edgewater Dr. Num. 7387, Orlando, FL 32804