Privacy policy
Explains the current WhiteLyin privacy posture, including Firebase sign-in data, transient tool-file handling, and customer rights requests.
These terms apply to the WhiteLyin public website, the public tools catalogue, and the authenticated WhiteLyin Core customer portal. They describe the current operational baseline for this launch stage in plain language.
This page reflects the current launch posture: controlled onboarding, transient tool-file processing, no public API, and no live self-serve checkout.
The public website explains the company, publishes policies, and introduces the available tool surfaces. WhiteLyin Core is the authenticated customer boundary where current browser-based tool execution and customer workspace access take place.
Public tool pages may describe products, plans, and current capabilities, but they do not replace the authenticated Core flow where access, entitlement checks, and governed execution happen.
Customers may sign in to WhiteLyin Core through supported identity providers. Individual users may receive a personal workspace on first sign-in, while broader tenant and team onboarding can remain a managed process handled directly by WhiteLyin.
Users must keep access credentials secure, provide accurate information where it is requested, and avoid sharing or misusing accounts, sessions, or organization-linked access.
WhiteLyin publishes a supporting acceptable-use page at /acceptable-use for a more specific conduct-focused view, including the current boundaries around tools automation and misuse.
Where WhiteLyin currently supports uploaded PDFs or similar customer-provided files, those files are processed to complete the requested tool action and return an immediate result. WhiteLyin does not offer a persistent public document library or stored result history on this pass.
Users remain responsible for ensuring that submitted material is lawful, that they have the right to process it, and that they do not upload content WhiteLyin cannot lawfully handle.
WhiteLyin may present Free, Pro, Business, and Custom Development plan comparisons on the public site, but public checkout, stored payment methods, and fully automated upgrades are not live in this launch stage. Commercial discussions and enablement remain contact-led.
WhiteLyin may offer manual invoicing, direct consultation, or managed activation for higher plans later, but those steps are arranged through direct contact rather than through an online purchase flow. Public API access also remains deferred.
WhiteLyin may limit, suspend, or terminate access where there is a security risk, suspected abuse, non-payment, a legal or regulatory reason, or another reasonable need to protect the service, users, or business.
WhiteLyin may also take proportionate operational steps such as rate limiting, workflow restrictions, or removal of specific material before broader service suspension is needed.
WhiteLyin retains rights in its software, content, branding, and service materials, except where rights are expressly granted or required by law. The service is launched on a controlled basis and may change as WhiteLyin improves reliability, onboarding, and commercial handling.
To the extent permitted by law, WhiteLyin aims to provide useful services without promising uninterrupted availability, fitness for every use case, or support for workflows that remain explicitly deferred in the current pass.
This terms page is the umbrella entry point for the public website, WhiteLyin Core customer portal, and the currently published tools surfaces.
Explains the current WhiteLyin privacy posture, including Firebase sign-in data, transient tool-file handling, and customer rights requests.
Sets out the conduct and access-misuse rules that support this umbrella terms page, including the boundary against batch or abusive tool usage.
Provides the broader public policy hub and the current operating notes for onboarding, tools, and launch-stage commercial posture.
WhiteLyin may publish narrower product supplements later if a live surface introduces materially different processing, billing, or sector-specific obligations. Until then, these terms remain the umbrella baseline.