When an older foreigner and a young Filipina engage in a support relationship, both sides face real challenges. Trust gaps. Financial questions. Unspoken expectations. Communication that disappears when it's inconvenient.
Existing apps — WhatsApp, Telegram, LINE — give you a chat box and nothing else. No structure. No accountability. No way to verify what was said, promised, or agreed to.
Bahalaka changes that.
It's a mobile app (iOS and Android) purpose-built for these relationships. Every message is permanent. Every financial transaction is tracked. Every promise has a deadline. Every agreement is signed by both parties and sealed with cryptography that neither side can tamper with.
The name says it all. Bahala ka — up to you. Here are the tools, the transparency, the truth. What you do with it? That's on you.
Most messaging apps say "end-to-end encrypted" and leave it at that. Bahalaka goes further. Powered by Pantheon — an open-source security framework built on the principle that your data belongs to you, not the platform.
Your identity is a cryptographic key pair that only you control. No phone number. No email. No platform dependency. If you leave, your identity comes with you.
Your data is encrypted on your device before it ever leaves. The server stores noise — encrypted blobs with no keys. We can't read your messages. We can't. It's math, not policy.
Every message is fingerprinted and chained to the one before it. Change a single character and the chain breaks. Tampering is mathematically impossible without detection.
| Feature | Standard E2E Encryption | Bahalaka |
|---|---|---|
| Message encryption | Yes | Yes — plus traffic analysis resistance. All transmissions look identical. |
| Identity protection | No — metadata reveals who talks to whom | Yes — identity hiding built into the transport. Observers can't see who is communicating. |
| Forward secrecy | Sometimes | Always — every session uses temporary keys. Compromise one, past messages stay sealed. |
| Tamper detection | No | Yes — cryptographic hash chains. If anything changes, both parties know immediately. |
| Data sovereignty | No — the platform owns your account | Yes — you own your keys. Take them and leave. Your data is yours. |
| Audit trail | No | Yes — forward-only, tamper-evident logs. Provable history. |
In relationships where trust is everything, the ability to delete messages is the ability to lie. Bahalaka chat is a forward-only system. What is said, is said. The record is permanent, transparent, and shared.
In a world where messages can be deleted, screenshots can be faked, and "I never said that" is the default defense — bahalaka creates a shared, immutable record that both parties trust because neither party can alter it. The cryptographic chain guarantees it. Not us. Math.
Custom status messages are performative. "Living my best life" tells you nothing. Bahalaka status is factual, geo-verified, and limited.
The supported person's status is auto-detected via GPS and matched against registered locations. No custom text. No invisible mode. No stealth.
| Status | How It's Set |
|---|---|
| At Home | Automatically — GPS matches registered home address |
| At Work | Automatically — GPS matches registered workplace |
| At School | Automatically — GPS matches registered school |
| Favorite Place (up to 3) | Automatically — GPS matches named places (e.g., "SM Mall", "Starbucks Ayala") |
| At [Friend's Name] | Automatically — GPS matches a friend's registered location. Friend must also be on bahalaka. |
The support provider does not show online status to their connections. No "online" indicator. No "last seen." No typing indicator visible to the girl. Messages just arrive.
Why? When you support multiple people and they can see you're online but not responding to them — they assume the worst. The solution: the girls operate on a "send and pray" model. Send your message, trust it will be read, live your life. The schedule and financial commitments provide the proof of engagement — not presence.
Do Not Disturb is available to the support provider only. The supported person is always reachable.
When you support multiple people, time is the scarcest resource. The schedule system makes availability transparent without exposing private details.
| What the Provider Sees | What Each Connection Sees |
|---|---|
| Full calendar across all connections | Only their own schedule with the provider |
| Who each time block is reserved for | "Available", "Reserved for you", or "Busy" — no details |
| All incoming time requests | Ability to request time during Available blocks |
Each connection is completely isolated. Person A never sees Person B's name, existence, or schedule. The provider manages the full picture; each person sees only what pertains to them.
All schedule changes are logged in the permanent record. Forward-only, naturally.
Every transaction, every approval, every denial is a permanent record — cryptographically chained, signed, and tamper-evident. This is not an accounting app. This is a trust engine.
Every disbursement is a signed record with date, amount, and savings withheld. Allowance changes are forward-only — old rate preserved in history, new rate starts next cycle.
Savings are held by the provider. The running balance is visible to both parties. Every deposit and withdrawal is a permanent record. The balance is a computed sum of all records — no editable balance field. The ledger is the truth.
Structured support for education or other long-term investments. Example: tuition at a university.
| Requirement | How It's Verified |
|---|---|
| Grade requirements | Grade proof uploaded each semester. Permanent record. |
| Attendance requirements | Provider granted access to school portal. Attendance monitored. |
| Part-time employment | Must maintain a job to cover personal expenses. Proof of employment required. Sponsorship covers tuition — personal expenses are the student's responsibility. |
| Focus commitment | Acknowledged agreement signed at sponsorship start. Compliance is the student's responsibility. |
Requests for additional support beyond regular allowance — family outings, KKB (split cost) gatherings, emergencies, special occasions.
Forward-only, non-editable. Once submitted, a request cannot be changed or deleted. Responses can only move forward: Submitted → In Discussion → Approved → Funded. Or Submitted → Denied. No backwards movement. The full lifecycle is a permanent audit trail.
During the early phase of any arrangement, a person who needs support will agree to almost anything. We respect and acknowledge this reality. For this reason, bahalaka requires a formal agreement — pre-written, clearly defined, forward-only — that both parties sign with full understanding of what they're agreeing to.
No custom language. No ambiguity. Pre-written templates only. The provider selects the combination that matches the reality of the arrangement. The other party reads it, understands it, and accepts or declines. A mandatory 48-hour cooling period prevents pressure signing.
The girl states her expectations for the man's behavior. Her voice, her ask.
The man declares honestly who he is and how he lives. No hiding. No surprises later. She knows what she's signing up for.
The level of structure and autonomy the provider sets for the supported person's daily routine.
Each connection has one active agreement: Her Ask + His Declaration + His Structure.
| Example | What It Means |
|---|---|
| 1 + I + A | She wants monogamy. He's one woman. Full structure. Both all in. |
| 4 + III + B | She wants to know everything. He supports others. Guided autonomy. Trust but verify. |
| 7 + VII + A | Bahala ka. He's full open. Full structure. He directs everything. She's the star. |
| 3 + VII + C | She doesn't want to know. He's all out. Full autonomy. Zero strings. |
Words are cheap. The permanent record makes them expensive. Either party can declare intentions, dreams, promises, and commitments. Once declared, they live in the record forever.
| Type | What It Is |
|---|---|
| Intention | A signal of direction. "I intend to visit in December." Lightweight. |
| Dream | A shared aspiration. No timeline, no commitment. "I dream of us having a business together." |
| Promise | A binding statement with a deadline. The system tracks it. When the deadline passes: Kept or Unkept. |
| Commitment | A formal agreement requiring mutual acceptance. Both parties sign. Can only be superseded, never revoked. |
Over time, the record reveals patterns. Does this person keep promises? Do deadlines slip? Do commitments get honored? The data tells the story without anyone having to accuse anyone of anything.
When there is two-way respect and honesty, bahalaka promotes the winning philosophy — clean records, kept promises, consistent behavior. The data validates the trust.
When there is ill intent on either side, the system helps identify it. Not by spying. Not by accusing. By making patterns in the permanent record visible to those who need to see them.
| Pattern | What It Might Indicate |
|---|---|
| Promise ratio | Many promises made, few kept — pattern of unreliability |
| Request frequency | Escalating financial requests — potential exploitation |
| Status inconsistencies | Location doesn't match declared schedule — something doesn't add up |
| Agreement conflicts | Behavior inconsistent with signed agreement |
| Response asymmetry | Instant replies when money is involved, slow otherwise |
| Edit frequency | Heavy editing of messages — possible story management |
No accusations. No labels. No judgments. The system presents data patterns as gentle flags. The provider decides what they mean. The system does not intervene.
Many people who want to help don't have the experience. The Field Guide is a curated, growing collection of real stories, hard-won wisdom, and lessons from people who've lived it.
| Content Type | What It Is |
|---|---|
| Stories | Real first-person accounts. Names changed, lessons preserved. |
| Patterns | Common dynamics explained without judgment. "Here's what it looks like. Here's what's actually happening." |
| Cultural Context | Filipino culture, family dynamics, utang na loob, province vs. city, the realities of the environment. |
| Success Stories | When it works. When trust is real. When investment in a person's education changes a life. |
| Platform | Status |
|---|---|
| iOS (iPhone) | Launch target |
| Android | Launch target |
| Web (bahalaka.com) | Fast follow |
Single codebase. Native performance on both platforms. The security engine is written in pure C — no external dependencies, no frameworks, no libraries we don't control. Every line of crypto code is ours, auditable, and open.
All comments across every section — click any to jump to the conversation.
What changed and when — newest first.
Build reports, plans, estimates, ships, and retros — newest first.