This is a courtesy translation. If there is any difference between this version and the Spanish version, the Spanish version prevails. Read the Spanish version
Legal
Privacy Policy
Last updated: October 29, 2026 (version 2.0) · Effective since: January 1, 2026 · Data controller: Orbita Technologies LLC
Preamble — Statement of Commitment
Fansxity is operated by Orbita Technologies LLC, a company organized in Wyoming, U.S.A. (“Orbita”). Fansxity ("we", "our", "us") respects your right to privacy and undertakes to protect your personal data with the utmost diligence, transparency and security.
This Privacy Policy describes how we collect, use, store, protect, share and delete the personal information of users ("you", "your", "User") of the fansxity.com Platform and its subdomains, in strict compliance with:
| Jurisdiction | Applicable Legislation |
|---|---|
| Argentina | Argentine Law 25,326 on Personal Data Protection + Regulatory Decree No. 1558/2001 + Provision 4/2019 AAIP |
| European Union | General Data Protection Regulation (GDPR) 2016/679 + ePrivacy Directive 2002/58/EC |
| United States | CCPA/CPRA (California), VCDPA (Virginia), CTDPA (Connecticut), CPA (Colorado), UCPA (Utah) |
| Brazil | Lei Geral de Proteção de Dados (LGPD) 13.709/2018 |
| Colombia, Chile and Argentina | Law 1581/2012 (Colombia), Law 19.628 (Chile), Argentine Law 25,326 (Argentina) |
| International | Council of Europe Convention 108+, APEC Privacy Framework |
READ THIS POLICY CAREFULLY. If you do not agree to ANY of its provisions, DO NOT ACCESS, DO NOT REGISTER AND DO NOT USE THE PLATFORM.
1. Identification of the Data Controller
1.1 Controller Details
| Field | Information |
|---|---|
| Legal Name | Orbita Technologies LLC (a company organized in Wyoming, U.S.A.) |
| Trade Name | Fansxity |
| Registered Address | Orbita Technologies LLC, 30 N Gould St, Ste R, Sheridan, WY 82801, USA |
| legal@fansxity.com | |
| Privacy Email | legal@fansxity.com |
| Telephone | Contact by email: legal@fansxity.com |
| Legal Representative | Orbita Technologies LLC — Legal Department |
1.2 Privacy Contact
For any inquiry or request regarding your personal data (access, rectification, erasure, objection, portability or any other right), write to legal@fansxity.com.
1.3 Database
- Database name: Fansxity Users
- Controller: Orbita Technologies LLC
- Purpose: User account management, payment processing, provision of the Platform's services
- Server location: Neon (PostgreSQL) — Region us-east-1 (AWS US East - N. Virginia, U.S.A.)
- File storage: Supabase Storage
2. Data We Collect
2.1.1 Registration and Authentication Data
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Username | Unique alias for identification on the Platform | Low | Public identification |
| Email address | Email for sign-in and notifications | Low | Authentication, transactional communication |
| Password | Access credential (stored encrypted by Clerk) | High | Account security |
| Date of birth | For verification of minimum age (18 years) | Medium | Legal age compliance |
| Phone number | Optional, for 2FA and account recovery | Medium | Security, two-step verification |
Providers: Clerk Authentication (SOC 2 Type II, GDPR-compliant)
2.1.2 Creator Profile Data
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Stage name | Public name for Fans | Low | Personal brand identification |
| Biography | Personal description of the Creator | Low | Engagement with Fans |
| Profile photo | Facial image for identification | Medium | Visual identification |
| Cover image | Profile banner | Low | Aesthetic personalization |
| Social media links | URLs of Instagram, Twitter, TikTok, etc. | Low | Cross-promotion |
| Rates and prices | Subscriptions, chats, tips | Low | Service configuration |
| Availability schedule | Service hours | Low | Expectation management |
2.1.3 Identity Verification Data (Mandatory for Creators)
WARNING: This data is SENSITIVE DATA under Argentine Law 25,326 (Art. 5) and GDPR (Art. 9). Its processing requires EXPLICIT AND INFORMED consent.
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Identity document | National ID (DNI), passport or driver's license (front and back) | VERY HIGH | Age and identity verification |
| Liveness test and facial match | Live capture of the face, compared with the photo on the document (processed by Didit) | VERY HIGH | Biometric match verification |
| Tax information | CUIT/CUIL, SSN, EIN, VAT depending on country | VERY HIGH | Tax compliance |
| USDT address (TRON network) | Address to receive withdrawals of earnings | High | Payment of earnings |
- Storage: verification is performed by Didit, which processes the document and facial images; Fansxity retains the result and the verified age. If the manual backup verification is used, the document and selfie are stored in Supabase Storage with PRIVATE access (the selfie is deleted 7 days after resolution), with no public access, solely for the authorized compliance team. Persons who appear in a Creator's content go through the same verification and sign an authorization, which is stored as a PDF in private storage.
- Retention: While the account is active + 5 years after closure (legal tax obligation).
2.1.4 Content Published by the User
| Data Type | Description | Primary Purpose |
|---|---|---|
| Images | Photos published on the profile or in messages | Service content |
| Videos | Uploaded recordings or live streams | Service content |
| Text | Messages, biographies, descriptions, posts | Communication |
| Audio | Voice messages, recordings | Communication |
| Files | Any other digital material uploaded | Service content |
IMPORTANT: You retain all intellectual property rights in your content. By publishing it, you grant us a limited license in accordance with the Terms and Conditions, Section 5.2.
2.1.5 Private Communications
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Chat sessions | Messages between Creator and Fan (private or live) | HIGH | Provision of the service |
| Asynchronous conversations | Messages saved for later reading | HIGH | Provision of the service |
| Support tickets | Communications with the customer support team | Medium | Technical support |
| DMCA notices | Name, email, description of the copyright claim | Medium | Legal compliance |
2.1.6 Legal Acceptance Data
| Data Type | Description | Primary Purpose |
|---|---|---|
| Date of acceptance of Terms | Timestamp of when you accepted the T&C | Evidence of contract |
| Date of acceptance of Privacy Policy | Timestamp of when you accepted this Policy | Evidence of consent |
| IP address at acceptance | Device IP at the time of acceptance | Forensic evidence |
| Device User-Agent | Browser, operating system, version | Forensic evidence |
| Session ID | Unique token of the registration session | Linking to registration |
2.2.1 Technical Connection Data
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| IP address | Public IP of the device | Medium | Security, approximate geolocation, fraud prevention |
| User-Agent | Browser, version, operating system, device | Low | Compatibility improvement |
| Access time | Timestamp of each visit | Low | Usage analysis |
| Session duration | Time spent on the Platform | Low | Engagement metrics |
| Session cookies | Persistent authentication token | Medium | Session maintenance |
2.2.2 Usage and Browsing Data
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Pages visited | Profile URLs, content viewed | Low | Preference analysis |
| Content viewed | Which photos/videos were viewed | Medium | Improvement of recommendations |
| Interactions | Likes, comments, shares, saves | Low | Engagement metrics |
| Time on content | How long each item is viewed | Medium | Preference analysis |
| Device used | Mobile, tablet, desktop, specific model | Low | Technical optimization |
| Operating system | iOS, Android, Windows, macOS, Linux | Low | Compatibility |
2.2.3 Payment Data
Today, payments are collected only in USDT on the TRON network, directly to a Fansxity address and without a payment intermediary. Fansxity does NOT store card data: when card payment is enabled, it will be processed by a certified processor and this policy will be updated beforehand.
| Data | What does Fansxity retain? |
|---|---|
| Payment record (ID, exact amount, Fansxity collection address, status, dates) | YES |
| Transaction hash (public on the blockchain) | YES, to verify the payment and for auditing |
| Creator's USDT withdrawal address | YES, to pay out their earnings |
| Private keys or seed phrases of your wallet | NEVER: we do not request or receive them |
| Card data | NOTHING (cards are not currently accepted) |
2.2.4 Approximate Location Data
| Data Type | Description | Sensitivity | Primary Purpose |
|---|---|---|---|
| Country of origin | Derived from IP address (IP geolocation) | Low | Payment routing, geoblocking |
| Region/Province | Approximation at regional level (not exact city) | Low | Creator geoblocking compliance |
| Time zone | Derived from IP or device settings | Low | Display times in local time zone |
We do NOT collect: exact GPS location, physical postal address (except for invoicing), or real-time location data.
2.2.5 Audit Logs
| Data Type | Description | Primary Purpose |
|---|---|---|
| Sign-in | Timestamp, IP, device, success/failure | Security, detection of unauthorized access |
| Profile changes | Which fields were modified, when, from which IP | Traceability, forensics |
| Acceptance of terms | Which version, when, from which IP | Legal evidence |
| Content uploads | Which file, when, size, IP | Moderation, security |
| Transactions | Which action, amount, timestamp, IP | Financial auditing, fraud |
| Data export | When requested, which data, IP | Exercise of ARCO rights (access, rectification, cancellation, objection) |
| Account closure | When, from which IP, device | Auditing |
2.3 Data We Do NOT Collect
Fansxity explicitly does NOT collect:
- Health status, illnesses, HIV/AIDS (sensitive health data)
- Religious, philosophical or moral beliefs
- Political, trade union or labor affiliation
- Sexual orientation (unless evident from content voluntarily published by the Creator)
- Racial or ethnic origin
- Criminal convictions or administrative offenses
- Data of minors under 18 years of age (the Platform is exclusively for persons over 18)
- Plaintext passwords (always encrypted with bcrypt/Argon2 by Clerk)
- Full credit card data (payment processors only)
2.4 Biometric Data (Verification with Didit)
To verify age and identity we use Didit as a provider. Didit checks the document, runs a liveness test and compares your face with the photo on the document: this is processing of biometric data, carried out by Didit on behalf of Fansxity, for the sole purpose of confirming that you are a real person, over 18, and who you say you are.
- What Fansxity stores: the verification session identifier, the link to that session at Didit, the result of each check (document, liveness, face match: approved, declined or in review), the verified age and, if declined, the reason. Fansxity does not download or store the images of the document or the face, nor any biometric templates or prints.
- What Didit stores: the images and biometric data from the session, under its own policy and retention periods. We ask for your express consent before verifying.
- Manual backup verification: only if Didit cannot be started, a Creator may upload a photo of the document and a selfie to private storage, where the authorized team reviews them. In that case Fansxity keeps the selfie for only 7 days after the verification is resolved and then deletes it (the result is kept, not the image). If you request deletion of your data, Fansxity also asks Didit to delete your session (see 7.1).
- How long: the verification result is kept while the account is active and for 5 years after closure (see 7.1).
- How to request deletion: through Privacy requests or by writing to legal@fansxity.com. It is granted except for what the law requires us to keep (see 7.3).
3. Purposes of Processing
3.1 Primary Purposes (Performance of Contract)
| Purpose | Data Involved | Legal Basis | Is It Mandatory? |
|---|---|---|---|
| Create and manage your user account | Username, email, password, date of birth | Performance of contract (Art. 6.1.b GDPR, Art. 10 Argentine Law 25,326) | YES — Without this you cannot use the Platform |
| Account authentication and security | Email, password, IP, User-Agent, 2FA | Performance of contract + Legitimate interest (security) | YES |
| Process payments and manage subscriptions | Transaction ID, amount, payment method, CUIT (for Creators) | Performance of contract | YES for Fans who pay or Creators who receive payments |
| Manage paid chat sessions | Messages, timestamp, duration, session ID | Performance of contract | YES for paid sessions |
| Distribute tips | Amount, transaction ID, receiving Creator | Performance of contract | YES for tips |
| Calculate and distribute commissions to Creators | Gross income, commission, withdrawal, CUIT | Performance of contract | YES for Creators |
| Verify compliance with minimum age (18 years) | Date of birth, identity document | Performance of contract + Legal obligation | YES — Prohibited for minors |
| Verify Creator identity | Document, selfie, proof of address, CUIT | Performance of contract + Legal obligation | YES for Creators, NO for Fans |
| Moderate content and ensure security | Published content, IP, User-Agent, reports | Legitimate interest (security) + Legal obligation | YES |
| Send transactional communications | Email, phone number (for 2FA) | Performance of contract | YES (payment confirmations, account alerts) |
| Provide technical support | Support ticket, email, description of the issue | Performance of contract | Optional (only if you contact support) |
3.2 Secondary Purposes (Explicit Consent)
| Purpose | Data Involved | Is It Mandatory? | How to Revoke |
|---|---|---|---|
| Marketing communications (news, promotions, events) | Email, username | NO | "Unsubscribe" link in email or settings panel |
| Service improvement through usage analysis | Usage data, interactions, time on content | NO | Settings → Privacy → Turn off "Usage analysis" |
| Generation of automated responses with AI (Claude AI) | Chat messages (only when the Creator enables the feature) | NO (only for Creators who enable the feature) | Turn off "AI Chat Assistant" in the Creator panel |
| Automatic translation of messages (DeepL) | Message texts | NO | Settings → Language → Turn off "Automatic translation" |
| Push notifications (mobile app only) | Device token | NO | Settings → Notifications → Turn off push |
| Participation in satisfaction surveys | Email, survey responses | NO | Do not participate or request removal from the survey list |
3.3 Legal Purposes (Legal Obligation)
| Purpose | Data Involved | Retention Period |
|---|---|---|
| Respond to DMCA notices | Name, email, description of the claim, reported content | Permanent (evidence of compliance) |
| Comply with court orders | Data requested by a competent judge | As required by the court order |
| Comply with tax obligations | CUIT, income, transactions, withdrawals | 10 years (Argentine Tax Code) |
| Prevent and report crimes (child exploitation, fraud, harassment) | Illegal content, IP, audit logs | As provided by criminal procedure |
| Comply with requirements from AAIP | All data in the database | While the investigation remains in force |
| Preserve evidence for litigation | Audit logs, messages, transactions | 5–10 years (civil statute of limitations) |
3.4 Legitimate Interest Purposes
| Purpose | Legitimate Interest | Safeguards |
|---|---|---|
| Prevention of fraud and abuse | Protection of the Platform and its users | Automated analysis with option of human appeal |
| Continuous service improvement | Improvement of user experience | Anonymized, non-identifiable data only |
| Platform security | Protection against cyberattacks | Encryption, restricted access, 24/7 monitoring |
| Business analysis and metrics | Business decision-making | Aggregated data only (non-personal) |
| Compliance with geoblocking configured by Creators | Respecting Creators' decisions | Country only, not exact city |
4. Legal Basis for Processing (GDPR and Argentine Law 25,326)
4.1 Mapping of Legal Bases by Purpose
| Purpose | GDPR Legal Basis | Legal Basis under Argentine Law 25,326 | Consent Required |
|---|---|---|---|
| Create and manage account | Art. 6.1.b (Performance of contract) | Art. 10 | NO |
| Process payments | Art. 6.1.b | Art. 10 | NO |
| Verify age and identity | Art. 6.1.c + Art. 6.1.b | Art. 10 + Art. 5 (sensitive data) | YES (for sensitive data) |
| Moderate content | Art. 6.1.f (Legitimate interest) | Art. 10 | NO |
| Send transactional emails | Art. 6.1.b | Art. 10 | NO |
| Email marketing | Art. 6.1.a | Art. 4 | YES (explicit, opt-in) |
| Usage analysis | Art. 6.1.a + 6.1.f | Art. 4 | YES (opt-in) |
| Fraud prevention | Art. 6.1.f | Art. 10 | NO |
| Comply with court orders | Art. 6.1.c | Art. 7 (Legal obligation) | NO |
| AI in chat (Claude) | Art. 6.1.a | Art. 4 | YES (explicit, opt-in) |
| Automatic translation | Art. 6.1.a | Art. 4 | YES |
4.2 Sensitive Data — Special Treatment
| Type of Sensitive Data | Do We Collect It? | Legal Basis | Safeguards |
|---|---|---|---|
| Identity document | YES (Creators only) | Explicit consent (Art. 5 Argentine Law 25,326) + Performance of contract | PRIVATE Supabase Storage, AES-256 encryption, access limited to the authorized team, deletion 5 years after closure |
| Selfie and face (biometric data) | YES (processed by Didit; Fansxity only stores the selfie in the manual backup verification) | Explicit consent | With Didit, Fansxity does not store the biometric image, only the result (see 2.4). In the manual backup verification, private storage, deleted 7 days after the verification is resolved (the document is kept) |
| Tax information (CUIT/SSN) | YES (Creators only) | Legal obligation (tax) + Consent | Encryption, access restricted to the finance team |
| Banking data | YES (for withdrawals only) | Performance of contract | Encryption, used only for payment processing |
| Explicit sexual content | YES (if the Creator publishes it) | Performance of contract (the platform allows adult content, including explicit content, which each Creator chooses to publish) | Access restricted to subscribed Fans, not indexed by search engines, age-based geoblocking |
Processing sensitive data REQUIRES EXPLICIT AND INFORMED CONSENT in writing (digital). You give this consent when you upload your identity document for verification, complete facial verification, provide CUIT/SSN for withdrawals, or publish explicit sexual content.
5. Sharing of Data with Third Parties
5.1 Fundamental Statement
Fansxity DOES NOT SELL, DOES NOT RENT, DOES NOT TRANSFER AND DOES NOT COMMERCIALIZE your personal data with third parties under any circumstances. We share personal data ONLY with the following service providers ("Data Processors"), all contractually bound to process the data solely in accordance with our instructions.
5.2 Service Providers (Data Processors)
These are the providers that currently process data on behalf of Fansxity, what each one receives and for what purpose:
| Provider | Purpose | Data Received | Location |
|---|---|---|---|
| Neon | Database (PostgreSQL) | Account, profile, posts, transactions, consents and verification records (result, not images) | U.S. (AWS us-east-1) |
| Supabase | File storage | Photos, videos, audio and PDFs (Creator agreements and 2257 consents) in private buckets; document and photo only in manual backup verification | U.S. |
| Vercel | Hosting and delivery of the application | Requests between your browser and the Platform: IP, User-Agent, pages requested, technical logs | U.S. and global network |
| Clerk | Accounts and sign-in | Email, username, credentials (encrypted), IP and User-Agent of sessions | U.S. |
| Ably | Real-time messaging and notices | Messages and events while they are delivered (chat, notifications) | EU and U.S. |
| Mux | Video upload and playback | Uploaded videos, metadata and playback data (viewer IP) | U.S. and EU |
| Daily | Live video and audio sessions | Audio and video of the session while it takes place, room and participant identifiers, IP | U.S. |
| Resend | Sending of transactional emails | Email address, username and the content of the email (confirmations, notices, acknowledgments) | U.S. |
| Didit | Identity and age verification (document, liveness test, facial match) | Images of the document and face, biometric data, name, date of birth. Returns to Fansxity the result and verified age, not the images | Per Didit's policy |
| DeepL | Message translation (only if enabled) | Text of the message to be translated | EU |
| TronGrid | Reading the TRON blockchain to detect payments and verify withdrawals | Fansxity's collection address and transaction hash, which are public blockchain data; does not receive your name or email | U.S. |
| Anthropic (Claude) | Automated AI responses (only when the Creator enables the feature) | Text of the messages in that conversation | U.S. |
| PostHog | Product usage analytics | Usage events (for example, content uploaded) associated with your internal identifier | Per PostHog's configuration |
| Upstash | Usage limits (rate limiting) against abuse | User identifier or IP during the control window, transiently | Depending on the configured region |
| Telegram | Optional notices to Creators and internal alerts | Text of the notice, only if the Creator connected their Telegram account | Per Telegram's policy |
Payment methods that are currently disabled (Stripe, Mercado Pago, NOWPayments) do not receive data. If any of them were enabled, it will be added here before being used.
5.3 Authorized Sub-Processors
Each provider may use its own sub-processors (for example, cloud infrastructure). We require each provider to have data protection terms equivalent to those of this policy. You may request the updated list at legal@fansxity.com.
5.4 International Transfers to Countries without Adequacy
Many of our providers have servers in the United States, a country that does NOT have an adequacy decision from the EU (post-Schrems II). To ensure equivalent protection we adopt: EU Standard Contractual Clauses (SCC) with all providers, a Data Protection Impact Assessment (DPIA) for each international transfer, end-to-end encryption (TLS 1.3+ in transit, AES-256 at rest), data minimization and the user's right to object.
5.5 Sharing with Government Authorities
Fansxity shares data with authorities ONLY in the following cases:
| Situation | Legal Basis | Is the User Notified? |
|---|---|---|
| Valid court order | Legal obligation (Procedural Code) | YES (unless the order prohibits notification) |
| Prosecutor's subpoena | Legal obligation | YES (after the investigation permits it) |
| Valid DMCA notice | Legal obligation (DMCA 17 U.S.C. § 512) | YES (to the infringing user) |
| AAIP request | Legal obligation (Argentine Law 25,326 Art. 17) | NO (during the investigation) |
| Prevention of serious crime | Legitimate interest + Legal obligation | YES (afterwards) |
| Child protection (CSAM) | Legal obligation (Law 26.388, PROTECT Act U.S.) | NO (reported directly to NCMEC/FBI) |
WARNING REGARDING THE CLOUD ACT (U.S.): U.S. providers (Clerk, Neon, Supabase, Vercel) may be required to share data with U.S. authorities under the CLOUD Act, even if the data is stored outside the U.S.
5.6 Business — Merger, Acquisition or Sale of Assets
If Fansxity is subject to a merger, acquisition, sale of assets or bankruptcy, your personal data may be transferred. In such case: the new controller will be bound to comply with this Policy, we will notify you by email before the transfer, and you may object to the transfer.
6. International Data Transfers
| Country or region | Purpose | Providers |
|---|---|---|
| United States | Database, hosting, storage, accounts, email, live video, blockchain reading, analytics | Neon, Supabase, Vercel, Clerk, Resend, Daily, Mux, TronGrid, Anthropic, PostHog |
| European Union | Message translation, real-time messaging and video | DeepL, Ably, Mux |
| Per each provider's policy | Identity verification and optional notices | Didit, Telegram |
Legal basis — Argentina (Argentine Law 25,326 Art. 12): countries with an adequate level of protection, or the consent of the data subject, or performance of contract. EU (GDPR Art. 44–49): Standard Contractual Clauses (SCC), adequacy, explicit consent. All transfers are protected with TLS 1.3+ in transit and AES-256 at rest.
To request information about transfers (specific countries, safeguards, copy of the SCC), send a request to legal@fansxity.com with the subject line "INFORMACIÓN TRANSFERENCIAS INTERNACIONALES" (INTERNATIONAL TRANSFERS INFORMATION).
7. Retention and Deletion of Data
7.1 Retention Periods by Data Type
| Data Type | Retention Period | Legal Basis |
|---|---|---|
| Active account data (email, username, profile) | While the account is active + 3 years after closure | Performance of contract + Statute of limitations for civil actions |
| Payment records (transactions, amounts, IDs) | 10 years | Tax obligation (Argentine Tax Code Art. 102) |
| Identity and age verification result (approved/rejected, verified age). Document and face images are processed by Didit | While the account is active + 5 years after closure | Legal obligation (anti-fraud, tax) |
| Audit logs | 5 years | Statute of limitations for actions + Evidence for litigation |
| DMCA notices | PERMANENT | Evidence of DMCA compliance (17 U.S.C. § 512) |
| Live session messages | Disappear for participants after 48 hours; kept encrypted for 90 days and then deleted | Only to handle reports, authority requests or disputes, with restricted and logged access |
| Consent records of persons appearing in content and signed Creator agreements (private PDFs) | The period required by law: 18 U.S.C. § 2257 requires keeping them for at least five years from when the content stops being distributed | Legal obligation (2257 records) |
| Published content (photos, videos, messages) | While the account is active + deletion after closure (except where legally required) | Performance of contract |
| IP and User-Agent | 2 years | Fraud prevention + Security |
| Session cookies | 30 days after last activity | Service functionality |
| Marketing data (email for newsletters) | While subscribed + 2 years after unsubscribing | Consent |
| Messages sent to the AI (Claude), only if the Creator enables the feature | Sent to the provider solely to generate the response; Fansxity does not use them to train models | Consent of the Creator |
| Database backups | 90 days (automatic rotation) | Disaster recovery |
7.2 Secure Deletion
Upon expiry of the retention period: data is marked as deleted and becomes inaccessible to users (logical deletion), then removed from production servers and backups within 90 days (physical deletion). We may issue a deletion certificate upon request. Some data is anonymized for statistical analysis.
7.3 Exceptions to Deletion
We will NOT delete your data even upon a deletion request when:
- There is a legal obligation to retain it (tax, criminal, administrative)
- The data is necessary to exercise or defend legal claims
- The data is evidence of a crime (child exploitation, fraud)
- There is a court order requiring retention
- The data is in backups (will be deleted in normal rotation within 90 days)
In these cases, we will restrict processing (storage only, no use) until the obligation expires.
7.4 Live Session Messages
Messages from live sessions disappear for participants after 48 hours, but are kept encrypted for 90 days, solely to handle reports, authority requests or disputes, with restricted and logged access. After that period they are deleted. Recording the other person without their consent is prohibited (see the Terms and Conditions, Section 5.5).
8. Data Security
8.1 Technical Security Measures
| Measure | Description | Standard |
|---|---|---|
| Encryption in transit | All data is transmitted encrypted | TLS 1.3+ (AES-256-GCM) |
| Encryption at rest | Data stored encrypted in the database and files | AES-256 (AES-GCM) |
| Secure authentication | Passwords encrypted with a strong hashing algorithm | bcrypt/Argon2 (by Clerk) |
| Two-factor authentication (2FA) | Optional for users, available for Creators | TOTP (Google Authenticator, Authy) |
| Role-based access control (RBAC) | Only authorized personnel access sensitive data | Principle of least privilege |
| Web application firewall (WAF) | Protection against OWASP Top 10 attacks | Controls of the hosting platform |
| DDoS protection | Mitigation of denial-of-service attacks | Controls of the hosting platform and usage limits |
| 24/7 monitoring | Detection of intrusions and suspicious activity | SIEM, audit logs |
| Encrypted backups | Automatic encrypted backups stored in a separate location | AWS S3 with versioning |
| Secrets management | API keys and credentials stored in a secure service | Hosting environment variables (Vercel), outside the code |
8.2 Organizational Security Measures
- Internal security policies — documented procedures for employees
- Annual data protection training for the entire team
- Mandatory confidentiality agreements (NDA) for the entire team
- Restricted access — only authorized personnel access sensitive data
- Audit log — all access to sensitive data is recorded (who, when, what)
- Annual penetration testing with a certified external firm
- Annual privacy risk assessment (DPIA)
- Incident response plan to detect, contain and notify security breaches
8.3 Security Breach Notification
In the event of a security breach affecting your personal data:
- We identify and confirm the breach within 24 hours
- We act immediately to contain the breach and assess the risk
- Notification to the AAIP (Argentina) and to the EU Data Protection Authority within 72 hours (GDPR Art. 33)
- If there is high risk to your rights: immediate notification by email with the nature of the breach, affected data, measures taken and recommendations
- Documentation of every breach (including those not subject to notification)
Contact for breaches: legal@fansxity.com
9. Rights of the Data Subject
9.1 List of Rights
| Right | Description | Law Recognizing It | How to Exercise It? |
|---|---|---|---|
| Access | Request information about what data we hold about you and how we process it | Argentine Law 25,326 Art. 14, GDPR Art. 15, CCPA §1798.100 | Send a request to legal@fansxity.com |
| Rectification | Correct inaccurate or incomplete data | Argentine Law 25,326 Art. 14, GDPR Art. 16, CCPA §1798.100 | Edit in the settings panel OR send a request |
| Erasure ("Right to be Forgotten") | Request deletion of your data when it is no longer necessary for the original purposes | Argentine Law 25,326 Art. 14, GDPR Art. 17, CCPA §1798.105 | Send a request to legal@fansxity.com |
| Restriction of processing | Request that we only store your data without using it | GDPR Art. 18, Argentine Law 25,326 Art. 14 | Send a request stating the specific reason |
| Data portability | Receive your data in a structured, commonly used and machine-readable format | GDPR Art. 20, CCPA §1798.100 | Send a request to legal@fansxity.com |
| Objection | Object to processing for marketing purposes or legitimate interest | GDPR Art. 21, Argentine Law 25,326 Art. 14 | "Unsubscribe" link in email OR send a request |
| Not to be subject to automated decisions | Not to be subject to decisions based solely on automated processing with legal effects | GDPR Art. 22, CCPA §1798.140 | Send a request to review the automated decision |
| Withdraw consent | Withdraw the consent given for processing of sensitive data or marketing | GDPR Art. 7, Argentine Law 25,326 Art. 4 | Settings panel OR send a request |
| Not to be discriminated against | Not to be discriminated against for exercising privacy rights (CCPA) | CCPA §1798.125 | N/A |
9.2 How to Exercise Your Rights
To exercise any right, send a request to legal@fansxity.com with the subject line "EJERCER DERECHO ARCO" (ARCO RIGHTS REQUEST) (e.g. "EJERCER DERECHO DE ACCESO" (ACCESS RIGHTS REQUEST)), stating your username, registered email and a specific description of the request.
Some rights can be exercised directly from the panel. Portability and account deletion are requested by email, as explained in Privacy requests and Delete my account:
- Rectification: Settings → Profile → Edit information
- Objection to marketing: Settings → Notifications → Turn off promotional emails
- Withdraw consent for AI: Settings → AI → Turn off Claude Assistant
Exercising your rights is FREE, except for manifestly unfounded or excessive requests. Response deadlines: 30 calendar days (EU, extendable to 60 if complex) and 45 calendar days (California, extendable to 90). For users in Argentina, the deadlines of Argentine Law 25,326 apply (see below).
Users in Argentina — Argentine Law 25,326
- Access (art. 14): you may request information about your data and we respond within 10 calendar days. It is free at intervals of not less than six months, unless you demonstrate a legitimate interest.
- Rectification, updating and deletion (art. 16): we resolve them within 5 business days of receiving the request. Deletion does not apply to data that we must retain due to a legal obligation.
- How to exercise them: by writing to legal@fansxity.com with the subject “EJERCER DERECHO ARCO” or from your panel (rectification, data download and account deletion).
- Complaint: if you receive no response, you may file a complaint with the Agency for Access to Public Information (AAIP), the supervisory body of Argentine Law 25,326.
9.3 Complaints to Supervisory Authorities
| Country | Supervisory Authority | Contact |
|---|---|---|
| Argentina | National Directorate for the Protection of Personal Data (AAIP) | www.argentina.gob.ar/aaip · info@aaip.gob.ar · 0800-222-2347 |
| European Union | Data Protection Authority of your country of residence | EDPB List of Authorities |
| California (U.S.) | California Privacy Protection Agency (CPPA) | oag.ca.gov/privacy/ccpa |
| Brazil | Autoridade Nacional de Proteção de Dados (ANPD) | gov.br/anpd |
10. Cookies and Similar Technologies
10.1 Cookies We Use
| Cookie Type | Name | Purpose | Duration | Is It Essential? |
|---|---|---|---|---|
| cookieauth | Clerk Authentication | Keep session signed in | 30 days | YES (basic functionality) |
| session_id | Session Identifier | Link requests to the session | 24 hours | YES |
| csrf_token | CSRF Protection | Prevent Cross-Site Request Forgery attacks | 24 hours | YES |
| preferences | User Preferences | Save language, theme (light/dark) | 1 year | NO (but improves the experience) |
| analytics_id | Analytics (optional) | Analyze use of the Platform (if enabled) | 1 year | NO (requires consent) |
10.2 Cookies We Do NOT Use
Fansxity explicitly does NOT use:
- Advertising tracking cookies (Google Ads, Facebook Pixel, etc.)
- Social media cookies for tracking outside the Platform
- Third-party marketing cookies
- Fingerprinting for advertising
10.3 Cookie Management
Essential cookies cannot be disabled (necessary for authentication, CSRF security, load balancing and fraud prevention). Without them you will not be able to sign in or access premium content.
Non-essential cookies can be disabled in: your browser settings (Chrome, Firefox, Safari, Edge), or in the Fansxity panel → Settings → Privacy → Turn off "Usage analysis".
11. Minors — Special Protection
THE PLATFORM IS DIRECTED EXCLUSIVELY AT PERSONS OVER 18 YEARS OF AGE. It is absolutely prohibited for persons under 18 to access, register or use the Platform; for adults to register minors; and for Creators to publish content featuring persons under 18 years of age (even if not sexual).
Fansxity does NOT intentionally collect data from minors. If we detect that a minor has provided their data: we immediately delete all of their data, permanently cancel the account, report to authorities if the content is illegal (CSAM) and block the email/IP to prevent re-registration.
ANY CONTENT INVOLVING PERSONS UNDER 18 YEARS OF AGE IS ILLEGAL AND WILL BE REMOVED IMMEDIATELY and reported to NCMEC/FBI (U.S.), INADI/DNPI/Specialized Prosecutor's Office (Argentina) and INTERPOL/Europol (international). Urgent reports: legal@fansxity.com with the subject line "MINOR IN CONTENT — URGENT".
12. Amendments to this Policy
Fansxity reserves the right to modify, update, replace or repeal this Policy at any time. Material changes will be notified by: publication on the Platform (at least 15 days before taking effect), email to the registered address, push notification in the mobile app, and a consent banner for changes involving new sensitive data.
CONTINUED USE OF THE PLATFORM AFTER THE EFFECTIVE DATE CONSTITUTES YOUR EXPLICIT AND UNCONDITIONAL ACCEPTANCE OF THE NEW POLICY. If you do not accept the changes, you must stop using the Platform and close your account before the effective date. The previous version remains available under Policy History.
13. General Provisions
- Language: This Policy is written in Spanish. In case of dispute between versions, the Spanish version shall prevail.
- Integration with the Terms and Conditions: This Policy forms an integral part of the Terms and Conditions by express reference. For privacy matters this Policy prevails; for other matters, the Terms.
- Severability: If any provision is declared void or unenforceable, the remaining provisions shall remain in full force and effect.
- Waiver: Any waiver of a right must be in writing. Failure to exercise a right does NOT constitute a waiver of that right.
- Assignment: Fansxity may assign this Policy in mergers or acquisitions. The user may NOT assign their rights under this Policy.
14. Contact and Official Channels
| Purpose | Channel | Response Time |
|---|---|---|
| Exercise privacy rights | legal@fansxity.com — Subject: "EJERCER DERECHO ARCO" | 30–45 days depending on jurisdiction |
| General privacy inquiries | legal@fansxity.com — Subject: "POLÍTICA DE PRIVACIDAD — CONSULTA" (PRIVACY POLICY — INQUIRY) | 3–5 business days |
| Report a security breach | legal@fansxity.com — Subject: "BRECHA DE SEGURIDAD — REPORT" (SECURITY BREACH — REPORT) | 24 hours |
| Report content involving minors | legal@fansxity.com — Subject: "MINOR IN CONTENT — URGENT" | Immediate |
| Data Protection Officer (EU) | legal@fansxity.com | 30 days |
See also: Terms and Conditions · DMCA Policy · Age Verification Policy