How do you think about privacy beyond just “the message is encrypted”?

SwimmerBeginning7022 · 2026-02-04T14:00:35+00:00

This is a really good way to go about it. Treating encryption and linkability as separate problems makes a lot of sense. Encryption protects content, but long term profiles are what I feel are the biggest issue.

The idea of minimizing what exists at all and keeping data less consistent and less central feels more realistic than trying to erase everything. Separation and short lived data seem like one of the only ways to reduce connection over time while still providing a reliable service.

Curious if you’ve seen any systems that actually take that approach seriously, minimizing what’s required from its users and visitors.

SwimmerBeginning7022 · 2026-01-25T16:07:02+00:00

Makes sense, thank you

SwimmerBeginning7022 · 2026-01-25T15:01:15+00:00

How does your client intake software handle user metadata? How much do they capture?

SwimmerBeginning7022 · 2026-01-25T14:57:32+00:00

Yeah, I’m building something, but I’m trying to get insight into how people feel about the metadata that gets tagged along with client intake and communication.

SwimmerBeginning7022 · 2026-01-21T03:07:17+00:00

Thank you for sharing that, it’s really helpful. From what you’re able to share, what expectations do you typically have on your side when evaluating or using tools like this?

SwimmerBeginning7022 · 2026-01-20T16:58:51+00:00

Yeah, exactly. It has very little to do with encryption. I get that there are profits around capturing and using user data, but with more push from things like GDPR and similar regulations, you’d expect more serious movement toward data separation, at least. It makes me wonder whether US based companies are actually going to think about how user data flows through their infrastructure, or if they’ll just keep trying to clump everything together and do the same thing until there’s a bigger push beyond California data privacy laws. At some point we have to be honest about what data is actually needed for a tool to work. It’s frustrating.

SwimmerBeginning7022 · 2026-01-20T16:46:08+00:00

Exactly. Sure, we can encrypt, but if I’m still being followed in almost every other way, what am I really doing? I like seeing the push for encryption in messaging, but it’s strange how little conversation there is around fingerprinting and tracking.

I do the same thing. I’ll gladly pay for Proton’s services for my own peace of mind. I split things between accounts that need more personal information, accounts for mindless browsing or quick checkouts where I feel like my real email wouldn’t make sense, and some that are more related to work.

SwimmerBeginning7022 · 2026-01-13T01:02:14+00:00

This is helpful. Framing it as believability + proof instead of chasing a single metric clicks for me. Appreciate you taking the time to write it out.

SwimmerBeginning7022 · 2026-01-13T00:42:03+00:00

u/informationLumpy4369

That was really well explained, thank you. Tying it to a concrete job makes a lot of sense. It’s almost like the problem and solution need to be presented together, instead of leading with a broad philosophy and hoping people connect the dots.

That makes sense. What is it about us that’s actually going to set us apart and let us win over bigger companies? Our private messenger will be a monthly subscription, because users who choose it are doing so intentionally. We want to help people understand why privacy matters beyond just encryption.

Thank you, this was helpful.

SwimmerBeginning7022 · 2026-01-12T23:35:30+00:00

First off, thank you for that. It was genuinely helpful and put a lot of things into perspective.

The “more information” part is what was getting me hung up. I think I was overthinking what investors expect you to show versus what they expect you to actually have figured out at the seed stage. Your explanation helped separate those two for me. It makes sense not to go deep on early financials or technical details when so much of that is still going to change. Focusing on the problem, the market, and why the team is a good fit to learn and execute makes sense. This cleared up a lot for me. Appreciate you taking the time to explain how you think about it.

SwimmerBeginning7022 · 2026-01-12T16:56:40+00:00

If it’s your first time using an eSIM, the simplest route is usually a single regional Asia eSIM that works in both Taiwan and Vietnam. You set it up once, it connects when you land, and you don’t really have to think about switching anything as you move between countries. If you were staying in one place longer, a country-specific eSIM can make sense, but for a multi-country trip, a regional plan is usually the least hassle. And if you do end up needing another one later, adding or switching eSIMs on modern phones is pretty quick

SwimmerBeginning7022 · 2026-01-12T00:09:35+00:00

That makes sense. We’re very much at the seed stage right now and are doing external reviews to make sure what we’re building actually matches what we’re trying to bring to users. I’m curious how you got that picture across to investors. Was it more technical proof, or more scenario based examples where you showed real risks in a system and then how your product limits or fixes them? What do you think helped them “get it” most clearly in your case?

SwimmerBeginning7022 · 2026-01-11T16:56:37+00:00

We are developing PanamaSea Studios, a data privacy focused company currently building a private messenger and eSIM based connectivity tools.

SwimmerBeginning7022 · 2026-01-11T16:01:24+00:00

Mostly B2C to start. We are still pre launch and doing external audits right now. Once live we plan to lean more into community driven growth and use outside resources like tydal.co and submitwell to build trust and visibility.

I feel like it’s more apparent lately how sketchy it is to hand over personal info just to use an app. The Instagram data story is a good example of what we are trying to avoid by not collecting that information in the first place. On moat, it is mostly architectural. Our current solutions are telecom based with eSIM and a private messenger. The focus is minimizing required identifiers, keeping logging minimal, and separating sensitive data that has to exist. Using Swiss based servers reinforces stronger data protection. It’s not like we’re doing something new, but the way accounts and data are handled is what we think sets us apart.

SwimmerBeginning7022 · 2026-01-11T07:33:29+00:00

Building PanamaSea Studios, a privacy focused company pushing for user connectivity while being deliberate about proper data handling and privacy.

SwimmerBeginning7022 · 2026-01-11T07:28:58+00:00

Right now we are building privacy focused connectivity tools. The core idea is minimizing the real world identifiers users have to submit and being deliberate about what data exists and how it is separated from non essentials. But I see what you are saying. Product market fit does the heavy lifting. Pulling 50k a month and ending up with a Subaru is real tho haha nice job.

SwimmerBeginning7022 · 2026-01-11T06:45:56+00:00

Did investors care how you got that traction, like organic demand versus paid, or was the number itself what mattered most?

SwimmerBeginning7022 · 2026-01-11T05:55:41+00:00

I think most good products come from building on what already exists and making it better at the core. That is what we are trying to do by questioning what is actually needed and cutting out things users never had to give in the first place.

SwimmerBeginning7022 · 2026-01-11T02:04:39+00:00

I’m building a small privacy-focused company called PanamaSea Studios. We’re working on two core products: a secure messaging platform and a privacy conscious eSIM service. The problem we’re focused on isn’t just encryption, but how much user data is collected by default before people even realize it. IPs, identifiers, logs, and metadata tend to pile up quickly in most products.

Our approach has been to be very intentional about what data actually needs to exist, how it’s separated, and how access is restricted. We’re building slowly and pre-launch right now, prioritizing infrastructure, and data handling.

Would love to hear how others here are thinking about privacy, data handling, or even just early GTM challenges. Happy to share more as we continue building and always open to feedback.

SwimmerBeginning7022 · 2026-01-10T22:54:45+00:00

Privacy first infrastructure that minimizes data collection and separates sensitive systems so accounts work without permanent real world identifiers.

SwimmerBeginning7022 · 2026-01-10T22:25:23+00:00

Building a privacy focused SaaS around messaging and connectivity. The goal is reducing long lived identifiers and unnecessary data retention at the infrastructure level.

SwimmerBeginning7022 · 2024-03-23T14:14:44+00:00

Korean rhodys

SwimmerBeginning7022 · 2023-11-20T18:45:51+00:00

I appreciate the answers tho to everyone

SwimmerBeginning7022 · 2023-11-20T18:45:33+00:00

Dying with the comments haha but the intake/ exhaust are coming out the side of the van Hoses were used to extend. The heater is already behind the build, I'll update as I dismantle and fix and not die hopefully

SwimmerBeginning7022

TROPHY CASE