Turn a file into a protected shareable asset designed to stay protected as it moves. The standard protection
flow keeps file contents local in your browser and produces a self-contained HTML unlock file that can work
offline, while stricter account-linked workflows add backend-enforced controls when you need them.
Standard workflow
Protect — choose a file and encrypt it with AES-256-GCM plus Argon2id key
derivation.
Share — download a self-unlocking HTML file that recipients can open in modern
browsers.
Stay in control — keep file contents local in the standard flow, or use stricter
account-linked controls where enabled.
Current public posture
Base can be used without an account, while signed-in accounts unlock GateSeal vault access and paid
upgrades
No file contents are uploaded in the standard protection flow
Strict exports may register policy and unlock metadata with the backend for expiry, incorrect
attempts limits, and tracking, but not the file contents themselves
Recipients can open the protected HTML in modern Chrome, Safari, Firefox, and Edge without apps,
plugins, or recipient accounts
What the public product is for
SentinelLolge is built for contracts, financials, API keys, private documents, code, media, and other
files that need confidentiality to stay attached to the asset even as it moves across inboxes, drives,
and offline handoffs.
Guides and use cases
Explore the routes SentinelLolge can rank for.
These public pages explain what SentinelLolge is, which document-sharing problems it solves, and which
workflow to choose for contracts, invoices, confidential files, recipient checks, and time-limited delivery.
Start with self-protected sharing for free. Upgrade when you need more control after the file leaves you:
larger exports, stronger rules, customization, and team accountability.
Base
For account-free protected sharing with offline unlocks built into the file, plus optional GateSeal on
signed-in accounts.
Unlimited AES-256-GCM + Argon2id file encryption
5 MB anonymous export allowance and 10 MB signed-in Base allowance
Offline self-unlocking HTML with no recipient account needed
GateSeal vault access on signed-in accounts with timed entry limits
Plus
For strict protected sends that need backend-tracked rules, richer recipient controls, and more room to
work.
512 MB protected exports plus bulk encryption
Strict exports with tracked incorrect attempts, max opens, and expiries
Strict-backed read-only, self-destruct, expiry, and password hint controls
Connected verification, separate password QR export, themes, notes, presets, and expanded GateSeal
access
Business
For teams that need policy controls, compliance workflows, and consistent protected sharing at scale.
Up to 512 MB with chunked encryption and batch re-encryption
Strict exports plus admin dashboards, alerts, and department policies
For high-trust environments that need advanced cryptography, stealth controls, and secure delivery.
1 GB+ file support and the most advanced strict export workflows
Keyfiles, hardware keys, biometrics, and composable unlock constraints
White-label SDK, custom domains, and enterprise integrations
Availability today
Today, Base is available and Plus is the only paid plan live. Business and Pro remain planned future
tiers and are not available for purchase yet.
Account expectations
No. You can use Base without an account. Creating an account raises the Base limit, unlocks GateSeal
vault access, and lets you upgrade to Plus when you need larger exports or stricter controls.
Contact
Contact for support, billing, privacy, and legal notices.
Use-case guidance, support requests, privacy questions, refund matters, and legal notices for the current
website service.
Use-case Guidance
If you need guidance on fit, workflow, or document type, outline the use case and we will respond
directly.
Billing & refund issues
If a charge is incorrect, duplicated, or tied to the wrong plan state, include the account email, date,
amount, and the issue.
Privacy & legal
Privacy, compliance, subpoena, or legal notice enquiries may be sent here. Referencing the relevant
public page will help with triage.
How to write in
If something broke, include browser details and the shortest reproducible description you can. If the
enquiry concerns privacy, refunds, paid access, or legal process, state that clearly in the opening
line.
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.
Information covered by this policy
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.
Information we may collect
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.
Information that may remain local
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.
How we use personal information
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.
How we disclose information
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.
Cookies, local storage, and similar technologies
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.
Retention
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.
Security
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.
Your choices and requests
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.
International use and updates
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.
Contact
Questions, requests, or complaints relating to this policy may be directed through the contact details
on the contact page.
Terms
Terms of use for the current website service.
These terms govern access to and use of the current SentinelLolge website service. Applies to the public
website service. Separate business terms apply only where agreed in writing. Effective date: May 7, 2026.
Service scope
SentinelLolge currently offers a browser-based service for file protection, controlled sharing
workflows, and related account-linked features. References to future plans, organization workflows, or
expanded packaging are informational only unless they are expressly made available through a live
purchasing or contracting path.
Eligibility and account use
You are responsible for ensuring that your use of the service is lawful and appropriate for your
circumstances. If the service requires an account for a given workflow, you must provide current and
accurate account information and keep your credentials secure. You are responsible for activity carried
out through your account unless the activity results from SentinelLolge's own fault or an unauthorized
compromise outside your reasonable control.
Permitted use and customer responsibilities
You may use the service only for lawful purposes and only in relation to content and workflows you are
entitled to handle. You remain responsible for the files you protect, the recipients with whom you share
them, the passwords or access material you create, and any confidentiality, employment, privacy,
export-control, consumer-protection, or sector-specific obligations that apply to your own use case.
Compatibility and operational limits
The service is designed for modern browser environments, but identical behavior is not guaranteed
across all devices, browsers, operating systems, network conditions, or local security settings. Preview
behavior, local file handling, media rendering, and large-file performance may vary. For a sensitive,
business-critical, or time-dependent workflow, test on the intended recipient environment before relying
on it.
Security model and practical limits
SentinelLolge is designed to improve confidentiality and control, but no browser-delivered or
account-linked system can eliminate all security risk. Different workflows rely on different trust
assumptions. Assess whether the service is appropriate for your own risk model rather than treating any
feature description as a guarantee against every recipient-side, browser-side, or endpoint-side threat.
Availability, changes, and suspension
SentinelLolge may modify, suspend, limit, or discontinue features where reasonably necessary for
product development, legal compliance, abuse prevention, security, commercial changes, or operational
reasons. SentinelLolge may also suspend access where reasonably necessary to investigate misuse, protect
the service, comply with legal obligations, or limit harm to users or third parties.
Fees, paid access, and renewals
Where paid plans or paid features are offered through a live checkout flow, the pricing, billing
cadence, taxes, and renewal terms shown at the time of purchase form part of the transaction. Unless the
live billing flow states otherwise, paid access is provided for the purchased term and renewals, if any,
are governed by the cancellation and billing information presented in that live flow or in the relevant
account billing surface.
GateSeal retention and plan limits
Account-linked GateSeal availability, storage limits, retention windows, and permanent-entry options
vary by plan and may change if the live product surface is updated. On the current Base plan, GateSeal
entries are time-limited and currently expire 30 days after creation. Base-plan GateSeal entries are not
permanent, may become unavailable automatically once expired, and may be removed during normal service
cleanup after expiry.
Refunds and mandatory consumer rights
Except where required by applicable law, fees are non-refundable once paid. Nothing in these terms
excludes any non-waivable consumer right or statutory remedy that applies under governing law. If a
separate refund or cancellation policy is published, it forms part of the overall purchase framework
together with these terms and the disclosures shown in the live purchase flow.
Intellectual property and service materials
SentinelLolge retains all rights in the service, including the website, branding, interface elements,
and service materials, except for rights in customer content that remain with the applicable user or
rights holder. These terms do not transfer ownership of the service or create any implied license beyond
the limited right to use the service in accordance with these terms.
Customer content and legal compliance
You represent that you have the necessary rights to use, process, share, and protect the content you
place into the service. SentinelLolge does not assume responsibility for the legality, accuracy, or
underlying rights status of customer content. Nothing in the service constitutes legal advice on how
regulated, proprietary, confidential, or personal information may lawfully be handled.
Limitation of assurances
To the maximum extent permitted by applicable law, the service is provided on an as-available basis and
SentinelLolge does not promise uninterrupted operation, universal compatibility, or suitability for
every purpose. Nothing in this section excludes liability that cannot lawfully be excluded or limited.
Contact
Questions about these terms, notices concerning the website service, and requests relating to legal or
billing matters may be sent using the contact details on the contact page.
Refund policy
Refund and cancellation policy.
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.
Security overview
Security overview for the current website service.
This overview states the current security position of the SentinelLolge website service. Informational only.
Not a warranty, audit report, or certification statement. Effective date: May 7, 2026.
General security approach
SentinelLolge applies technical and organizational measures intended to support confidentiality,
integrity, and controlled access in the ordinary operation of the website service. The service uses a
browser-first protection model together with account-linked controls for certain workflows. The
protection boundary depends on the feature used and the environment in which that feature is used.
Standard file-protection workflows
In the standard website workflow, protected file handling is designed to occur within the browser
rather than by routinely transmitting raw source file contents into the service for ordinary storage.
That architecture reduces certain categories of hosted-content exposure, but it does not eliminate all
operational, browser, endpoint, or recipient-side risk.
Managed access-control workflows
Some workflows rely on service-side account, access-control, or enforcement mechanisms in addition to
local browser processing. Those workflows provide stronger control than a purely self-contained export,
but they do not guarantee prevention of every hostile recipient action, compromised endpoint, or local
manipulation scenario.
Account security
Authenticated features may use account, session, and access-management controls intended to reduce
unauthorized use and maintain service integrity. Those controls support account discipline but do not
replace the need for strong credentials, careful device hygiene, and sound customer-side security
practices.
Operational limits
Security outcomes depend in part on browser behavior, device integrity, recipient conduct, network
conditions, and the way a customer chooses to use the service. No online service can guarantee
uninterrupted operation, universal compatibility, or absolute protection against every misuse, attack,
disclosure, or failure scenario.
No public certification claim
No certification, audit standard, or independent assurance is claimed unless SentinelLolge expressly
publishes it.
Security contact
Security-related questions or responsible disclosure communications may be directed through the contact
details on the contact page.
Data processing addendum
Data processing addendum summary.
This summary outlines the data processing framework SentinelLolge may offer to business customers for the
website service. Applies only where SentinelLolge and a customer agree in writing to business processing
terms. Effective date: May 7, 2026.
When this addendum applies
This summary is not a standalone contract and does not bind either party absent a written agreement. It
reflects the type of processing terms that may be incorporated into a business arrangement.
Roles of the parties
Where a business customer uses SentinelLolge to process personal data on that customer's behalf, the
customer is generally expected to act as the controller and SentinelLolge as the processor for the
applicable customer-controlled processing. SentinelLolge may nevertheless act as an independent
controller for its own corporate records, service security, fraud prevention, billing administration,
legal compliance, and similar internal purposes.
Scope of processing
The applicable business agreement should describe the subject matter, duration, nature, and purpose of
processing, together with the categories of personal data and data subjects relevant to the contracted
use case. The current website service is not designed around routine hosted ingestion of every raw
source file used in standard browser-first protection flows, but it may process account, access-control,
billing, support, and related operational information as part of providing the service.
Instructions, retention, and deletion
SentinelLolge processes customer-controlled data only in accordance with the applicable agreement,
documented customer instructions, service operation requirements, and applicable law. Retention,
deletion, return, and backup handling commitments are governed by the executed agreement.
Security measures
Where a written business arrangement is in place, SentinelLolge may commit to commercially reasonable
technical and organizational measures appropriate to the service and the agreed processing scope. This
summary is not a public audit statement, enterprise security schedule, or guarantee of a particular
control framework.
Subprocessors and transfers
Where SentinelLolge uses third-party providers to support the service, the applicable business
arrangement may address subprocessor use, notice expectations, and any transfer-related requirements
necessary for the customer's legal review. Public-facing legal pages should not be treated as the sole
source of negotiated transfer or audit terms for business use.
Incidents, assistance, and contact
Incident notification, data subject assistance, audit support, and regulatory cooperation commitments
are governed by the executed business agreement. Questions about business processing terms may be
directed through the contact details on the contact page.
Subprocessors
Subprocessor disclosure approach.
SentinelLolge may use subprocessors to support operation of the current website service. Public disclosure
is provided at a legal and operational level. Additional diligence materials may be handled separately where
appropriate. Effective date: May 7, 2026.
General approach
SentinelLolge may use third parties to support hosting, service operation, analytics, identity, payment
processing, communications, and related business functions.
Public disclosure scope
The public disclosure does not enumerate every downstream supplier, infrastructure dependency, or
internal tool. It states the legal and operational scope within which subprocessors may support the
website service and may handle personal information relevant to their role.
Categories of subprocessor activity
Subprocessors, where used, may support account operation, identity and sign-in flows, analytics and
measurement, payment processing, customer communications, customer support operations, hosting and
storage, security monitoring, and related operational functions necessary to run the service
responsibly.
Business diligence
Where a customer requires a more detailed subprocessor review in connection with a genuine business
relationship, SentinelLolge may provide additional diligence information through the appropriate
commercial or legal process.
Updates
SentinelLolge may update this page as the service evolves, as legal requirements change, or as the
company's disclosure posture changes. The absence of a public vendor-by-vendor register does not mean
the service operates without subprocessors.
Relationship to other documents
Read this page together with the privacy policy, security overview, and any separately agreed business
terms. Requests relating to data processing, diligence, or subprocessor concerns 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
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.