Ulgama

How Ulgama works, and who holds what

Three letter pages for a board meeting: the picture and the honest line, what stays locked and who else handles data, and who can do what. Print this page from your browser; nothing else prints.

Back to Trust and security
Ulgama

How Ulgama works, and who holds what

Checked against the running system on October 19, 2026 · release 0.15.1 · app 1.0 (5)

  1. 1 · Your organizationthe people
    • Only your administrators make members; roles decide what each can open and do.
    • Password plus a passkey or authenticator app. Wide roles must use a passkey. No codes by text or email.
    • Sessions end after 30 minutes idle, 12 hours at most. Leavers are signed out of every device at once.
  2. Face ID or PIN · sign-in kept in the iPhone's Keychain
    2 · The iPhone appin a member's pocket
    • A scan is encrypted on the phone, uploaded, then removed from the phone.
    • The app wipes itself on sign-out, after five wrong PINs, seven days locked, or a sign-out from the website.
    • Approvals on the phone are confirmed with Face ID.
  3. All traffic encrypted · roles checked on every request
    3 · Ulgama itselfthe software running for you
    • One database; the database itself keeps organizations apart, even if the software erred.
    • Names, contacts and tax numbers encrypted under each organization's own key; documents encrypted where stored.
    • Every action, including every look at a name or donor, in a log nobody can change; signed daily. Filed documents are never deleted.
  4. Hardware security key · Google's own tunnel, never the open internet
    4 · Where it runs, and Charwa LLCwho runs it
    • Google Cloud, United States (South Carolina): servers, database, documents, keys, backups.
    • Backups: a key never on a Google machine; 400 days locked against deletion, then deleted.
    • Charwa LLC runs the servers, keeps backups, answers support, sets plan features. Only the owner and one sealed emergency account can reach the servers.

The honest line· A high, guarded wall with one named door. Not a sealed box.

Charwa LLC runs the servers, so the people who run them could, technically, reach the records the system decrypts to show your members, such as names and documents. What stands in the way: Charwa LLC has no account in your organization and does not sign in to it; only the owner can reach the servers, with a hardware security key, through Google's tunnel; and the one thing Charwa LLC cannot open at all is the link between a gift and the person who gave it.

Page 1 of 3 · the pictureUlgama by Charwa LLC
Ulgama

What stays locked, and who else handles data

Locked to Charwa LLC · the keys · who else, and exactly what crosses

What Charwa LLC cannot see, by design

  • Who gave a gift. The gift–donor link is encrypted in your officers' browsers with a key Charwa LLC never receives: three printed share codes, any two open it. Lose all three and nobody can recover it.
  • Passwords. Stored only in a form that cannot be read back.
  • Passkeys. Their secret part never leaves the member's device.
  • Who came to an event. Attendance is counted, not named.

Who else handles data, and exactly what crosses

  • Google Cloudservers, database, document storage, keys, backups · United States
  • Google Workspacedelivers the system's email; no member names, no document contents
  • Applenotifications to the app: an identifier and a count, never a name
  • Cloudflareanswers the lookup of Ulgama's address only; carries no traffic
  • Public registersonly if switched on: the organization's own public details; nothing about a person

Nobody else receives data unless the organization sends it itself (an export, a connection it sets up) or the law requires it.

What Ulgama never does. No advertising, no tracking across sites or apps, no analytics service, no selling or sharing of data for marketing, no cookies from other companies. No organization's data is sent to an artificial-intelligence service.

Your records are yours. The organization can export its records at any time. Records are kept for as long as the organization keeps them.

The keys, and who holds them

  • Google's master key · Google's key service; used by the system, not handed to people
  • Your organization's own key · locked by the master key; unlocks your sensitive fields
  • The donor key, in three pieces · three of your officers; any two open it; never Charwa LLC
  • The backup key · Charwa LLC, never on a Google machine
Page 2 of 3 · who else, and what Ulgama never doesUlgama by Charwa LLC
Ulgama

Who can do what

A mark and a word in every cell, never colour alone.

Decision or actionYour administratorsYour membersCharwa LLCNobody
Who is a member, and their rolesyesnonono
Which folders and records a role can openyesnonono
Switching a module on or offfor the modules the plan includesnonono
Which paid features the plan includesnonoyesno
Opening the donor linknotwo of your three key-holding officers, togethernonever Charwa LLC
Seeing a member's name or contact detailsnoif their role allows it; every look is recordednono
Running the servers, updates and backupsnonoyesno
Deleting a filed document, or changing the lognononoby design
Taking all the records out (export)yesnonono