Skip to content
Logpagia

Run your team

PeopleOperationsLobbiaPayrollRecruiting

Run your business

AccountingCRMService ManagementHealth

Work together

SpacesKnowledgePagia

Stay in control

ContractsSignaturesRisk & Compliance
All productsFor talent: meet Pagenia
Business leadersHR teamsOperations teamsFinance teamsCustomer teamsMulti-location teamsFront desk teamsHealthcare providersAll solutions
Resource libraryFind a useful starting point and reading.Product tourFollow the work, step by step.Getting startedPlan a practical first workflow.Global coverageUnderstand regional fit and limits.
Book a demoSee how Logpagia fits your team.Contact usTalk to Sales, Support or Security.Help and supportGet help with an account or a question.The platformHow the parts fit together.SecurityAccess, records and responsibility.IntegrationsConnections and configuration.
Pricing
Book a demoSign inGet started
Loading page…
Logpagia

A clearer place for your people, work and customers.

Platform

  • Overview
  • All products
  • Pricing
  • Product tour
  • Integrations

Solutions

  • Business leaders
  • HR teams
  • Operations teams
  • Finance teams
  • Customer teams
  • Multi-location teams
  • Front desk teams
  • Healthcare providers

Explore

  • Resource library
  • Product tour
  • Getting started
  • Global coverage

Company

  • Book a demo
  • Contact us
  • Help and support
  • The platform
  • Security
  • Integrations

Your workspace

  • Get started
  • Organization sign in
  • Explore Pagenia

© 2026 Logpagia.

Legal
  • Privacy
  • Terms
  • Cookies
  • Accessibility
  • Pagia AI

  1. Home
  2. /Privacy

Privacy

Privacy policy

What personal information Logpagia handles, who decides how it is used, which providers help run the service, and how people exercise their rights.

Document status

Effective 14 October 2026

Effective from 2026-10-14. Last reviewed against the current source on 2026-10-14.

Published by Logpagia Technologies LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78741, United States. Questions go to privacy@logpagia.com.

On this page

  1. Scope and who we are
  2. Our role and the customer’s role
  3. Information we handle
  4. Why we use it
  5. Legal bases
  6. Service providers and other recipients
  7. International transfers
  8. How long we keep information
  9. Security
  10. Your rights and how to use them
  11. United States state privacy rights
  12. Children
  13. Pagia and external AI processing
  14. Automated processing and decisions
  15. Changes to this notice
  16. Contact

Scope and who we are

This notice covers the Logpagia website and the Logpagia workspace applications an organization uses for people, time, payroll, hiring, documents, contracts, electronic signatures, customers, accounting, visitors, messaging and the Pagia assistant. It also covers the signing pages that people outside an organization open from a signature request.

Pagenia, the talent marketplace, publishes its own notice for marketplace accounts and public profiles. This notice covers candidate information once a candidate applies to an organization that hires through Logpagia.

Logpagia is operated by Logpagia Technologies LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78741, United States. The privacy contact is privacy@logpagia.com.

Our role and the customer’s role

An organization that subscribes to Logpagia decides which records it keeps about its employees, candidates, visitors, customers and signers, and why. For those records the organization is the controller, or the business under US state privacy laws, and Logpagia processes them on the organization’s behalf as its processor or service provider, following the organization’s instructions and the customer agreement.

Logpagia is the controller for the information it needs to run its own business: sign-in and account security data, billing and subscription records, website requests and chats, service operations and support.

If you are an employee, candidate, visitor or signer and have a question about records an organization holds about you, contact that organization first. Logpagia supports the organization in answering the request.

Information we handle

The information depends on which products an organization enables and what its members enter. The main categories are:

  • Account and sign-in: name, work email, password stored as an Argon2 hash, multi-factor authentication settings, sign-in history with network address and browser details, and security events.
  • Workforce records: employee profiles, job and organization structure, locations, emergency contacts, national or tax identifiers the organization requires, documents, clock events, timesheets, time off and daily work reports.
  • Payroll: pay rates, earnings, deductions, tax details, payslips and year-end forms, and the bank account details an employee provides for payment.
  • Hiring: job applications, CVs, interview notes, assessments and offers, including applications a candidate submits from Pagenia.
  • Visitors (Lobbia): visitor name, email, phone, company, host, purpose of visit, arrival and departure times, badge details, check-in requirements, screening results against the organization’s own watchlist, deliveries and emergency roll-call status.
  • Contracts and signatures: documents sent for signature, signer name and email, one-time verification codes, the signer’s agreement to use electronic records, signature images and field entries, and a tamper-evident event history that stores hashed network address and browser details.
  • Business records: customer contacts and accounts, invoices and accounting entries, inventory, tasks, calendars and internal service requests.
  • Messages and AI: Spaces messages and attachments, Pagia conversations, and the facts a person asks Pagia to remember.
  • Billing: billing contact, plan, seat counts, invoices and payment status. Card details are entered on Stripe’s payment page and are held by Stripe.
  • Website: the requested page, network address and browser details that every web request carries, recorded in server logs.
  • Website chat: the name and email a visitor enters before chatting, the messages exchanged, the website page where the chat started, and the browser, device and language details the chat records with the conversation.

Why we use it

Logpagia uses personal information to provide the service the organization requested, to keep accounts and records secure, and to run its own business.

The service contains no advertising and no function that sells personal information.

  • Create and secure accounts, verify email addresses and enforce each organization’s permissions.
  • Carry out the workflows an organization uses, such as payroll runs, approvals, hiring, visitor check-in and signing.
  • Send service email: verification, invitations, approvals, signature requests and notifications, each notification with an unsubscribe link.
  • Bill subscriptions and add-ons and keep financial records.
  • Provide support through audited staff tools, detect abuse, investigate incidents and keep audit trails.
  • Answer questions sent through the support chat and the website chat, and follow up by email when a visitor leaves the chat.
  • Meet legal obligations, such as tax, payroll and record-keeping duties.

Legal bases

Where the law of your location requires a legal basis, Logpagia relies on performance of a contract to provide the service, legitimate interests to secure and improve it and to communicate with business contacts, legal obligation for tax and record-keeping duties, and consent for optional choices such as Pagia memory. Answering a website visitor who starts a chat rests on Logpagia’s legitimate interest in responding to the question the visitor asked.

For records Logpagia processes for an organization, the organization determines the legal basis and gives the notices its employees, candidates and visitors need.

Service providers and other recipients

Logpagia hosts its application servers, PostgreSQL database, Redis cache and file storage on servers it rents from Contabo and operates itself. Electronic signature processing, including document conversion, malware scanning and signing keys, also runs on that infrastructure. Other providers receive information only for the purpose listed:

  • Email delivery: Resend sends service email.
  • Subscription payments: Stripe processes card payments, invoices and taxes for Logpagia plans and add-ons.
  • Support desk: Logpagia runs its support desk, Chatwoot, on the same infrastructure. Support and website chats, and the names and emails people give there, are stored there, with website chats kept apart from signed-in support.
  • Pagia: when an organization turns on external AI processing, and when Pagia answers Logpagia’s own support chat and website chat, OpenRouter routes the request to the one model provider Logpagia has approved for that route.
  • Payroll payments: Dwolla, in the United States, and Flutterwave receive payee and payment details only when an organization turns on live disbursement for a country those providers serve. Disbursement runs in a simulated mode by default.
  • Public signing forms: Cloudflare Turnstile checks for automated submissions when an organization’s deployment turns that check on.
  • Visitor messages: Lobbia sends emergency text messages through a message provider the organization connects.
  • Health applications: when an organization links a Health application such as RevMind 360, opening it shares the person’s name, email, organization name and country so that application can sign them in.
  • Platform staff: authorized Logpagia staff with an audited staff grant can view and support organization accounts. Support actions are explicit and audited.
  • Legal and corporate: authorities when the law requires disclosure, and a successor in a merger or acquisition under equivalent protections.

International transfers

Logpagia is a United States company. Several of the providers above, including Stripe, Resend and OpenRouter, are based in the United States, and model providers can process a Pagia request in other countries. Information can therefore be processed outside the country where it was collected.

Where a transfer out of a country requires a safeguard, Logpagia relies on the provider’s standard contractual clauses or an equivalent recognized mechanism, and on the data processing terms it offers customers. The data center location for the servers Logpagia operates is stated in those data processing terms.

How long we keep information

Logpagia keeps an organization’s records for as long as its subscription is active and as the organization instructs. Records are archived rather than erased when someone removes them, so audit, approval and payroll history stays complete.

After a subscription ends, Logpagia keeps the organization’s records available for export for 30 days and then deletes or anonymizes them, except where the law requires longer retention, such as for tax and payroll records.

Retention periods that are set in the product today:

  • A personal data export stays available to download for seven days.
  • A member’s account deletion request can be cancelled for 30 days. The account is then anonymized.
  • Documents sent for signature are kept for ten years by default, a period each deployment can change, and a legal hold keeps an envelope for as long as the hold applies.
  • Facts removed from Pagia memory are deleted permanently 30 days after removal.
  • A sign-in session cookie lasts seven days and ends when the person signs out.
  • Support and website chat conversations are kept in the support desk for 24 months after the last message and then deleted. Once a person takes over a chat, Logpagia replaces its own working copy of the messages with a placeholder; the support desk keeps the conversation.

Security

Every workspace query is limited to the requesting organization, and each person’s access follows the permissions their organization grants. Connections use HTTPS. Passwords are hashed with Argon2, multi-factor authentication is available, and repeated failed sign-ins lock the account.

Payroll identifiers, bank details, payment provider credentials and multi-factor secrets are encrypted with AES-256-GCM. Private files are served through short-lived signed links. Profile photos, organization logos and Pagenia profile media are served from public links so they can appear on shared and public pages.

No method of storage or transmission is completely secure. If Logpagia confirms a personal data breach affecting a customer’s records, it notifies that customer’s administrators without undue delay and no later than 72 hours after confirming it, with what Logpagia knows at that time.

Your rights and how to use them

Depending on where you live, you can ask to access, correct, delete or receive a copy of your personal information, to restrict or object to its use, to withdraw consent, and to appeal a decision about your request. Logpagia verifies the requester’s identity before acting and treats people who use these rights the same as everyone else.

Workspace members can edit their profile, request corrections to fields their organization controls, download a personal data export and request account deletion from their own settings.

For records an organization holds, send your request to that organization; Logpagia helps it respond. For information Logpagia controls, write to privacy@logpagia.com. Logpagia answers within 30 days, or sooner where the law requires.

If you are not satisfied with Logpagia’s response, you can complain to a data protection authority. In the European Economic Area that is the supervisory authority of the country where you live or work; in a US state with a privacy law it is the state attorney general; elsewhere it is the data protection authority of your country. Logpagia would rather hear from you first and asks that you give it the chance to resolve the matter.

United States state privacy rights

Residents of California, Colorado, Connecticut, Texas, Virginia and other states with a consumer privacy law have the rights described above, plus the right to appeal a refused request by writing to the same address and the right to use an authorized agent. Logpagia confirms the outcome of an appeal in writing, with the reasons.

Logpagia does not sell personal information, does not share it for cross-context behavioral advertising, and has not done either in the twelve months before the effective date of this notice. It therefore offers no opt-out link for sale or sharing. It uses sensitive personal information, such as government identifiers, bank details and health information an organization records, only to provide the service the organization asked for.

The categories of personal information Logpagia collects, the purposes, and the recipients are the ones listed in the sections above. Logpagia keeps each category for the periods listed under How long we keep information. Organizations that use Logpagia are businesses under these laws, and Logpagia is their service provider or processor for the records they hold.

Children

Logpagia is a business service for organizations and the people who work with them. It is not directed to children under 16, and Logpagia does not knowingly collect personal information from children for its own purposes. A person who administers a workspace or accepts the terms for an organization must be at least 18.

An organization that keeps records about workers under 18 where local law allows is responsible for those records and any consent they require.

Pagia and external AI processing

When an organization administrator turns on Pagia’s external processing, a person’s message and the records they choose to include can be processed by OpenRouter and the approved model provider. Checks on the organization, product, permissions and policy limit what is sent, and detected credentials, bank and payroll details, government identifiers and health information are blocked before sending.

When Logpagia turns it on, Pagia also answers questions in Logpagia’s own support chat and in the chat on this website. It answers from Logpagia’s product guide, and in the website chat also from Logpagia’s plan catalog. It sees only the conversation and reads no account or organization data. Up to the last ten messages of the conversation go to OpenRouter and the approved model provider, after a check that blocks detected passwords, keys, card numbers and national identification numbers.

Logpagia does not use workspace records to train AI models, and asks the provider route to deny data collection for training. The provider’s own terms govern how long it keeps a request and where it processes it. The Pagia AI page describes these controls in full.

Automated processing and decisions

The Services compute results automatically: time and overtime totals, compliance alerts, payroll calculations, candidate matching scores, visitor watchlist matches and Pagia’s suggestions. Each of these is shown to a person in the organization, who decides what to do with it. Logpagia makes no decision that has a legal or similarly significant effect on a person, such as hiring, discipline, pay or access to a building, without a person in the organization reviewing it.

Where a law gives you the right to know the logic of an automated result, to contest it or to ask for human review, contact the organization that uses the result; it holds the inputs and can explain the outcome. Logpagia supports the organization in that review.

Changes to this notice

Logpagia publishes each revision of this notice on this page with its effective date and tells organization administrators about material changes at least 30 days before they take effect.

Contact

Privacy questions and requests: privacy@logpagia.com. Post: Logpagia Technologies LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78741, United States. Logpagia appoints a local privacy representative where a law requires one and names that representative here when it does.

Cookies and browser storagePagia AI use and data boundariesSecurity and responsibility