Secure Authentication
Sign in with Google — no manual passwords. A JWT access token is stored in secure storage and validated on every app launch, with automatic redirection if it expires.
Your money data, properly protected
Secure authentication, room-level locks, and a clear permission model keep shared finances private and tamper-resistant.
Security & privacy
Three layers of protection
From the moment you sign in to the way each room is locked down.
Room Lock (PIN)
Protect sensitive rooms with a 4-digit or 6-digit PIN. Only members who know the passcode can open a locked workspace.
Bearer Token Requests
The network layer automatically injects your token as a Bearer header on every request, so each API call is authenticated end to end.
Transparency by default: when you invite someone to a room, a disclaimer makes it clear they'll be able to see the room's transactions and activity — so consent is always explicit.
Access control
User roles & permissions
PoolPay defines distinct roles to keep collaborative workspaces orderly and data accurate.
| Capability | Room Owner | Room Admin | Room Member | Personal Friend |
|---|---|---|---|---|
| Delete / Rename Room | ✓ | — | — | N/A |
| Manage Room Color Theme | ✓ | ✓ | — | N/A |
| Toggle Member Permissions | ✓ | — | — | N/A |
| Settle / Unsettle Dues | ✓ | ✓ | Optional | ✓ |
| Add / Edit Transactions | ✓ | ✓ | ✓ | ✓ |
| Remove Friends (Direct) | N/A | N/A | N/A | ✓ |
"Optional" means the Room Owner can grant a Member settle permission via a toggle in Room Settings.
Who does what
The four roles at a glance
Full control
Creates the room and holds every permission — rename, delete, theme, member permissions, and settlement.
Trusted helper
Manages themes, adds/edits transactions, and settles dues — without the ability to delete the room or change permissions.
Everyday user
Adds and edits transactions freely; settlement is available when the Owner enables it for them.
Direct peer
In personal 1-on-1 rooms, both friends can add, edit, settle, and remove the direct connection.
Questions
Security FAQ
PoolPay uses Google Sign-In. After authorization, a JWT access token is stored in your device's secure storage and checked at every launch. If it's valid you go straight to your rooms; if it's expired or missing, you're routed to login.
Yes. When creating a room you can enable a Room Lock and set a 4-digit or 6-digit PIN. Locked rooms require the passcode to open, adding a layer of privacy for sensitive workspaces.
Only members of a room can see that room's activity. When you invite someone, a disclaimer explicitly confirms they'll be able to view the room's transactions and activity, so everyone consents up front.
Rooms you leave or delete move to your Previous Rooms history with countdowns — a window before permanent deletion and a separate window to rejoin. Recovery buttons let you act before those timers run out.
Once a transaction is settled, its financial cycle is complete. PoolPay locks settled items from multi-selection and bulk actions to keep historical records accurate and tamper-resistant.
Logging out clears your security tokens from secure storage and redirects you to the login screen. Your room data stays safe on the backend and reappears the next time you sign in.
Share expenses with confidence
Secure sign-in, private rooms, and clear roles — get started in minutes.