This policy sets out the refund and cancellation position for the current website service. Applies to live
paid purchases of the current website service. Mandatory legal rights continue to apply. Effective date: May
7, 2026.
Scope
This policy applies to paid purchases made through a live SentinelLolge checkout flow for the website
service. It does not convert non-live demonstrations, indicative pricing, development-only billing
paths, or internal test flows into completed consumer transactions.
General rule
Except where required by applicable law, fees are non-refundable once paid. Where the service provides
digital access or digital features promptly after purchase, change-of-mind refunds are generally not
offered after that access has started.
Consumer rights preserved
Nothing in this policy limits any statutory remedy or non-waivable consumer right that applies under
governing law. That includes rights that may arise where the service is not provided, is materially
defective or deficient, is materially not as described at the time of purchase, is billed in error, or
is subject to a mandatory cancellation, withdrawal, or cooling-off right.
Immediate access and cancellation rights
If immediate access to digital services is provided after purchase, any otherwise applicable
cancellation or withdrawal right may be limited only where the live checkout flow captures the consent
and acknowledgements required by applicable law. If those disclosures are not properly presented,
SentinelLolge does not assume that any such right has been waived.
Cancellation and renewals
Where recurring billing is enabled, the cancellation and renewal terms shown in the live checkout flow
or account billing surface govern how future renewals stop. Unless the applicable billing flow states
otherwise, cancellation prevents future renewal and does not ordinarily reverse access already provided
for the current paid term.
Billing errors
If a transaction is duplicated, billed incorrectly, or associated with the wrong account or plan state,
SentinelLolge may investigate and, where appropriate, correct the billing outcome or work with the
relevant payment environment to address the issue. SentinelLolge may request enough information to
verify the transaction and the account involved before taking action.
Requests and review
Refund, billing, and cancellation requests should be sent using the contact details on the contact
page. To support review, provide the account identifier or email used for the purchase, the transaction
date, the amount charged, and a concise explanation of the issue.
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
Protect files before sharing them.
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.
Standard browser-first path
Protect the file locally in your browser and export a self-contained unlock experience that can travel
with the document.
Stricter controlled delivery
When needed, pair the handoff with expiry, read-only access, unlock limits, or recipient-aware checks.
Designed for real business files
Use it for PDFs, contracts, invoices, proposals, reports, archives, and other sensitive documents that
should not become raw open attachments.
Explore SentinelLolge guides for secure file delivery, PDF protection, intended-recipient delivery, file
expiry links, and protecting files before sharing.
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.
Protect before sharing
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.
Browser-first workflow
The standard flow keeps original file contents local in the browser while producing a protected unlock
package that recipients can open in modern browsers.
Controlled delivery paths
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.
Secure file delivery when you care about the handoff itself, not
just encryption at rest.
File expiry links when the document should only remain available during
a defined review window.
Guide / Secure sharing
Protect files before sharing them
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.
Why it matters
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.
How SentinelLolge helps
The product prepares a protected unlock experience first, then lets you share that result instead of
the original raw file.
When to use it
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.
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.
Good use cases
Protect invoices, pricing sheets, board packs, signed agreements, and review copies before sending them
outside your own team.
Preview-friendly delivery
PDF-based workflows fit well with preview-oriented unlock experiences where the chosen rules allow it,
making the protected handoff easier for recipients.
Expiry and access rules
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.
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.
Delivery-focused protection
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.
Standard and strict paths
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.
Fits real business handoffs
This route is useful for investor materials, customer reports, legal documents, vendor exchanges,
design handoffs, and financial records that need stronger control during delivery.
Intended-recipient delivery and stricter access checks
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.
Why it matters
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.
What this helps with
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.
Practical limit
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.
File expiry links and time-limited document access
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.
Reduce long-tail exposure
Expiry helps lower the chance that an old shared document stays accessible indefinitely after the
reason for sharing has ended.
Good fits
Use it for short review cycles, temporary customer approvals, expiring invoice access, diligence
material, and one-time protected document delivery.
Works with stricter rules
Pair time-limited access with unlock limits, read-only behavior, or recipient-aware controls when the
document sensitivity requires a tighter handoff.
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.
Safer invoice delivery
Share a protected delivery asset instead of a raw invoice attachment that can be forwarded or stored
indefinitely.
Fits finance review windows
Use expiry-aware delivery when invoices, statements, or billing packs only need to stay available
during a short approval or payment cycle.
Useful for client-facing billing
This route fits client invoices, payment summaries, credit notes, and finance records that should stay
protected after they leave your team.
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.
Built for email-heavy reviews
Use a protected delivery path instead of sending the raw agreement first and hoping the thread stays
private.
Supports recipient-aware delivery
Stricter workflows can help align access with a named reviewer, signer, or customer contact when a
contract should not be broadly opened.
Useful for agreements and renewals
Use it for MSAs, vendor contracts, employment agreements, renewal terms, and other legal files that
need tighter handoff control.
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.
Designed for sensitive files
Use it for legal documents, finance packs, customer records, board materials, credentials, and private
reports.
Works from simple to strict
Start with browser-first protected delivery, then add expiry, unlock rules, or recipient-aware checks
for higher-risk handoffs.
Keeps protection close to the asset
The workflow is built so confidentiality travels with the document instead of depending entirely on
where the recipient stores it.
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.
Fits recurring client handoffs
Use it for billing documents, onboarding packs, monthly reports, signed paperwork, and
customer-specific approvals.
Good for expiring access
Pair client delivery with expiry when access should end after the review, approval, or payment window
closes.
Supports named-recipient delivery
Use stricter controlled access when a particular customer contact or reviewer should be the one opening
the protected file.