Terms of Service

What dlectroflow is

dlectroflow is a web app for people whose brains do not do “just start it”. You capture whatever is rattling around, an AI helps break the daunting things into small concrete steps, you focus on one step at a time with a timer, and you get some credit for finishing. It can optionally push those steps into Google Tasks so a scheduling tool can book time for them.

These Terms cover the hosted instance at dlectroflow.dev. If you run your own copy of the software, these Terms do not govern it — see The code, the licence, and this instance.

This agreement, and who it is with

The agreement is between you and Dominique Top, an individual in the United Kingdom running dlectroflow as a personal, non-commercial hobby project— not a company, not a business, and not a trade. In these Terms, “I” and “me” mean that person, and “you” means you.

Because nothing is charged for, this is not a sale and you are not a customer. It is closer to being handed something someone made in their spare time — which is also why the sections on warranty and liability below read the way they do. It is not a disclaimer strategy; it is what an unpaid side project can honestly promise.

None of that reduces what I owe you about your data. See the Privacy Policy, which explains why being a hobby project does not exempt me from UK data protection law.

By using dlectroflow you accept these Terms. That applies whether you have an account or are using it as a guest — there is no separate tick-box, and using it is the acceptance. If you do not accept them, please do not use it.

It is free, and it is provided as is

dlectroflow is given away. There is no charge, no paid tier, no trial that turns into a subscription, and nothing to cancel — it is a hobby project, not a product.

What follows from that, stated plainly rather than hidden in a capitalised paragraph at the bottom:

• It is provided “as is” and “as available”, with no warranties of any kind beyond those UK law does not allow me to exclude.
• There is no uptime guarantee and no service level commitment. None. It is one small deployment looked after by one person, and there is no commercial arrangement here for a service level to hang off.
• There is no committed support. I will usually answer an email, but “usually” is the honest word.
• I do not promise it is free of errors, that it will meet your particular needs, or that any AI suggestion it produces is correct.

So please keep your own copy of anything that matters. There are nightly backups, but they exist for disaster recovery, not as a promise to you.

Who can use it

• As a guest, anyone can use it with no account. Guest workspaces are sandboxes: they expire after about a day and are then deleted, by design. Do not keep anything you care about in one.
• Accounts are invite-only. There is no sign-up form. Sign-in is through GitLab, and only identities on the allowlist can get in. I am under no obligation to grant anyone an account.
• You must be at least 13. dlectroflow is not intended for children under 13.
• Do not share your account, and do not use anyone else’s.

Your content stays yours

Everything you write into dlectroflow — your captures, tasks, steps and notes — remains yours. I claim no ownership of any of it.

You give me only the permission needed to actually run the service for you: to store your content, show it back to you, include it in backups, and send the parts described in the Privacy Policy to the AI provider when you ask for a breakdown. That is the whole licence. It does not extend to publishing your content, showing it to anyone else, or training any model on it.

That permission ends when you delete the content, or when your data is deleted at your request.

You are responsible for having the right to put content into the app in the first place, and for what you choose to put in it.

About the AI suggestions

This section matters more than most, so it is written properly rather than as boilerplate.

A suggestion, not an instruction

When the app breaks a task into steps, that list is a first draft. It has never met you. It does not know that Tuesdays are bad, that step three is the one you have been circling for a month, or that the whole task is really about one phone call you are dreading.

Argue with it. Reorder it. Delete half of it. Throw the whole thing away and write your own. That is not misuse of the feature — that is the feature. You are allowed to ignore it.

It is not professional advice

Nothing dlectroflow produces is medical, clinical, therapeutic, diagnostic, psychological, legal, financial or safety advice, and none of it is a substitute for talking to someone qualified. It is a to-do app with a kind tone. It does not assess you, diagnose you, or treat anything.

If something in your life needs a professional — a doctor, a therapist, an ADHD assessment, a solicitor, an accountant — please talk to one. Please do not let a tidy-looking list of steps be the reason you decide you have it handled.

Where being wrong would cost you

Do not rely on an AI suggestion for anything with real consequences: medication or dosing, legal or tax deadlines, medical appointments, money, or anything with a safety implication. Check those against the real source. The app will cheerfully suggest something wrong, and it has no way of knowing that it has.

If you bring your own API key

If you have an account, you can save your own API key for the AI provider in Settings. It is optional, and the app works without one. Two things follow, and both are yours rather than mine:

• Your key, your bill. Requests you make are charged to your account with the provider, and keeping the key valid and funded is up to you. If it stops working, breakdowns stop working — that is between you and them, and I cannot fix it from here. Remove the key in Settings and your account goes back to the shared allowance.
• Your agreement with the provider applies to it. Requests made on your key sit under whatever terms you accepted with them, not under mine, and you are responsible for complying with those.

What a key does not do is let you choose the provider. The key is used against the provider this instance is configured to use, and there is no setting for a different vendor, model endpoint or address — deliberately, since letting an account decide where the server sends requests would be a security hole rather than a feature. If you want a different provider, the software is open source and you can run your own instance configured however you like.

And a note on the hard days

The app is enthusiastic about streaks because that helps some people start. A broken streak is not a verdict on you, and a day where nothing got done is not a failure of anything the app can measure. It counts steps. It does not count worth.

Using it fairly

Please do not:

• break the law with it, or use it to store or share unlawful content;
• try to reach another workspace’s data, get around the invite allowlist, or use someone else’s account;
• attack or overload it — no denial of service, no attempts to break into the hosting, no automated hammering, and no routing around the rate limits and fair-use caps;
• resell, proxy or automate the AI feature for your own purposes. Unless you have saved your own API key, it runs on my API credentials and my money, and abuse of it is what would force a cap on everyone else. Bringing your own key lifts the allowance, not this rule — dlectroflow is not a gateway to resell;
• upload malware, or scrape the site;
• use it as a store for other people’s personal data at any scale. It is a personal task app, not a customer database, and I am not in a position to act as anyone’s data processor.

Security research is welcome.If you are looking for vulnerabilities in good faith and want to report one, the repository has a security policy explaining how. Please test against your own workspace, never anyone else’s data.

Your Google account is yours to look after

Connecting Google Tasks is optional, and the connection is yours: if you have an account you connect your own Google account, and dlectroflow writes tasks into yourGoogle Tasks rather than mine or anybody else’s. That account, and everything in it, remains your responsibility and is governed by your agreement with Google, not by these Terms.

Practically: check what it writes. The app creates and updates task titles and due dates in one list, and while it is careful to update rather than duplicate, you should satisfy yourself that it is behaving before you let a scheduler act on it. You can disconnect at any time in Settings, or revoke access from your Google account directly — and revoking at Google’s end always works, whatever state your account here is in.

I am not responsible for what any third-party scheduler does with those tasks once they are in your Google account, nor for changes Google makes to its own service.

Availability, changes, and shutting down

It will sometimes be down. Sometimes that is a deployment; sometimes something broke at two in the morning and I was asleep. There is no promised availability, and no compensation for downtime.

I may add, change or remove features, including ones you like. I may change the AI provider or model. Where a change materially affects how your data is handled, the Privacy Policy is updated and its effective date moves.

I may also shut the hosted instance down. If I decide to, I will give as much notice as I reasonably can, in the app and in the repository. Because the software is open source, you would not be left with nothing: you can run your own instance.

Suspending or ending access

You can stop whenever you like. Sign out, or ask me to delete your account and data.

I may suspend or end your access if you break these Terms, if your use threatens the service or other people using it, if I am legally required to, or if running the instance stops being sustainable. Where it is reasonable to do so I will tell you first and give you a chance to put it right; where the circumstances do not allow that, I may act immediately.

Being honest about what termination does not do: ending your access does not automatically delete your content today. Email privacy@dlectroflow.dev and it will be deleted — see the retention section of the Privacy Policy.

Limits on my liability

First, what I do not and cannot limit. Nothing in these Terms excludes or limits my liability for:

• death or personal injury caused by my negligence;
• fraud or fraudulent misrepresentation;
• anything else that cannot lawfully be excluded or limited under the law of England and Wales.

Your rights under UK data protection law are also untouched by anything here.

Subject to that, and because this is software given away as is rather than sold to you, to the fullest extent the law allows I am not liable for:

• indirect or consequential loss, or loss of profit, revenue, business, contracts or goodwill;
• loss of or damage to data, or the cost of reconstructing it — which is why the honest advice above is to keep your own copy of anything that matters;
• anything you missed, forgot, or got wrong while relying on the app or on an AI suggestion — a deadline, an appointment, a commitment;
• downtime, interruption, or the service being discontinued;
• the acts or failures of third-party services the app depends on or connects to.

Where liability cannot be excluded but can lawfully be limited, my total liability to you for all claims combined is limited to £100. A nominal cap rather than a pretence of none: this is software written by one person in their spare time and given away, and open-ended exposure would simply end the project. A clause claiming total immunity would be worth nothing to either of us, so I would rather write one that means what it says.

And one argument I am deliberately not making. Several of the rules that forbid excluding liability for death, personal injury or fraud are written to catch businesses and traders, and whether an unpaid hobby project counts as either is genuinely arguable. I am not going to run that argument. The carve-outs at the top of this section are stated flatly, they are not conditional on my status, and they stand whether or not those rules reach me.

The code, the licence, and this instance

The dlectroflow source code is published under the GNU Affero General Public License v3.0 (AGPL-3.0). You may read, run, modify and share it on those terms; the licence text in the repository is what governs, not this summary.

The licence covers the software, not this service. Having a licence to the code gives you no rights over this instance, its infrastructure, its API credentials, or anybody’s data on it, and it does not entitle you to an account here.

If you run a modified version and let other people use it over a network, AGPL-3.0 section 13 requires you to offer them the source of your version. The Source link in the footer of every page is how this instance meets that obligation for itself.

The name “dlectroflow” and the brand mark are not licensed for uses that suggest I endorse or maintain your version. Rename your fork and there is no issue.

Your data

How your data is handled is set out in the Privacy Policy, which forms part of these Terms. It covers what is stored, the lawful basis for each purpose, what is sent to the AI provider, how long things are kept, and how to exercise your rights.

For anything about your data, write to privacy@dlectroflow.dev rather than the general address — that inbox is the statutory route and it is monitored as one.

Governing law, and where disputes go

These Terms, and any dispute arising out of them or out of your use of dlectroflow, are governed by the law of England and Wales.

The courts of England and Wales have jurisdiction. If you live in Scotland or Northern Ireland you may also bring proceedings in the courts of the part of the UK where you live, and nothing in these Terms takes away any mandatory legal protection you have there.

Deliberately written without leaning on whether you count as a “consumer” and I count as a “trader”. Nothing is charged for here, so those labels sit awkwardly — and your right to sue where you live should not depend on how that argument comes out.

Changes to these Terms

The effective date at the top of this page is its version. If these Terms change substantively, that date changes with them.

The full, timestamped history of every word here is public in the source repository, so you can see exactly what changed and when. There is no in-app notification system yet, so the effective date and that history are the reliable ways to check.

Continuing to use dlectroflow after a change means you accept the revised Terms. If you do not, you can stop using it — and ask me to delete your data.

Odds and ends

• Severability. If any part of these Terms turns out to be unenforceable, the rest still applies.
• No waiver. If I do not enforce something straightaway, I have not given up the right to enforce it later.
• No third-party rights. Only you and I can enforce these Terms; nobody else acquires rights under them by virtue of the Contracts (Rights of Third Parties) Act 1999.
• Transfer. You may not transfer your rights under these Terms. I may transfer mine if the instance ever changes hands — and if that happened I would tell you, and it would not reduce your rights.
• The whole agreement. These Terms and the Privacy Policy are the entire agreement between us about dlectroflow.

Getting in touch

Two addresses, deliberately kept apart:

• admin@dlectroflow.dev — anything about the service: your account, access, a bug, or reporting abuse.
• privacy@dlectroflow.dev — anything about your data or your rights under data protection law.

They are separate because a data request comes with a statutory one-month deadline, and mixing it into general support mail is how such a deadline gets missed.