Firebase-backed sign-in and account data
Email address, identity-provider subject data, and WhiteLyin Core session records are used to authenticate customers, create or update user records, and issue customer access.
Privacy notice
WhiteLyin uses this notice to explain how personal and workspace-linked information is handled across the public site, WhiteLyin Core onboarding, and the current tools launch. It is written to match the runtime that exists today.
This launch uses account, session, security, advertising, and tracking data where needed to run WhiteLyin Core and the current PDF tools flow. Persistent document storage is not part of this pass, and paid Core subscriptions remove ad surfaces from the premium workspace lane.
On this page
Data categories
WhiteLyin keeps this section structured so visitors can see the main categories that matter for the current launch without reading through product fiction or future-state assumptions.
Workspace, membership, and entitlement records
WhiteLyin stores the minimum workspace, membership, and product-access information needed to activate customers on WhiteLyin Core and govern the current tools experience.
Contact details and support requests
Names, email addresses, and support context may be used to answer enquiries, manage onboarding conversations, and support customers who use the live tools.
Uploaded PDFs and processing metadata
Uploaded PDFs and request metadata may be handled to complete a tool action such as PDF Merge, PDF Split, or PDF Compress. WhiteLyin does not present a stored public document library in this pass.
IP, browser, device, and session information
Device, browser, session, and network information may be used for security review, abuse prevention, diagnostics, and basic runtime reliability monitoring.
How data is used
WhiteLyin uses data to authenticate customers, activate workspaces, run the current tools flow, answer support requests, protect the service, investigate abuse, maintain a reliable runtime, and support ad-funded PDF surfaces where they are enabled.
That can include measurement, network advertising, sponsorship delivery, cookie-backed preferences, and provider or customer-configured tracking pixels/scripts on the public PDF lane and relevant Core PDF pages. Paid Core subscriptions remove those ad surfaces on the premium workspace lane.
Sharing and service providers
WhiteLyin may work with infrastructure providers, authentication providers, advertising providers, sponsorship partners, and messaging or support services where needed to operate the public site and WhiteLyin Core. Firebase-backed authentication is part of the current customer sign-in posture.
The current advertising abstraction is provider-driven and can support AdSense-first, Media.net, Microsoft Monetize, house sponsorships, customer-configured image/script pixels, and related embed technologies where they are enabled by runtime configuration.
Uploaded files are processed transiently for the current tool request.
When a customer uploads PDFs to WhiteLyin Core, WhiteLyin processes those files to produce the requested result and return it immediately to the current browser session. WhiteLyin does not offer persistent document storage or stored tool-result history in this launch stage.
WhiteLyin may retain limited request metadata, diagnostics, or audit evidence where needed for support, abuse prevention, or operational accountability.
Retention
WhiteLyin retains account, workspace, support, and security records for as long as they are needed for legitimate operational, legal, or support purposes. Uploaded tool files are not meant to become a standing document archive on this pass.
WhiteLyin may refine retention schedules as the service matures, but the current baseline is to minimise stored customer file content while keeping the records required to run and protect the service.
Security
WhiteLyin applies technical and operational controls intended to protect access, data handling, tool execution, and runtime integrity. Current controls include session handling, access checks, rate limiting, and operator-visible diagnostics.
Cookies
WhiteLyin may use session, security, measurement, personalization, advertising, and related tracking cookies or similar technologies where needed for service quality, fraud prevention, monetization, runtime stability, and configured campaign measurement.
The cookie popup on the relevant public and Core PDF surfaces allows users to switch from the default ad/tracking posture to non-personalized or necessary-only modes. For a dedicated cookie and tracking view, see /cookie-notice.
User rights
Access and confirmation
WhiteLyin aims to support reasonable requests to understand whether relevant personal information is being processed and to obtain access where applicable.
Correction and objection
WhiteLyin expects to support requests to correct inaccurate information and to consider objections where POPIA-oriented rights apply.
Consent and complaints
Where consent is part of the legal basis, WhiteLyin expects to respect withdrawal requests where possible, subject to lawful and operational limits, and to receive complaints through the published contact path.
Contact details, related notices, and policy changes
Questions about this notice or privacy requests can be sent to hello@whitelyin.co.za. General support remains available at help@whitelyin.co.za.
Cookie and tracking notice
Sets out the broader cookie, session, and operational-tracking posture for the WhiteLyin surface.
PDF tools handling posture
The public PDF tools page explains the current anonymous-primary surface while WhiteLyin Core remains the premium workspace lane for signed-in execution.
WhiteLyin may revise this page as the service matures, as additional live products are introduced, or where legal obligations require clearer or narrower disclosures.