Privacy

Privacy Policy

Last updated: March 18, 2026

This Privacy Policy describes how PrySai Lab and its affiliated operations for prysai.com collect, use, disclose, store, and protect information across websites, integrations, and distributed platform channels. This version is written for cross-platform publication while preserving a consistent rights-and-responsibility baseline for users and for PrySai Lab.

Scope and Service Coverage

This policy applies to interactions with PrySai Lab touchpoints, including official pages, policy pages, support channels, profile pages on third-party platforms, model-related publishing pages, and integration endpoints that are controlled by PrySai Lab.

• Primary domain content and functional pages operated on prysai.com.
• Official external pages used for communication, distribution, or collaboration.
• Operational endpoints and security mechanisms needed for service integrity.
• Business and support communications through approved channels.

Data Controller and Processing Role

PrySai Lab acts as controller for website-level interactions and service operations under its control. For third-party platform accounts, the platform operator may be the independent controller for account-level processing performed on its own systems.

Cross-Platform Distributio

Equivalent privacy commitments apply where this policy is referenced or mirrored across managed channels. If local law requires stricter terms, those legal obligations apply in addition to this policy.

Information We Collect

• Technical telemetry: IP address, browser and device metadata, request path, referrer, and timing information.
• Security and operations logs: anti-abuse events, reliability diagnostics, and monitoring signals.
• Communication records: information submitted through email or support channels.
• Integration metadata: callback and endpoint identifiers used for continuity and verification.
• Aggregated performance indicators: non-personal trend metrics used for planning and quality control.

Sources of Informatio

Data may be collected directly from user interaction, generated by service infrastructure, or received from trusted processors and platform partners where operationally required.

How and Why We Use Informatio

• Provide and maintain service availability.
• Defend infrastructure against abuse, fraud, and unauthorized access.
• Respond to inquiries, support requests, and legal rights requests.
• Improve reliability, latency, and operational quality.
• Retain records where legally required for compliance and dispute handling.

Legal Bases for Processing

Depending on jurisdiction, processing may rely on legitimate interests, contractual necessity, legal obligations, and consent where non-essential technologies or communications require explicit permission.

Model, Content, and Dataset Handling

PrySai Lab may process prompts, metadata, and related artifacts to run model workflows, quality controls, and service safeguards. Rights handling follows applicable law, platform policies, and project-specific agreements where signed.

NoobAI Usage and Commercial Terms

For NoobAI-related workflows, PrySai Lab may process minimum necessary prompt and output metadata for quality assurance, abuse prevention, and support continuity. Commercial use of resulting assets depends on upstream model licenses, platform rules, and applicable law.

• PrySai Lab does not grant rights it does not control under third-party licenses.
• Users are responsible for checking destination-platform terms before commercial publication.
• Detailed terms: NoobAI Commercial Policy and General Commercial Use Policy.

Strict Model-Specific Commercial Controls

To keep enforcement consistent across model tracks, PrySai Lab applies a strict baseline to Illustrious, NoobAI, Pony, FLUX, Z-Image, and LLM workflows when outputs are used in public or commercial contexts.

Illustrious

• Commercial publication requires a pre-release check against platform rules, model card limits, and destination terms.
• High-risk categories (personality misuse, deceptive claims, rights-sensitive assets) require manual review before release.
• Official references: Civitai Terms of Service, Civitai Rules.

NoobAI

• NoobAI outputs follow the same strict gate and rights-validation workflow used for all active commercial tracks.
• Users must confirm redistribution and monetization permissions before launch in any external marketplace.
• Detailed terms: NoobAI Commercial Policy, General Commercial Use Policy.

Pony

• Pony outputs are subject to the same release controls as Illustrious and NoobAI for rights and misuse screening.
• Commercial campaigns must retain provenance notes and source-policy references for compliance review.
• Official references: Civitai Terms of Service, Civitai Rules.

FLUX

• FLUX track use must comply with upstream model-card limits and applicable provider restrictions.
• Deployment decisions involving paid distribution require a documented policy check and retention of approval records.
• Official references: FLUX.1-dev model card, Black Forest Labs Terms.

Z-Image

• Z-Image pipelines must pass format-integrity and rights checks before external publication or archival export.
• Where image payloads include embedded metadata, handling follows least-data and purpose-limitation controls.
• Official references: W3C PNG Specification, JPEG XL (ISO/IEC 18181).

LLM

• LLM-assisted outputs are reviewed for policy risk, factual sensitivity, and disallowed content before public distribution.
• Commercial usage requires adherence to provider acceptable-use and content policy constraints.
• Official references: OpenAI Usage Policies, Anthropic Acceptable Use Policy.

Model-Specific Policy Index

The following pages define usage boundaries for active model and LLM tracks currently used by PrySai Lab. Users should review both project pages and upstream platform policies before commercial deployment.

• Illustrious Usage Policy (external baseline: Civitai ToS)
• NoobAI Commercial Policy (external baseline: Civitai Rules)
• Pony Usage Policy (external baseline: Civitai ToS)
• FLUX Usage Policy (external baseline: FLUX model card)
• Z-Image Usage Policy (external reference: W3C PNG spec)
• LLM Usage Policy (external baselines: OpenAI, Anthropic)

Cookies and Similar Technologies

Cookies, local storage, and related mechanisms may be used for core functionality, security controls, and performance diagnostics. Non-essential processing follows applicable consent standards.

Sharing, Processors, and Partners

PrySai Lab does not sell personal data. Data may be shared with infrastructure and professional service providers only where operationally necessary and under binding confidentiality and security obligations.

International Transfers

Because services and vendors may operate globally, data may be processed outside a user’s jurisdiction. Appropriate safeguards are applied where legally required.

Data Retention and Deletio

Retention periods depend on purpose, legal obligations, and security requirements. Data is retained only for as long as reasonably necessary and then deleted, anonymized, or de-identified where appropriate.

Security Controls

Controls include access governance, least-privilege principles, transport protection, environment hardening, operational monitoring, and periodic control improvements.

Incident Response and Breach Handling

Security incidents are managed through documented procedures: detection, containment, impact assessment, remediation, and post-incident review. Notifications are made where law requires.

User Rights and Request Process

Depending on local law, users may request access, correction, deletion, portability, restriction, or objection. We may request proportionate verification before acting on a rights request.

Request Handling Timeline

Requests are reviewed in reasonable timeframes based on jurisdiction, complexity, and identity verification needs. Where extension is permitted, users are informed with reasoned notice.

Law Enforcement and Legal Requests

Data may be disclosed when required by applicable law, valid legal process, or enforceable regulatory demand. PrySai Lab reviews legal requests for scope, validity, and proportionality before disclosure.

Business Transition and Asset Transfer

If all or part of operations are reorganized, merged, or transferred, relevant data may be transferred as part of lawful business continuity with equivalent protection obligations.

Children and Age-Restricted Use

Services are not directed to children below applicable legal thresholds. If prohibited collection is identified, reasonable removal steps are taken.

Automated Processing and Abuse Preventio

Automated systems may support anti-spam, anomaly detection, and fraud prevention. Significant decisions requiring additional safeguards are handled with enhanced review where applicable.

Third-Party Platforms and External Links

External services and partner platforms operate under their own terms. Users should review those policies directly.

Copyright, Data Access, and Platform Rights

Original content, brand assets, code expressions, and service structure are protected by applicable intellectual property and competition law.

• Unauthorized scraping, mirror copying, bulk extraction, or commercial misuse is prohibited.
• Machine access must remain lawful and respect technical boundaries and policy constraints.
• PrySai Lab may enforce rights through access controls, takedown actions, and legal remedies.

Complaints and Supervisory Contacts

Where law provides supervisory authority rights, users may file complaints with competent regulators. We encourage contacting PrySai Lab first for fast operational resolution where possible.

Accessibility and Policy Format

This policy is maintained in clear structured sections for readability and cross-platform consistency. Alternative format requests can be made through official contact channels.

Compliance, Audits, and Regulatory Cooperatio

PrySai Lab may retain required records and cooperate with lawful regulatory requests. Controls and policy text are periodically reviewed for legal and operational alignment.

Policy Updates

This policy may be revised to reflect legal, technical, or business changes. Material updates take effect upon publication unless a different date is required by law.

Contact

For privacy, rights, legal, or infringement-related matters, contact: uuzzrm@gmail.com