Should Your Invoices Live in Dropbox?

After the backup article I keep getting the same email: "Vlad, I already pay for Dropbox. Can't the invoices just live there?" Short answer: yes, as one copy. No, as the only one. The long answer is this page.

Key takeaways

The question is not where. It is who.

"Where should my invoices live?" feels like a practical question. It hides the real one: who can read them, change them, delete them, and charge you for the privilege?

A folder on your disk answers all four with "you." A cloud account answers them with "the vendor, and you too." That is not an argument against the cloud. It is an argument for knowing which one you chose.

Run the Cloud Trap check on your storage: if the vendor disappears tomorrow, can you still read your history? If the answer is no, your invoices are guests in someone else's house. Sovereign data means the opposite: your business files answer to you.

I have watched a freelancer keep five years of invoices in one Dropbox folder. It worked. Right up to the first sync conflict after a laptop change. Then the folder showed three versions of the same database, and none of them opened. The cloud had done its job perfectly. The job just was not his.

When the cloud is the right call

I do not hate Dropbox. I hate unexamined defaults. The cloud earns its place in specific roles:

Notice the pattern. In every good role, the cloud holds a copy or an export — never the original. The full argument for the copies is in the backup problem article.

Why Dropbox alone is not enough for invoice storage

The problems start when the copy becomes the home:

And the vendor risk list is not theoretical: a forgotten password, a suspended account, a pricing change, a provider shutdown, a deleted file. Any one of them, and a cloud-only setup becomes an evening of reconstruction.

Why sync and SQLite do not mix

SQLite expects exclusive write access to its file. A sync client copies files block by block, on its own schedule, sometimes from two machines at once. Those two models do not meet well. The sync tool sees a file. SQLite sees a transaction. When they disagree, the file loses.

Some free services also analyze usage data or build revenue on behavioral data. Read the privacy policy before your financial history becomes part of that model. That is vendor lock-in in its quiet form — and the opposite of data portability.

The 3-2-1 rule: local primary, cloud copies

One rule settles every version of this question: the primary lives local; the cloud holds copies.

  1. Primary: a local database or folder you fully control.
  2. Copy two: an external drive on your desk.
  3. Copy three: an encrypted export in Dropbox, Drive, or OneDrive. The brand does not matter.
  4. Sync exports and closed PDFs. Never the live database file.
  5. Once a quarter, restore one file from the cloud copy and check it. Verification, not possession.
Original records: local Working database: local Backups: local + external + cloud Exports and PDFs: cloud is fine Archive: cloud is fine Live SQLite file: never synced

That is the whole setup. It costs one external drive and five minutes a season. Offline-first primary, plain-text exports, and the cloud demoted to what it is good at: being somewhere else.

Moving everything out of a single Dropbox folder

If your current setup is "everything in one Dropbox folder," the fix is an afternoon, not a migration project. See how a local primary works >

The decision matrix

Dropbox vs local, property by property
PropertyLocal diskDropbox as the only copyDropbox as one of the copies
Works without internetYesNoYes — the local copy works
Vendor can lock you outNoYesNo
Provider holds the keysNoYesNo, if the archive is encrypted
Survives a disk fire or theftNoYesYes
Good as primaryYesNon/a
Good as offsite copyn/aRiskyYes
Dropbox in each role: the verdict
Your situationVerdict
Encrypted exports as the offsite copyYes — that is what offsite means
Shared folder of PDFs for the accountantYes — output, not source
The only place your invoices existNo — one password from disaster
Live database file under syncNever — sync corrupts live databases
Working documents you edit with othersFine for the draft; the signed copy lives local
Bad and good storage architecture Bad: Dropbox holds the database, invoices, and backups — everything. Good: a local SQLite primary with an external drive copy and encrypted exports in Dropbox. BAD: the cloud is the home Dropbox database + invoices backups — everything one password from disaster GOOD: the cloud is a copy SQLite local (primary) external drive encrypted exports in Dropbox primary, then copies

Primary > copies. Not copies > primary.

What LockMargin does here

LockMargin keeps the primary on your machine: a local SQLite database, encrypted, in open formats. It does not sync, on purpose. It exports CSV, JSON, and PDF — exactly the files your cloud copy should hold. The division of labor is honest: your machine owns the record; the cloud holds a spare. The three-level automatic backup system behind that primary is documented in How We Built a Backup System Nobody Asked For.

Honest limits: no mobile app, no real-time sync. If those are your real need, the cloud is your answer — just go in knowing it is rent. The storage side of this argument is in Own Your Data.

The cloud is a fine copy and a bad home.

If your invoices hold client data that deserves extra care, read the GDPR guide. And if you want the philosophy behind "primary local," it is in the manifesto.

Questions freelancers ask

Is Dropbox a good backup for invoices?

Yes, as one offsite copy among several. No, as the only one. The cloud earns its place as the offsite copy in a 3-2-1 setup, not as the home of your records.

What is wrong with keeping invoices only in the cloud?

Control. A suspended account, a forgotten password, or a terms change can sit between you and your history. If the vendor can delete, lock, or read your files, your records are guests in someone else's house.

Can a cloud provider read my invoices?

By default, yes. Dropbox, Google Drive, and OneDrive encrypt your files, but they hold the keys — so they can decrypt for support, legal requests, or a breach. Client-side encryption, where only you hold the key, is the exception you have to configure.

Should I sync my accounting database to Dropbox?

No. Sync tools copy files in the middle of transactions and write them back from two places. That is exactly how live databases get corrupted. Sync exports and closed copies, never the live file.

What is the simplest safe setup?

A local primary you control, an external drive on your desk, and an encrypted export in any cloud folder. Once a quarter, restore one file from the cloud copy and check it.

Does this apply to Google Drive and OneDrive too?

Yes. The brand is not the issue; the model is. Any service where the vendor holds the keys and the terms behaves the same way.

How long should I keep invoices as a freelancer?

Keep invoices and supporting records for as long as your tax authority can ask about them — commonly three to seven years depending on the country. After that window, keep the archive anyway: it is your business memory, and storage is cheap.

Is Dropbox GDPR compliant for client invoices?

Dropbox offers GDPR tools such as DPAs and EU storage options, and compliance is shared: the provider secures the infrastructure, you control what you upload and who can access it. For sensitive client data, encrypt before upload or keep it local. The obligation stays with you.

Vlad (Volodymyr) Shiyan, founder of LockMargin

About the Author

Vlad (Volodymyr) Shiyan — Founder & Developer, Kharkiv, Ukraine. Building LockMargin since December 2025. Offline-first invoicing for freelancers who are tired of subscriptions. Standard is $49 one-time. Read more about Vlad →

Get one practical guide each month on building a business you own

No spam. No fluff. Unsubscribe anytime.

Back to top ↑