Privacy Policy

Last updated: 25 September 2026

This Privacy Policy describes how EXOFORCE collects, receives, generates, uses, analyzes, stores, shares, retains, and otherwise processes information in connection with EXOFORCE websites, applications, artificial-intelligence services, games, software, APIs, research systems, community services, and other services covered by this Policy (collectively, the “Services”).

EXOFORCE is operated by the EXOFORCE team (“EXOFORCE”, “we”, “us”, “our”).

Privacy questions may be sent to privacy@exoforce.org.

This Policy should be read together with the EXOFORCE Terms of Service and any privacy notice applicable to a particular Service.

1. Scope

This Policy is intended to apply broadly to EXOFORCE Services unless a Service provides a different or supplemental privacy notice.

Different Services may collect different information.

The fact that a category of information is described in this Policy does not mean every Service collects that category from every user.

EXOFORCE may introduce new Services, features, technologies, integrations, data sources, or processing activities. This Policy applies to them where they fall within its scope unless a separate notice states otherwise.

2. Information we may process

Depending on the Service and how you use it, EXOFORCE may collect, receive, generate, infer, derive, or otherwise process the categories below.

2.1 Account and identity information

This may include:

• usernames;
• display names;
• email addresses;
• account identifiers;
• profile information;
• avatars;
• authentication information;
• linked accounts;
• age or eligibility information;
• settings;
• account status;
• permissions;
• roles;
• subscription status;
• application or registration information.

EXOFORCE does not require every category for every Service.

2.2 Authentication and security information

This may include:

• login attempts;
• session information;
• authentication tokens;
• IP addresses;
• device identifiers;
• security events;
• account recovery records;
• access records;
• failed authentication attempts;
• integrity signals;
• abuse indicators;
• fraud indicators;
• suspicious activity;
• ban or restriction records;
• account associations;
• risk signals;
• security investigation material.

2.3 Device, network, and technical information

This may include:

• IP address;
• browser type;
• operating system;
• device characteristics;
• hardware information;
• software versions;
• application versions;
• language;
• locale;
• approximate location derived from technical information;
• network information;
• timestamps;
• request information;
• diagnostic information;
• performance information;
• crash information;
• configuration;
• compatibility information.

2.4 Usage and operational information

EXOFORCE may collect information about how Services are accessed and used.

This may include:

• pages or features used;
• interactions;
• commands;
• requests;
• API activity;
• model usage;
• session activity;
• event logs;
• feature usage;
• timestamps;
• navigation;
• performance;
• errors;
• moderation events;
• service state;
• operational records;
• diagnostic records.

2.5 Content you provide

EXOFORCE may process content submitted through the Services, including:

• text;
• prompts;
• conversations;
• messages;
• documents;
• source code;
• files;
• images;
• audio;
• video;
• forms;
• feedback;
• reports;
• support messages;
• applications;
• community content;
• other submissions.

Do not submit information that you are not authorized to provide.

2.6 AI interactions

For AI-related Services, EXOFORCE may process:

• prompts;
• responses;
• generated Outputs;
• uploaded files;
• retrieved material;
• conversation history;
• feedback;
• tool requests;
• tool results;
• model selections;
• model-routing information;
• usage metadata;
• evaluation information;
• safety signals;
• moderation information;
• derived representations;
• other information generated through interaction with an AI Service.

2.7 Research, training, and derived information

EXOFORCE may create or process information derived from other information.

This may include:

• classifications;
• embeddings;
• tokens;
• features;
• labels;
• rankings;
• annotations;
• evaluations;
• safety classifications;
• quality assessments;
• aggregates;
• statistical information;
• de-identified information;
• datasets;
• training examples;
• benchmark records;
• research artifacts;
• model-development data;
• other derived information.

2.8 Communications and support

If you contact EXOFORCE, we may retain:

• messages;
• correspondence;
• support tickets;
• reports;
• attachments;
• account information;
• investigation records;
• internal notes;
• resolution history.

2.9 Community, moderation, and enforcement information

EXOFORCE may process information relating to:

• reports;
• warnings;
• bans;
• suspensions;
• moderation decisions;
• investigations;
• staff notes;
• abuse reports;
• exploit reports;
• appeals where offered;
• account links;
• enforcement history;
• evidence;
• conduct affecting EXOFORCE Services.

2.10 Payment and transaction information

Where payments are available, EXOFORCE may process:

• purchase records;
• transaction identifiers;
• subscription status;
• billing status;
• currency;
• amounts;
• invoices;
• payment-provider records;
• refunds;
• disputes;
• chargebacks;
• fraud indicators.

Full payment-card information may be handled directly by third-party payment providers rather than EXOFORCE.

2.11 Cookies and similar technologies

EXOFORCE Services may use:

• cookies;
• local storage;
• session storage;
• authentication storage;
• device storage;
• SDKs;
• pixels;
• telemetry;
• similar technologies.

These may support authentication, security, preferences, analytics, functionality, measurement, experimentation, and other Service purposes.

Blocking them may cause some Services to stop functioning correctly.

2.12 Information from other sources

EXOFORCE may receive information from:

• service providers;
• authentication providers;
• payment providers;
• community platforms;
• linked services;
• public sources;
• users;
• reports;
• partners;
• security or anti-abuse sources;
• other sources where permitted.

3. How EXOFORCE may use information

EXOFORCE may process information for purposes including:

• providing the Services;
• creating and administering accounts;
• authentication;
• operating infrastructure;
• processing requests;
• delivering content;
• storing content;
• providing AI functionality;
• model inference;
• personalization;
• customer or user support;
• troubleshooting;
• compatibility analysis;
• debugging;
• service monitoring;
• analytics;
• statistics;
• measurement;
• research;
• experimentation;
• product development;
• feature development;
• service improvement;
• artificial-intelligence development;
• dataset preparation;
• AI evaluation;
• AI benchmarking;
• model training;
• model fine-tuning;
• safety training;
• quality evaluation;
• security;
• fraud prevention;
• abuse prevention;
• moderation;
• enforcement;
• detecting unauthorized access;
• investigating incidents;
• maintaining operational records;
• communicating with users;
• sending service notices;
• complying with legal obligations;
• responding to lawful requests;
• establishing, exercising, or defending legal claims;
• protecting EXOFORCE, users, infrastructure, personnel, projects, and third parties;
• administering purchases or subscriptions;
• preventing payment abuse;
• conducting internal business and project administration;
• documentation;
• archival;
• other purposes compatible with or reasonably related to the operation, development, protection, research, or administration of EXOFORCE.

Where permitted, information may be used for more than one purpose.

4. Artificial intelligence development and training

Unless an applicable Service or control states otherwise, EXOFORCE may use AI interactions and associated information for:

• research;
• model development;
• training;
• fine-tuning;
• evaluation;
• benchmarking;
• safety;
• red teaming;
• dataset preparation;
• quality improvement;
• debugging;
• classification;
• synthetic-data work;
• model-behavior analysis;
• development of future systems.

This may involve automated processing and authorized human review.

4.1 Training controls

A Service may provide a setting or mechanism allowing some users to exclude future content from certain training or improvement uses.

Unless that control expressly says otherwise, an opt-out applies only to new content submitted after the opt-out becomes effective.

An opt-out does not automatically apply retroactively.

4.2 Content already in processing or training systems

A later opt-out, deletion request, conversation deletion, account deletion, or termination does not require EXOFORCE to retrieve or remove information that was already, before the relevant request took effect:

• copied;
• transformed;
• tokenized;
• embedded;
• sampled;
• labeled;
• annotated;
• derived;
• aggregated;
• de-identified;
• selected;
• placed in a dataset;
• placed in a benchmark;
• placed in an evaluation set;
• placed in a safety set;
• placed in preprocessing;
• placed in data preparation;
• queued for training;
• included in a fine-tuning pipeline;
• included in a training pipeline;
• included in a training job;
• used in evaluation;
• used in model development;
• used to train or fine-tune a model;
• incorporated into resulting models, weights, statistics, derived artifacts, or systems,

except where mandatory applicable law requires otherwise.

EXOFORCE does not undertake to “untrain,” reconstruct, retrain, or alter a model merely because underlying content is later deleted or a user later opts out, unless required by applicable law.

5. Human access and review

Authorized EXOFORCE personnel, contributors, contractors, or service providers may access information where reasonably necessary for:

• operation;
• support;
• research;
• model development;
• evaluation;
• quality review;
• debugging;
• moderation;
• security;
• abuse investigation;
• legal compliance;
• enforcement;
• administration.

Access controls may vary by Service.

EXOFORCE does not promise that user content is never reviewed by a human.

Where a Service provides a review opt-out, its scope will be described by that Service.

6. Analytics and measurement

EXOFORCE may use internal, self-hosted, third-party, temporary, experimental, or future analytics and measurement systems.

Analytics may be used to understand:

• traffic;
• Service usage;
• user flow;
• performance;
• retention;
• reliability;
• errors;
• model usage;
• feature usage;
• compatibility;
• infrastructure load;
• conversions;
• Service health;
• other operational or development information.

EXOFORCE does not commit to using any specific analytics provider or analytics architecture.

7. Advertising and future business models

EXOFORCE may introduce advertising, sponsored material, recommendations, promotions, measurement technologies, commercial partnerships, or other monetization systems in the future.

Nothing in this Policy is intended as a permanent promise that EXOFORCE will never engage in advertising, measurement, data-sharing arrangements, or practices that may be classified as a “sale,” “sharing,” targeted advertising, or similar activity under a particular jurisdiction's laws.

Where applicable law requires a specific notice, consent mechanism, opt-out, or other control for such a practice, EXOFORCE will provide it as required.

8. Sharing and disclosure

EXOFORCE may disclose or provide information to categories of recipients including:

8.1 Service providers

Providers assisting with:

• hosting;
• compute;
• storage;
• databases;
• networking;
• content delivery;
• security;
• monitoring;
• analytics;
• authentication;
• communications;
• customer support;
• payments;
• AI inference;
• AI model access;
• research;
• development;
• infrastructure;
• other Service operation.

8.2 EXOFORCE personnel and projects

Information may be made available within EXOFORCE where reasonably relevant to:

• operation;
• administration;
• research;
• development;
• support;
• security;
• moderation;
• enforcement;
• project coordination.

8.3 Third-party AI systems

Where a Service uses external model or AI providers, information necessary to perform a request may be transmitted to those providers.

Providers may change over time.

8.4 At your direction

Information may be shared when you:

• connect a third-party service;
• use a tool;
• publish information;
• share content;
• request an integration;
• direct EXOFORCE to transmit information.

8.5 Legal and protective disclosures

EXOFORCE may preserve, access, or disclose information where it reasonably believes this is necessary or appropriate to:

• comply with law;
• respond to valid legal process;
• respond to competent authorities;
• enforce agreements;
• investigate abuse;
• prevent fraud;
• address security incidents;
• protect users;
• protect EXOFORCE;
• protect infrastructure;
• establish or defend legal claims;
• protect rights, property, or safety.

8.6 Restructuring and transactions

Information may be transferred or disclosed in connection with:

• restructuring;
• asset transfers;
• financing;
• acquisitions;
• mergers;
• sales;
• project transfers;
• outsourcing;
• changes of operator;
• insolvency-related processes;
• similar transactions.

9. Public and shared information

Content you intentionally make public or share with other users may be visible, copied, stored, indexed, redistributed, archived, or used by others.

EXOFORCE cannot control information after an independent third party receives or copies it.

Deletion from EXOFORCE does not require third parties to delete independent copies they already possess.

10. Storage and international processing

Information may be stored, transmitted, accessed, cached, backed up, or otherwise processed in any location where EXOFORCE, its infrastructure, its personnel, or its service providers operate.

This may include jurisdictions different from your own.

EXOFORCE may change infrastructure and providers without updating this Policy solely to identify each infrastructure change.

Where applicable law imposes mandatory requirements on international transfers, EXOFORCE will apply required measures.

11. Retention

EXOFORCE may retain information for as long as reasonably necessary, useful, or permitted for the purposes for which it is processed or for related legitimate purposes.

Those purposes may include:

• Service operation;
• account administration;
• continuity;
• security;
• moderation;
• enforcement;
• ban prevention;
• fraud prevention;
• research;
• AI development;
• model training;
• analytics;
• debugging;
• technical history;
• dispute handling;
• legal compliance;
• legal claims;
• audit;
• documentation;
• archival;
• project continuity.

Different categories may have different retention periods.

Some records may be retained for extended or indefinite periods where a continuing purpose exists and applicable law permits that retention.

Examples may include:

• security records;
• moderation records;
• ban records;
• fraud records;
• account-integrity records;
• transaction records;
• operational history;
• research artifacts;
• training datasets;
• derived data;
• legal records;
• archival material.

EXOFORCE does not promise a fixed deletion period unless an applicable Service expressly provides one.

12. Backups, caches, logs, and derived systems

Deletion from an active user-facing system does not necessarily cause immediate deletion from:

• backups;
• caches;
• logs;
• replicated storage;
• disaster-recovery systems;
• archival storage;
• security systems;
• moderation systems;
• analytics;
• datasets;
• derived records;
• research systems;
• AI training systems.

Information may remain in those systems until overwritten, rotated, deleted under applicable processes, or no longer lawfully retained.

13. Deletion

EXOFORCE does not provide a universal contractual right to delete every category of information.

A Service may provide deletion controls.

EXOFORCE may also process deletion requests where applicable law requires it.

Even where information is deleted from an account or active Service, EXOFORCE may retain information where permitted or required for:

• legal obligations;
• security;
• moderation;
• ban enforcement;
• abuse prevention;
• fraud prevention;
• payment records;
• dispute resolution;
• claims;
• auditing;
• backups;
• operational integrity;
• research;
• documentation;
• archival;
• other lawful purposes.

Deletion does not require reversal of completed processing or AI training except where applicable law specifically requires otherwise.

14. Access, correction, export, and other requests

EXOFORCE does not voluntarily create identical privacy rights for every user worldwide.

Your rights depend on applicable law and the circumstances of processing.

Where legally required, rights may include access, correction, deletion, objection, restriction, portability, or other rights.

EXOFORCE may:

• require identity verification;
• request information needed to locate relevant records;
• reject requests that cannot be verified;
• reject or limit requests where an applicable exception exists;
• retain information necessary to document the request and response.

Requests may be sent to privacy@exoforce.org unless a Service provides another process.

15. Automated systems

EXOFORCE may use automated systems to:

• detect abuse;
• detect fraud;
• identify security threats;
• classify content;
• moderate Services;
• prioritize or route requests;
• evaluate model interactions;
• detect suspicious accounts;
• personalize functionality;
• recommend material;
• administer limits;
• support operational decisions.

Human involvement and review may vary.

Where applicable law creates mandatory rights regarding a particular automated decision, those rights remain available as required.

16. Security

EXOFORCE may use technical, organizational, operational, and administrative safeguards intended to protect information.

No security measure is perfect.

EXOFORCE does not guarantee that information, systems, accounts, networks, databases, communications, models, backups, or infrastructure will always be:

• secure;
• private;
• available;
• uninterrupted;
• intact;
• recoverable;
• inaccessible to unauthorized persons.

Users are responsible for protecting their credentials and for considering the sensitivity of information before submitting it.

17. Sensitive and confidential information

Unless a Service specifically requests particular information, you should consider carefully whether submitting sensitive, confidential, proprietary, regulated, or secret information is appropriate.

If you choose to submit such information, EXOFORCE may process it as part of the Service and for purposes described in this Policy, subject to applicable law and any specific Service commitments.

Do not submit third-party confidential information unless you have authority to do so.

18. Children and age-restricted services

Unless a Service expressly states otherwise, EXOFORCE Services are intended for users who are at least 18 years old.

A particular Service may permit users under 18 and establish additional requirements.

Where applicable law requires parental or guardian authorization, age-specific processing, or another requirement, the applicable Service may require it.

EXOFORCE does not represent that every Service is designed for children merely because a Service may permit some users under 18.

19. Third-party services

EXOFORCE Services may link to or integrate with third-party platforms.

Third parties process information under their own terms and privacy policies.

EXOFORCE does not control and, to the maximum extent permitted by law, is not responsible for independent third-party privacy practices.

20. Legal bases and required processing

EXOFORCE processes information on grounds available under applicable law.

Depending on the jurisdiction and processing activity, these may include:

• performance or preparation of an agreement;
• consent;
• legitimate or operational interests where recognized;
• compliance with legal obligations;
• protection of rights and security;
• other grounds permitted by law.

Use of some Services necessarily requires processing of certain information.

If required processing cannot occur, EXOFORCE may be unable to provide the relevant Service.

21. Changes to this policy

EXOFORCE may update this Privacy Policy as Services, technology, processing practices, law, infrastructure, or business needs change.

Notice of material changes may be provided through one or more appropriate EXOFORCE channels.

Unless applicable law requires another procedure, continued use of the affected Services after an updated Policy becomes effective constitutes acknowledgment of the updated Policy and, where legally effective, acceptance of the associated processing terms.

Where applicable law requires consent for a new processing activity, EXOFORCE will seek that consent as required.

22. Relationship to service-specific notices

A Service may provide additional privacy information.

Where a service-specific privacy notice directly conflicts with this Policy regarding that Service, the service-specific notice controls for the conflicting matter.

Otherwise, both apply.

23. Contact

Privacy questions and requests may be sent to:

privacy@exoforce.org

© 2026 EXOFORCE. All rights reserved.