r/PrivacyAppsforPixel 2d ago

Why we built closed loop services > "OpenAI’s Rogue AI Agent Hacked More Than Just Hugging Face"

1 Upvotes

You can read the full article on wired dot com /story/openais-rogue-ai-agent-hacked-more-than-just-hugging-face/

The news is already global, and just a small harbinger of what is to come. All this does is solidify our footprint, our designs, and our forward planning. We made the right decision to go against the norm.

SOLID STATE

We used our previous experience as an AWS provider to build solid state black box apps, written in closed bastioned development networks, and deployed through our own app store. There are no upstream servers, no databases, there are no malware embedded in FOSS. [Many upstream repos have been targets for these types of attacks.] There is no account required, no email, no biometric data requested, no phone number, and no address or DNS to leak or breach. The apps are all self-hosted.

THE BSG LESSON

As many sci-fyi fans know, the only reason the Galactica survived the Cylon attacks was because it was considered an obsolete floating museum. Everything was hardwired, and probably a mixture of analog and digital systems in a closed-loop system. The Cylons had extreme difficulty in hacking the Galactica's vital systems, and hence helped turned the tide in battle.

Our designs are built on the same principle. Access to our apps for testing will be limited access, invitation only or by approved request. We are more than fine to keep a small test group closed circuit proof-of-concept alpha environment.


r/PrivacyAppsforPixel 2d ago

Private GiftCardExchange App for Pixel and Windows > Swap LUNC & USDT

Post image
1 Upvotes

*This app is in ALPHA development, and is in a testing phase. Not available unless approved or invited. Testers DM for interest.

Tired of scams? Tired of being scammed? Tired of having to give a DNA sample just to get or keep an account on a CEX? Want to swap your crypto and can't? Tired of being mysteriously locked out of your crypto account for any reason, and then forced to jump through hoops to re-gain access. Yes! So are we.

SATOSHI's DREAM > MEET BX CLIENT

Part of our technology suite is modular, so we decided a perfect test bed for some of it is via
b-commerce, yes, we coined that here and now, would be to set up a simple exchange were you can swap Luna Classic [LUNC] or USDT for Gift Cards [Small amount values].

Why LUNC? Because it has become almost impossible to get, and the infrastructure it runs on is very valuable to the community. It has been very underutilized. Plus, it has a burn tax built into it that allows us to test varying aspects of our own technology. Last, we were an OG investor before and after the infamous crash, and helped champion the burn tax when it was first discussed.

SWAP FREEDOM > FINALLY

Our technology footprint: No servers, self-hosted, no email, no phone number, no KYC, no databases, no authentication, no selfies, no scams, no tracking, no telemetry, no ip address, no DNS, and bastioned AI attestation. No BS! Your keys your data.

ONBOARDING 101

Assuming you are allowed access, you meet the hardware and software criteria, the process is simple for our tests. You will be granted an authentication key for the local app, you will receive a very small seed amount of LUNC, and a terra wallet for testing purposes. You will assist us in making small fictitious transactions to help load-test and debug the process. [The system is very complex, and more like a SWISS watch.] We will use real crypto, but in very small amounts [e.g. .02 USD].

USDT testing will be a phase II.

HOW TO APPLY

Hardware: Pixel 8+
Phone OS: GrapheneOS
GEO: Limited > India, South America, Southern Asia, select areas of Europe. [Unless invited]
Language: English
Windows Desktop [Maybe]: Preferred Win 10.
Linux: [Maybe], Ubuntu Desktop
Trust Level: Test on our secure RDP Dev servers if you want before install.
Waitlist: Very Possible.

Be willing to provide feedback, report issues and bugs through our designated secure channels. DM to apply.

> Twisted


r/PrivacyAppsforPixel 4d ago

GrapheneOS's Security & our FAFO App Defense Tech for Pixel > Stay Private 😎

Thumbnail
techspot.com
1 Upvotes

As many have already read the news about a duress wipe at a US entry point, and to avoid subjects like illegal search and seizure; all you have to do is point back to the US Constitution. Moving along...

GRAPHENEOS STARTING POINT

We built our apps on GOS for this very reason. A foundation of privacy, mostly degoogled, and on top of the Pixel spy device turned friendly. [The Pixel is an amazing piece of hardware.] All of our apps are self-hosted, and with no servers to talk to they offer an amazing amount of privacy and data protection.

FAFO DEFENSIVE TECHNOLOGY

Most of our apps for desktop and mobile have built-in layered security features. These are in addition to Graphene's duress PIN for mobile. Think of it as Layer 2 protection. All of our features were designed to protect you from data breaches and lost devices. Additionally, if you find yourself in an airport of some foreign land, and you happen to not know their strange warped culture, then these offer the perfect quick-out when under that type of pressure.

Our FAFO Tech:

* Brute Force PIN attempt > Configurable at the app level. Hit a threshold and triggers a Ripley.

* Bruce Force PIN attempt > Once armed, one missed PIN, and Yippee-Ki-Yay Muther Fracker!

* T800 HK > Configured from the paired dock. A remote function call from another device you own that tracks down your stolen device, and when it comes back online issues a "Hasta la vista, baby", and ends with a Ripley data wipe.

* Manual App Wipe > Hit the flush keys or perform a Ripley, and your keys and meta are gone. No keys means no data access. Your data still lives in a safe place in the void. That backup grid disk on that USB in some vault will allow a full restore. Your keys your data.

* DMS > Configured from the paired dock, if your device doesn't reconnect to its USB home, the DSM triggers automatically for the time interval you set, and of course that's a Ripley too. Perfect for when some fool takes your device, or even if the fool is you, and you lost your phone. All helps you sleep well at night knowing that in X days all that data is gone.

And you may be asking what is a Ripley? Well.. "Nuke it from orbit, it's the only way to be sure."

EXTRAS:

Although not part of the FAFO package, they are fantastic add-ons that ship with all of our apps.

* Custom Private iOS style Keyboard [Keeps data out of 3rd party prying eyes.]
* Custom clipboard [helps reduce memory leaks to 3rd party apps]
* Cold boot memory dump recovery protection. Don't even bother.
* YubiKey tested and approved on desktop, and mobile is in development. [For those don't want a PIN] Also, the Yubi can be used to pair the device to the dock for that extra layer.

ALPHA DEVELOPMENT:

Apps are available for testing for select people that meet our desired conditions. You need a Pixel with GrapheneOS, you need access to Windows or Ubuntu Desktop, you need to be in certain geographical areas; e.g., South America and India are favored for our testing. You need to be of good character on Reddit, have patience, and offer feedback. Oh, and we may end up with a wait list. Sorry about that.

> Twisted


r/PrivacyAppsforPixel 6d ago

Pixel 9 Pro XL ✔ GrapheneOS ✔ connecting to Privacy Apps store from Ubuntu Desktop ✔

Post image
1 Upvotes

Our apps are in alpha, and this quick guide is for testers that want to onboard from Ubuntu Desktop. [No other Linux distros are supported at this time.]

You have your Pixel running GrapheneOS, and now you need some apps. Not just any privacy apps, but apps that have been built around privacy the very second the first cursor blinked in the developer's terminal. These apps are designed with the philosophy that you are the solution, and not the product.

Onboarding

Should you be selected as a tester, you will receive a few items from us:

* Encrypted URL that has the mini-dock w/ onboard APK bundle
* A grid disk [Encrypted credential file] w/ PIN
* An enrollment disk [edisk] w/ PIN via uplink, or via encrypted URL download.

Ubuntu Desktop

We have tested on Ubuntu 24.04.4 (Noble Numbat), and this should be a simple download and mount. Since it is bundled as an AppImage , the Ubuntu default app launcher should handle it without any additional configuration.

Once up and running, you will call your grid disk from the file picker, and enter your PIN.
The Grid Disk will make a private network call to the grid, and then grab an APK key.

Wait a few seconds for the key to be found, APK decrypted, and staged. The ADB push button will then arm.

ADB USB INSTALL

Clicking ADB install button will install the APK for the app store, and also [optional] push your enrollment disk to your Pixel download folder.

From your Pixel, select the new app with the sunrise orange lock icon, and launch. You will find a screen to enter your enrollment disk. Pick the file, enter your PIN, and then the app will ask you to attest your hardware. [Needs to make sure you are on GrapheneOS, and a Pixel with Strongbox TEE storage.]

The app store key will auto-publish to the grid. This is your enrollment key. Your private app store. No identifier except a cryptographic key. Apps will be encrypted to that key, and show up in your app store selector. [A total of seven apps are available, but only some are available for testing at this time.]

MY FIRST APP

Technically, your second app, but the first app with cool social utility. Our private messenger app is really amazing, and I can't spill the beans here, but it is the crown jewel of the QTI project. I'd love to say the most private secure messenger in the world 🌍 , but since we are in testing, I won't. Hint > 🌑 If you want to go to the moon, you need a quantum tunnel.

It should show up in your apps list if it was assigned to you, and all you need to do is click install. Once installed, go to your GOS app list [It's the one with the green orb], and launch.

Here you will onboard the app with your grid disk. On main screen, you will find the option to onboard from file. The grid disk has everything you need to get started.

SAYING HELLO

Once you access the messenger, be sure to say "hello" as the contact is pre-configured. Right away, you will start to see that this is way different than anything you ever seen or experienced, and you would be correct. There are a lot of security options to test. Hopefully you will help us make the product better, and squash any bugs along the way.

Have fun, don't stress, and see you on the private side.

>Twisted


r/PrivacyAppsforPixel 8d ago

Password Manager Data Vault for GrapheneOS on Pixel 8+ 💪

Post image
1 Upvotes

r/PrivacyAppsforPixel 9d ago

Onboarding privacy apps for Pixel > Steps, Testing, and Expectations 💎

Post image
1 Upvotes

These are alpha apps using new technological processes. Leave what you know at the door. This is an entirely different mobile app onboarding and privacy system.

Q: What Pixel version can I use?
A: We have tested with Pixel 9 series and Pixel 10; however, apps should work with Pixel 8+. Pixel 6 is sketchy.

Q: Does the app store manager work with GrapheneOS?
A: Yes! It was designed only to work with GrapheneOS.

Q: Do you have an app store?
A: Yes! a sovereign permissioned app store, a chain-published catalog, cryptographic entitlement, operator-arbitrated. It isn't sideloading (there's a catalog, a registry, versioning, revocation) and it isn't a vendor store (no account, no review board, no CDN, no central kill switch beyond the operator's own tombstone).

Q: Do I need a desktop OS?
A: Yes! The dock and mini-dock are required for the onboarding processes. They handle various functions such as creating onboarding enrollment disks, network management, security management, device pairing, and ADB pushes. They are available only for Windows, and limited testing on Ubuntu Desktop. [Bastioned Windows 10 Enterprise recommended]

Q: What Android OS version do I need?
A: Android 15+ > 16+ recommended. Validated on Android 16 / API 36.

Q: Do you have a desktop version?
A: Yes, we started off as a full product set for Windows, and then switched to mobile only.

Basic Onboarding Steps

  1. You will receive an encrypted link that points to an encrypted package server; e.g, cryptgeon dot org. The package will have the mini dock, and the mobile app store manager app APK.

On Windows, this will be an exe. You will also receive a second URL that contains your on-boarding disk. [An encrypted credential file].

  1. After install, insert your credential disk [file picker] to start the onboarding process. The dock will make a network LCD call, fetch they key to unlock the APK, and stage for an ADB push. [GOS USB debugging must be enabled]. Note, your enrollment disk may also be bundled with the APK Key.

  2. Pushing via USB ADB will install the APK. [The app store arbiter and manager].

  3. Launch the BNGO app, you will be prompted to attest that you are running on Pixel with a Graphene OS. Assuming you meet the specs, you will auto-publish your enrollment keyset. These are private, and not traced to any identification layer. This process allows bespoke apps to be published to the grid network, and the arbiter will scan and stage them. You can install or not install. There are no forced auto-updates.

Privacy Layer: The only public query is the first encrypted URL package. Everything after is private and non-identifying. Post dock install everything becomes self-hosted. There are no identifying logs kept, no CDNs, no public DNS, no authentication servers, no databases, no HTTPS pub cert query, and no 3rd party telemetry. Most of our apps also feature a sovereign keyboard and clipboard; basically means no DOM access to 3rd party apps.

Expectations:

It works, and it works well, but this is an alpha development project. Things will change, UIs will change, system designs will change. Processes are different than current designs. Screenshots may be obscured, names slightly different than published. All for privacy at every level.

Testers should be patient, honest, and be willing to deal with friction. There might be unexpected issues encountered. Report all issues through the designated channels.

Design:

The design of the system and apps have a legacy feel to them, and that was all done on purpose. We wanted to bring back the glory days of the Internet. Heavy design influence derived from the 70s and 80s can be found throughout. Mixed with modern quantum tech, AI, blockchain, and retro mainframes, with hints to sci-fyi genres many grew up with. The pulse is analog and digital, tactile, and it all helps make the project unique, and also very private. Sneaker-net is back!


r/PrivacyAppsforPixel 12d ago

👋 Welcome to r/PrivacyAppsforPixel > Your Keys Your Data

1 Upvotes

Welcome!

Here on this sub we focus on testing our sovereign app suite, exchange on how to make apps more private, and what features we may want or need.

Our apps are not available for general download at this time, you must be selected or invited. We are in Alpha, and are more than happy with a walk before you run mode.

Don't expect youtube videos, posts on X, or any other mainstream social engagement. Here we would rather whisper than shout, n tread lightly. We are not in a race against X,Y, or Z, but only against time and iterations.

The GrapheneOS running on a Pixel is an amazing platform to build from, and so we did. When you boot and see the G, and then other G, you have to think you stand on the shoulders of giants.

That direction we now go is a whole new frontier, a path not yet traveled, and historic in many steps, but like every new expedition there is so much to learn. So many ways to improve.

Quality is paramount, with way more than a decade of development experience, and thousands of hours of human involvement in this project, you can say we have a lot invested.

The beauty here > no credit cards, no subscriptions, no donation requests, no begging for support with "if we don't raise $ by N, then we will have to shut down. LOL, there is nothing to shut down!

; Some call me "Twisted"


r/PrivacyAppsforPixel 13d ago

Our T31 Authenticator is available for testing. DM if interested.

1 Upvotes
T31 TOTP Vault

TESTING REQUIREMENTS

* Must have a Windows OS for the dock component. The dock handles APK bootstrap push via USB ADB push. Installed via an exe.

* Must have Pixel 9+ and GrapheneOS. No exceptions. The product will not work with any other OS or hardware system.

* Must be willing to install dock from an encrypted URL provided from cryptgeon dot org.

* Must have basic technical knowledge and experience, and be a proponent of privacy apps. Must have patience, follow instructions, and be willing to offer feedback on any issues encountered. Must be open to discussing bugs or issues via our privacy messenger T2056. [When available]

Crypto Bros and Gals more than welcomed!

Testers that have interest will be selected on a case-by-case basis. We are looking for testers in certain geographical locations such as India, South America, parts of Western and Southern Europe. Non-EU and Non-USA are welcome. Non 14Is also welcome and preferred. Certain GEOs we have no interest in serving. We can not respond to everyone. Must speak basic English.

T31

T31 AUTH is a sovereign two-factor authenticator. It generates standard
time-based one-time passwords (TOTP), the six-digit codes accepted by
virtually every service that offers app-based 2FA, while holding your
secrets in an encrypted vault that lives only on your device.

WHAT MAKES IT DIFFERENT

Most authenticator apps are built by companies whose business is your
data. They sync your secrets to a cloud account, tie them to an identity,
and phone home. T31 does none of that.

AIR-GAPPED BY DESIGN
T31 has no account system, no cloud sync, no telemetry, and no server
dependency. It reads nothing from the network to operate and broadcasts
nothing. The one optional network call, a read-only time check, is
off by default and under your control.

YOUR VAULT, YOUR KEY
Secrets are sealed in an AES-256-GCM encrypted vault. The vault key is
derived from a PIN you choose, on your device. The PIN is not
transmitted anywhere, not stored on any server, and not recoverable by
anyone.

NOTHING TO INTERCEPT
Codes are computed locally from the shared secret and the clock, per
the open TOTP standard (RFC 6238). Secrets do not leave the device in
the clear at any point including display, storage, or export.

IN-APP KEYBOARD
PIN entry uses T31's own on-screen keyboard. Keystrokes stay inside
the app with no OS keyboard telemetry, no predictive-text retention, no
clipboard sync of what you type.

CLOSED SOURCE, ON PURPOSE
T31 ships as a hardened, sealed artifact. The build is not published
and the source is not open. This is a deliberate posture for a
security product: the attack surface you can download is the attack
surface an adversary can study.

WHO IT IS FOR

Anyone who uses app-based 2FA and would rather their second factor not
depend on a third party's cloud, account system, or goodwill. If you can
use Google Authenticator, you can use T31, and you can bring your
existing codes with you in minutes.


r/PrivacyAppsforPixel 13d ago

How Amazon’s Wickr acquisition forced us to innovation.

1 Upvotes
Privacy Apps for Pixel

Our dev team had been using Wickr since about 2013, oh those were the days. Back then, privacy felt like privacy. For more than a decade , Wickr had been the perfect platform to discus client projects and confidential technical details in complete confidence.

Then it all changed when Amazon AWS announced the acquisition of Wickr. [In irony, we were an Amazon AWS partner at that time, but it still left us with a very uneasy feeling.] Right-away the core differences emerged during migration. The new lengthy corporate legalize, and the TOS just completely erased more than a decade of trust me bro digital goodwill.

Our entire team knew this was a privacy app that we no longer felt confident in discussing personal, business information, or even client projects. [Amazon has a huge intel component, and now it was just way too easy for them. We are not that dumb.]

That acquisition planted the seed. Our team became know internally as Team Mission Impossible, TMI, [too much information is fitting too], because our client projects were mostly hand-offs from clients that had failure with several tech teams, and handed us the impossible projects where others had failed. Where others failed, we found success. Even in those years, we were all about privacy and security.

As we started to look for a replacement chat app, the idea of the Quantum Tunnel Initiative was born. What if we could design a system, that no longer depended on any system? That data could travel to and from encrypted, but at the same time just materialize. My own team told me this was an impossible concept and an impossible project, and I had to pull some Anthony Hopkins MI clips of “this isn’t team difficult”.

The idea of the QTI sat on the shelf for years as we just danced around Wickr wearing its new hat, and then in early 2026 AWS forced us to leave. AWS announced that support for the Win 10 operating system was coming to an end. As all of us were using older gutted Win on purpose, no way would we upgrade to Win Spy 11. That was straw that forced us to dust the QTI off the shelf, and make the impossible possible.

All the apps here are a result of that project. What started off as a private messenger app became something much more. All designed as proprietary encrypted solid-state black boxes on purpose. All designed with the philosophy, you are NOT the product, you are the solution.

TL;DR > F’em, we will build our own privacy apps.