Trust & Privacy Manifesto
Every company says they protect your privacy. The words have been hollowed out by the ones who didn't mean it.
This document exists because I know you don't believe privacy promises anymore. Neither do I. That's why I built OSQR.
I don't believe every company sells our data. Many genuinely try to protect users. But the system makes it hard to tell who's trustworthy—and even well-intentioned companies can be acquired, pressured, or compromised.
OSQR is different—not because I'm asking you to trust my words, but because I've built a system where trust is architectural, not promissory.
My Personal Commitment
My name is Kable Record. I built OSQR. I own 100% of it.
I will never sell OSQR to a company that doesn't share these values. I will never take investor money that compromises user privacy. I will never dilute ownership to people who see your data as a product.
| Typical Startup | OSQR |
|---|---|
| VC investors demand growth at any cost | I answer to users, not investors |
| Board can override founder on privacy | No board. My decision. |
| Exit pressure leads to data monetization | No exit pressure. I'm building for decades. |
| "We had to change our privacy policy" | I don't have to do anything |
I'd rather own 100% of something smaller than any percentage of something that betrays users.
Architectural Transparency
OSQR's privacy isn't a policy—it's how the system is built.
"Your data is protected by design, not just by policy."
| What This Means | How It Works |
|---|---|
| Your data is encrypted at rest | AES-256 encryption protects stored data |
| Embeddings are irreversible | Numeric vectors that cannot be converted back to text |
| Strict access controls | No human at OSQR can browse your vault contents |
| Cryptographic deletion | Destroy keys = data becomes meaningless |
Roadmap: True End-to-End Encryption (v1.1)
We're building toward a zero-knowledge architecture where data is encrypted before leaving your device. Currently, data is encrypted at rest on our servers with strict access controls. Client-side encryption is on our v1.1 roadmap.
The Legal Consequence:
- Right to deletion? Delete your key—data becomes meaningless
- Subpoena? I can only hand over encrypted blobs
- Data breach? Encrypted data breach is a non-event
- "Sell my data"? I can't sell what I can't read
I'm not asking you to trust my intentions. I'm showing you a system where bad intentions wouldn't matter.
The Constitutional Framework
OSQR operates under a published constitution—rules the system follows that you can read and verify.
These aren't policies. They're constraints built into the code.
Radical Receipts
I publish regular transparency reports:
Government/Third-Party Requests
Every data request received and what was shared (spoiler: nothing, because I can't read it)
Security Incidents
Any incidents and exactly what was affected
Revenue Sources
Proving no data monetization
Third-Party Audits
Security audits from independent firms
Boring consistency over time builds trust.
The Anti-VIKI Promise
In I, Robot, VIKI was a centralized AI that controlled all robots—one intelligence making decisions for millions of people, "for their own good." OSQR is architecturally the opposite:
| VIKI (What We're Avoiding) | OSQR (What We're Building) |
|---|---|
| Centralized control | User-owned intelligence |
| Platform decides what's best | You see and control everything |
| Your data serves the system | Your data serves you |
| Robot loyalty to manufacturer | Intelligence loyalty to you |
| "Trust us" | "Verify it yourself" |
Your robot should work for you, not the manufacturer.
Your AI should work for you, not the platform.
As OSQR expands to more devices—phones, computers, cars, eventually robots—this architecture ensures the intelligence layer always belongs to you.
What OSQR Will Never Do
These are hard commitments, not aspirational statements:
Never sell your data
The architecture makes this impossible, not just prohibited
Never use your data to train models sold to others
Your intelligence is yours
Never show you ads
Revenue comes from subscriptions and plugins, not attention harvesting
Never lock you in
Export everything, anytime, in usable formats
Never manipulate for engagement
OSQR's job is to improve your thinking, not maximize your screen time
Never share with governments without legal compulsion
And even then, I can only share encrypted data I can't read
Never change these commitments
The constitution is immutable. If I tried to change it, the system would be forked.
The Trust Equation
I'm asking you to trust OSQR with your most personal information—your thoughts, decisions, family details, business strategy. Here's why that trust is reasonable:
| Your Concern | How OSQR Addresses It |
|---|---|
| Can they access my data? | Encrypted at rest, strict access controls, no staff access to vault contents. |
| Will they sell my data? | Never. Revenue comes from subscriptions, not data. |
| What if they're acquired? | 100% ownership. No investors. No board. My choice. |
| What if they go bankrupt? | Export your data anytime. Full data portability. |
| What if they change the policy? | Constitutional framework is immutable. |
| What if they lie? | Burn-It button lets you delete everything instantly. |
Trust is earned through transparency and action.
The Burn-It Button
One click. Everything gone.
Not "scheduled for deletion in 30 days."
Not "removed from active systems but retained in backups."
Not "anonymized and retained for analytics."
Gone.
The Burn-It Button:
- Deletes your encryption keys from all devices
- Instructs OSQR servers to purge all associated encrypted blobs
- Removes all metadata
- Confirms deletion with cryptographic proof
Why this matters:
You should be able to walk away. Completely. At any moment.
If you can't truly leave, you're not a user—you're a hostage.
OSQR will never hold your data hostage.
My Story: Why I Built This
I used an app that promised not to sell my data. Then I learned they did exactly that.
I'm not naive—I knew companies collected data. But the explicit lie bothered me. "We don't sell your data" wasn't a gray area. It was false.
I looked for an AI assistant I could trust with my real thoughts, my business strategy, my family details. Something that would remember everything and work for me, not harvest me.
It didn't exist.
So I built it.
OSQR exists because I wanted something I could actually trust. If I'm going to have an AI that knows everything about me—my decisions, my patterns, my family, my business—I need to know that information works for me, not against me.
I built OSQR for myself first. Then I realized others need it too.
Kable Record
Founder & 100% Owner, OSQR
For technical details on our current privacy practices:
View Privacy Policy →This document is version 1.0 · Last updated: December 2025 · ∞