If Okidoky ever stops, your data doesn't depend on us
A fair concern with any online service: 'what if they stop tomorrow?'. That's why we put in writing here what happens to your data then — including that, as a last resort, we make the code public.
Many apps have already shut down
Over the past years, many popular apps have shut down — sometimes with 30 days warning, sometimes overnight. Users lost years of data. Three examples that affected many people:
Mint (Intuit)
15M+ users. Announced November 2023, closed March 2024. Intuit pushed users to Credit Karma, many found no alternative.
Multiple coffee apps
Loyalty apps from coffee chains were often acquired, replaced or closed. Balances vanished or had to be used up within weeks.
Small SaaS tools
Many freemium productivity tools (Wunderlist, Sunrise, Mailbox) have closed since 2015. Usually after acquisition by a larger party, followed by a brief wind-down of a few months.
The best protection: choose an app you can always download your data from, and that tells you honestly what happens if it stops.
A ladder of protection
Instead of one promise, we have three layers. Each for a different situation weight — the more serious the loss, the deeper the protection.
180 days advance notice
If we decide to stop (for any reason), all active users receive an email and in-app notification at least 180 days in advance. Time enough to choose alternative.
- Email to your account address with closure date and next steps
- Prominent notice on website AND in app — no hidden announcement
- Reason explained: succession, financial, personal choice of owner
You can always download everything
During those 180 days (and always before, too) you can download all your data. Not just transactions — everything you put in. No 'premium download' or half overviews.
- A file you open straight away in Excel or Google Sheets
- A second file type for those who want to do something technical with it
- A PDF with yearly overviews and charts — handy for the treasurer
Make the code public (last resort)
If steps 1 and 2 aren't enough — for example because you want to keep using Okidoky but without us — then we make the full code public. Someone with technical know-how can then run Okidoky themselves.
- The part that runs on the server — works on a cheap server
- The part you see in your browser — you can put it online yourself or have it hosted
- Instructions to install it yourself — up and running within half an hour
What we would and wouldn't make public
Not everything can be public. Here's what would and wouldn't.
This we would make public
The server side
The part that runs on the server: your transactions, logging in, and reading receipts. With terms that allow reuse.
The side you see
All the pages and screens you use in your browser, including the translations. Same terms as the server side.
Instructions to run it yourself
Step-by-step instructions to set everything up yourself, including backups. Well tested before we release it.
A ready-to-use package
A package with everything already set up, so installing is easier.
Could we do this tomorrow? Technically yes. Are we doing it now? No. It's a promise for if we ever stop, not something for today.
Not this
Secret security keys
The secret keys that keep everything secure. Releasing those would put every account at risk, and you don't need them — whoever runs it themselves makes their own.
Customers' data
Of course not. Everyone can download their own data (step 2). Our database contains data from thousands of people and stays confidential.
The name and logo 'Okidoky'
Making the code public isn't the same as giving away the name. Whoever takes over the code picks their own name — that prevents confusion and misuse of the brand name.
In short: everything you need to continue, YES. Everything that's unsafe or could be misused, NO.
What a shutdown would concretely look like
If we ever decide to stop, the planning looks like this. Exact dates we'd announce then, but this is the rhythm.
- T-180 days
Public announcement
Email to all active users + banner in app + news post on website. Reason explained. Next steps per user.
- T-90 days
Make the code public (if step 3 is needed)
The full code goes public online, with instructions to run it yourself. We keep repeating that this is an option. Only applies if steps 1 and 2 aren't enough (e.g. we stop because we're starting something new).
- T-30 days
All-users migration reminder
Last email: 'you have 30 days to export your data'. Insisting on attention — nobody should lose data through oversight.
- CLOSURE
Server closure
App is no longer accessible. Data is still preserved (backups + production DB), but nobody can log in anymore. No new registrations, no payments, no support.
- T+180 days
Permanent deletion
180 days after closure: all user data is permanently deleted from our servers (including backups). This extra 180 days gives room for last forgotten exports.
But honestly: how likely is this?
Not likely short-term. Okidoky has no investors wanting their money back, is built by RULIDO, and runs on its own servers — no cloud company that suddenly pulls the plug.
But not impossible either. Things happen. The owner might want to retire in 15 years. An acquisition offer might come. A personal circumstance can change everything. We're humans, not immortal corporations.
We think about this seriously, precisely because we want you to feel at ease about your data.
Frequently asked questions
Why not open-source right now?
Good question. A few reasons: 1. The business needs to stand on its own feet first. 2. Managing the code in public takes a lot of time — we'd rather put that into improving the app now. 3. The code works well, but isn't fully ready yet for others to help with. Our plan: someday, when the business is stable, we'll look again. Not ruled out — but no deadline.
Can I help with Okidoky if the code becomes public?
If we stop: yes, the code is then free and you can change it however you like. It then continues without us. While we're still running: no, we currently don't accept changes from outside. The code is managed by RULIDO itself.
What if you get acquired by a larger company?
Acquisition without quality loss is our preference but not a promise. If we ever get sold: • We commit in the purchase agreement that this open-source promise gets taken over • Existing Lifetime customers always retain access under same conditions • Users get 90 days to leave if they don't want to continue with new owner Note: we have no active acquisition conversations. This answer is purely theoretical.
On what terms would the code be released?
On terms that let others run Okidoky themselves, including commercially. We'll make the exact choice at the time itself.
Have you already put in writing what should happen?
Yes. RULIDO has recorded with a notary what should happen to Okidoky (and other products): who gets access to the servers, who gets informed, and how everything is wound down neatly. This is a real, formal document. We keep the exact content private for privacy reasons.
Your data stays yours
This promise is here to let you be sure: your data is yours — today, tomorrow, and also if we're ever no longer here.