Blog

What “your data is yours” means in practice

“Your data is yours.” Wonderful. It sounds reassuring, looks great under a padlock icon, and fits neatly into the sort of marketing sentence nobody expects you to question. But I have a question anyway: if the data is mine, why do I sometimes have to ask permission to see it, download it, or take it somewhere else?

We have reached a strange point in software where the information you create can feel less accessible to you than to the company storing it. You did the work, entered the transactions, organized the records, and paid for the service. Yet when you want your information back, suddenly there are menus, restrictions, unfamiliar file formats, and maybe a customer-support ticket standing between you and your own history.

At Skaynz, that doesn't sit right with us. We're a self-funded software company, and we intend to keep it that way because independence matters to the decisions we make. We don't need to pretend an irritating experience is delightful just because the industry has learned to call it a seamless ecosystem.

Ownership shouldn't disappear when you click “Sign in”

When did access become a favor?

Imagine keeping your business records in a filing cabinet, only to discover that someone else controls the key. They can decide when the cabinet opens, whether you may copy what's inside, and which boxes you can carry away. That would be an absurd arrangement for paper records, yet versions of it have become surprisingly ordinary in software.

There are perfectly good reasons for some applications to run online. Shared databases, live collaboration, and services that genuinely need a central server can benefit from that model. What bothers us is when online dependence is treated as the natural price of admission even when the job could be done locally.

Your bank statements don't become less yours because a company built a nice dashboard around them. Your photographs don't become less personal because they're in an account. And your business history shouldn't become harder to retrieve just because someone has decided that keeping you inside a subscription is good for retention.

A usable export is not a decorative button

Before you put years of work into an app, ask a question that seems almost embarrassingly basic: can I get all of it out? Not just a report, not a screenshot, and not a few columns that leave the interesting bits behind. Can you export the actual information in a format you can open and understand without begging that same company for another favor?

An export that only works in the original app is a little like a suitcase whose handle is welded to the floor. Technically, yes, the suitcase exists. Practically, you're not going anywhere.

Our approach is to keep information in open file formats that can be opened, backed up, and moved, and to provide export access whenever the user needs it. We shouldn't ask anyone to trust a promise they can't check. Take a copy, inspect it, and make sure the files remain useful outside the software that created them.

The less you collect, the less you can expose

My date of birth is not a feature request

There is a difference between collecting information needed to do a job and collecting information simply because a signup form has room for another field. If an app needs a shipping address to ship something, fine. If it needs my birthday, photograph, or mobile phone number before letting me organize a local spreadsheet, I would like a much better explanation.

Every extra piece of personal information creates another thing a company must store, secure, limit, and eventually delete. The customer usually has little visibility into how well any of that happens. Once exposed, information such as a date of birth or home address can't be fixed as easily as changing a password.

We're not opposed to security; we're enthusiastic about it. Strong authentication, including two-factor authentication, is useful when an account or sensitive remote service needs protection. But two-factor authentication doesn't automatically require a company to store your mobile number: authenticator apps, passkeys, and hardware security keys can provide alternatives depending on the system.

Security and privacy are supposed to be on the same team

We've somehow let “for your security” become a phrase that ends conversations instead of starting sensible ones. A legitimate security requirement should be proportional to the risk, and the company should explain what it needs and why. Nobody should be expected to supply a miniature identity dossier just to complete an ordinary task.

The National Institute of Standards and Technology treats authentication as a serious technical subject, not a contest to collect the most personal details. Its digital identity guidelines recognize different authenticators and assurance levels, including approaches that don't rely on SMS messages. That matters because a phone number is personal information, not a magical ingredient that automatically makes an account safe.

We design Skaynz apps to ask for the information the task actually requires, without ad targeting or behavioral tracking as a business model. We do not sell what customers entrust to us. Those are design commitments, not a claim that any computer, website, operating system, or third-party network service can be guaranteed to reveal absolutely nothing under every circumstance.

What happens after the breach headline fades?

When a database is breached, a company may issue notices, reset passwords, and promise a review. Those responses can be necessary, but the person whose information escaped may carry the consequences much longer. An exposed address, phone number, or identifying detail can be copied, combined with other records, and circulated beyond the original breach.

Verizon's 2025 Data Breach Investigations Report found ransomware present in 44% of the breaches it reviewed. That statistic does not mean 44% of businesses were breached, and it doesn't prove that every company is careless. It does show why storing information responsibly is an ongoing job, not a little checkbox marked “secure” at registration.

No, local-first software isn't magically invulnerable either. A stolen laptop, malware infection, damaged drive, or poor backup plan can make a terrible day. What local storage can do is reduce the need to put every working record in another company's central system just to use the application.

Six questions worth asking before you hand over your records

The questions a decent software company should welcome

  • Where does my information actually live? On my computer, on your servers, or both?
  • Can I use the essential features offline? If not, what specifically requires a connection?
  • Can I export everything in an open, usable format? Could I read the files if I stopped using the app tomorrow?
  • What personal information do you require? Which fields are essential, which are optional, and why?
  • How do you protect accounts without collecting extra identity data? Are there choices beyond SMS?
  • What happens if I leave? Can I retain useful records without depending on continued access to the provider?

These aren't hostile questions, and they shouldn't make a developer defensive. They're ordinary questions from someone trusting a piece of software with a part of their life. If the answers are buried under vague slogans, that's useful information too.

Backups are your responsibility, and that's worth saying plainly

Keeping local files gives you control, but it also gives you responsibility. If your computer fails and the only copy of your records was on that drive, a company can't magically reconstruct everything for you. You need a backup routine that makes sense for the value of the files, ideally including a separate protected copy you can restore.

We would rather say that clearly than make a grand promise about total safety. Some people will prefer managed online storage and be happy with the trade-offs. That's their choice, and the choice itself is what we want to defend.

Trust is earned by giving people choices

We aren't building a relationship with your data

Software should make a job easier, not arrange a lifelong dependency around it. A customer shouldn't need a lawyer, a technical consultant, and three weeks of email correspondence to recover their own work. And a company shouldn't call that inconvenience a feature just because it makes leaving harder.

We want people to choose the tools they genuinely like and keep choosing them because they do good work. We're not backed by venture capital, and we don't plan to trade that freedom for pressure to squeeze more information or revenue out of every user. We know not everyone will agree with our approach, and that's fine.

“Your data is yours” should be a testable statement, not a decorative promise. You should know where the files are, how to back them up, how to move them, and what information you were asked to surrender along the way. That's what the words ought to mean in practice.