Security, Built-In
Privacy Policy
This policy governs how SentinelLolge handles personal information in connection with the current website service. Applies to the public website service, including account-linked features and paid-plan flows where enabled. Effective date: May 7, 2026.
This policy applies to personal information SentinelLolge collects, receives, stores, uses, discloses, or otherwise handles in connection with the website service. It does not govern third-party sites, services, or payment environments except to the extent SentinelLolge directs information into those environments as part of a service workflow.
Depending on how you use the service, SentinelLolge may process account and profile details, contact details, authentication information, payment and billing records, customer support communications, device and browser information, usage and event data, and settings or metadata associated with protected-sharing workflows. SentinelLolge may also process customer-provided content-related metadata where that is necessary to operate access controls, support account features, or maintain service records.
Certain website workflows are designed so protected file contents are handled locally within the browser rather than routinely uploaded as raw source content to the service. Even where content remains local, related metadata, event data, account state, or control information may still be processed by SentinelLolge where needed to provide account-linked features, security controls, billing state, or service operations.
SentinelLolge may use personal information to provide and operate the service, authenticate users, maintain account state, deliver paid access, administer sharing controls, prevent abuse, enforce service policies, maintain security, respond to requests, provide support, measure product usage, improve reliability, comply with legal obligations, and protect the rights, safety, or integrity of SentinelLolge, its users, and third parties.
SentinelLolge may disclose personal information to service providers, infrastructure providers, analytics providers, identity providers, payment providers, professional advisers, corporate transaction participants, or public authorities where reasonably necessary for service delivery, security, billing, legal compliance, or protection of rights.
The website may use cookies, local browser storage, identifiers, and similar technologies to maintain sessions, support login flows, preserve preferences, protect account access, measure usage, and support service reliability. Disabling those mechanisms may affect how certain workflows operate or whether some account-linked features function correctly.
SentinelLolge may retain personal information for as long as reasonably necessary to provide the service, maintain account relationships, resolve disputes, enforce terms, preserve security records, comply with law, and maintain appropriate business and operational records. Different categories of information may be retained for different periods depending on their purpose and the obligations attached to them.
SentinelLolge applies technical and organizational measures intended to protect personal information against unauthorized access, misuse, loss, or disclosure. No internet-connected or browser-based environment can be made completely risk-free.
Subject to applicable law and the nature of the relationship, you may have rights to access, correct, delete, export, object to, or restrict certain processing of personal information. SentinelLolge may need to verify a request and may decline or limit a request where permitted by law, where the request affects the rights of others, or where the information must be retained for security, legal, or operational reasons.
The website service may be used across jurisdictions, and personal information may be handled in countries other than the one from which you access the service, subject to applicable legal requirements. SentinelLolge may update this policy from time to time to reflect changes in the service, legal requirements, or operational practices. The updated version becomes effective when published unless a different date is stated.
Questions, requests, or complaints relating to this policy may be directed through the contact details on the contact page.
This HTML exists as a branded search-friendly fallback while the Flutter app loads. The visible structure preserves current public content for crawlers without depending only on Flutter-rendered text nodes, and it now includes keyword-targeted guide routes as dedicated HTML templates.
Protect workspace
SentinelLolge is built around the moment a file leaves you. Use the protect workflow to prepare a browser-based protected delivery asset before the file is emailed, uploaded, or handed to someone else.
Protect the file locally in your browser and export a self-contained unlock experience that can travel with the document.
When needed, pair the handoff with expiry, read-only access, unlock limits, or recipient-aware checks.
Use it for PDFs, contracts, invoices, proposals, reports, archives, and other sensitive documents that should not become raw open attachments.
Guides hub
Explore SentinelLolge guides for secure file delivery, PDF protection, intended-recipient delivery, file expiry links, and protecting files before sharing.
Guide / Product overview
SentinelLolge is a browser-first file protection product from Lolge Labs for people who need to protect files before sharing them. It is built around the delivery moment: before a file is emailed, forwarded, copied, or sent outside the system where it was originally stored.
SentinelLolge helps the sender prepare a protected delivery experience first, so the protection can move with the file instead of depending on a separate portal later.
The standard flow keeps original file contents local in the browser while producing a protected unlock package that recipients can open in modern browsers.
When a use case needs more than a simple protected handoff, stricter workflows can add expiry, unlock limits, read-only behavior, and recipient-aware access checks.
Related guides
Guide / Secure sharing
If a file matters after it leaves your inbox, protect it before sharing it. SentinelLolge is designed for contracts, spreadsheets, reports, source archives, customer documents, and other private assets that should not become unprotected raw attachments after download.
Once a raw file is sent, the sender usually loses control over forwarding, copying, or reuse. Protecting the file before sharing helps keep confidentiality attached to the delivery asset itself.
The product prepares a protected unlock experience first, then lets you share that result instead of the original raw file.
Use this route when the file contains sensitive business information, client records, internal review notes, payment material, or any document that should not circulate freely after handoff.
Guide / PDF protection
PDFs are one of the most common formats for invoices, proposals, agreements, policies, and customer documents. SentinelLolge helps protect a PDF before sharing it so the sender is not relying on the recipient to handle the raw file securely afterward.
Protect invoices, pricing sheets, board packs, signed agreements, and review copies before sending them outside your own team.
PDF-based workflows fit well with preview-oriented unlock experiences where the chosen rules allow it, making the protected handoff easier for recipients.
For stricter workflows, you can pair the protected PDF delivery path with expiry schedules, unlock limits, or read-only behavior before the document is sent.
Guide / Delivery control
Secure file delivery is about more than storing a file safely. It is about how the document is handed off, what the recipient sees, what rules travel with the file, and how much control the sender keeps after sharing. SentinelLolge is built around that delivery moment.
The workflow protects the document before it leaves you, so the handoff itself is controlled instead of depending only on the security of the destination system.
Use the standard browser-first delivery flow for offline-friendly protection, or choose stricter delivery controls when you need expiry, unlock rules, or recipient-aware access steps.
This route is useful for investor materials, customer reports, legal documents, vendor exchanges, design handoffs, and financial records that need stronger control during delivery.
Guide / Intended-recipient delivery
Some protected files should only be opened by the intended person, not simply anyone who receives the package. SentinelLolge supports stricter delivery workflows for senders who want stronger intended-recipient control around sensitive handoffs.
Confidential files are often sent to a named reviewer, signer, or customer contact, yet plain attachments are easy to forward. Recipient-aware controls help align document access with the intended audience.
Use it for customer-specific reports, approval packets, renewal terms, employee paperwork, and procurement documents where a plain password on a raw file is not enough.
The goal is stronger delivery discipline and intended-recipient control. It should not be treated as a guarantee against every forwarding, capture, or endpoint-side risk.
Guide / Expiry controls
Some documents should only stay available during a review window, an approval deadline, or a short-lived client exchange. SentinelLolge supports protected delivery paths where expiry is part of the file-sharing workflow instead of an afterthought.
Expiry helps lower the chance that an old shared document stays accessible indefinitely after the reason for sharing has ended.
Use it for short review cycles, temporary customer approvals, expiring invoice access, diligence material, and one-time protected document delivery.
Pair time-limited access with unlock limits, read-only behavior, or recipient-aware controls when the document sensitivity requires a tighter handoff.
Finance workflow
Invoices often include customer details, payment information, and approval context that should not remain exposed after delivery. SentinelLolge helps teams protect invoices before sending them so the invoice handoff stays controlled.
Share a protected delivery asset instead of a raw invoice attachment that can be forwarded or stored indefinitely.
Use expiry-aware delivery when invoices, statements, or billing packs only need to stay available during a short approval or payment cycle.
This route fits client invoices, payment summaries, credit notes, and finance records that should stay protected after they leave your team.
Legal workflow
Contracts move through review threads, approvals, and external inboxes where plain attachments are easy to forward. SentinelLolge helps legal and commercial teams protect contracts before emailing them so the agreement stays controlled after the send.
Use a protected delivery path instead of sending the raw agreement first and hoping the thread stays private.
Stricter workflows can help align access with a named reviewer, signer, or customer contact when a contract should not be broadly opened.
Use it for MSAs, vendor contracts, employment agreements, renewal terms, and other legal files that need tighter handoff control.
Confidential sharing
Confidential files should stay controlled after the send, not just while they are stored internally. SentinelLolge helps teams share confidential documents securely by protecting the file before it leaves the sender.
Use it for legal documents, finance packs, customer records, board materials, credentials, and private reports.
Start with browser-first protected delivery, then add expiry, unlock rules, or recipient-aware checks for higher-risk handoffs.
The workflow is built so confidentiality travels with the document instead of depending entirely on where the recipient stores it.
Client delivery
Client documents often include exactly the material that should stay controlled after delivery: invoices, reports, contracts, approvals, and private records. SentinelLolge helps you send secure client files without relying on raw attachments alone.
Use it for billing documents, onboarding packs, monthly reports, signed paperwork, and customer-specific approvals.
Pair client delivery with expiry when access should end after the review, approval, or payment window closes.
Use stricter controlled access when a particular customer contact or reviewer should be the one opening the protected file.