Skip to content
Back to OYLIW

Terms of Service — OYLIW (Offload Your Life in Weeks)

Last updated: 2026-08-16 · Version: 2.8 · See the changelog.

The short version

OYLIW is a free tool that draws your life as a grid of weeks. It runs in your browser. Your grid is yours. You can use it without an account, and most people should. If you make an account we'll keep a copy of your grid for you — including your birthdate and every date on the grid, exactly as you entered them. If you publish a grid it becomes public until you unpublish it, and the dates go public with it. If you ask us to write a life story from your grid, we send part of it to a language-model company and we promise you nothing about whether what comes back is true. The life-expectancy number is an assumption you choose, not a prediction about you. Please don't use the tool to harass anyone, and please don't expect it to be perfect.

1. What this is, and agreeing to it

OYLIW ("the service") is a web app provided by Offload Foundry ("we", "us") at oyliw.com. By using it, you agree to these terms. If you don't agree, please don't use it.

The service is currently provided free of charge.

2. The most important disclaimer: this is not a prediction

OYLIW is not actuarial, medical, insurance, financial, or health advice, and it is not a prediction of your lifespan.

The service draws a grid based on a life-expectancy figure that you set — it defaults to 90 years and you can change it. That number is a configurable assumption for the purpose of drawing a picture. It is not:

Nothing in this product knows anything about you beyond a date you typed in. Please do not treat the output as information about your mortality, and please do not make medical, financial, or life decisions on the basis of it.

If this product leaves you feeling distressed rather than reflective, please step away from it and talk to someone. If you are in crisis, contact your local emergency services or a crisis support line. We mean this sincerely — a memento-mori tool is a thing to be used lightly and put down.

3. Your grid is yours

You own everything you create — your milestones, your chapters, your labels, the arrangement of your life on the grid. We claim no ownership of it, no licence over it, and no right to use it.

If you use the service signed out — the default — we couldn't use your grid even if we wanted to: as described in the Privacy Policy, it stays on your device and never reaches us.

If you sign in and save a grid, we store a copy so we can show it back to you, and if you publish a grid we store and serve it so other people can open the link. That is a permission to operate the service you asked for, and nothing more. You keep ownership. We do not acquire the right to sell your grid, licence it to anyone else, use it in our marketing, or train anything on it. The permission lasts only as long as you keep the grid with us: delete it, or delete your account, and it ends.

Exports — the images you generate — are yours to keep, post, print, and share however you like, including commercially. The exports carry a small OYLIW watermark; please leave it in place, but that's a request about attribution, not a restriction on your use.

Our side: the OYLIW name, look, code, and design system belong to us. Please don't copy the app itself or pass it off as your own.

4. Attribution — whose idea this is

OYLIW is a build on an idea we did not invent, and we credit it prominently in the product itself:

We are not affiliated with, endorsed by, or partnered with either. The credit is a matter of intellectual honesty, and it stays in the footer.

5. Acceptable use

Please don't:

A note on grids about other people. The tool lets you make a grid for someone else — a child, a parent, someone who has died. That's a legitimate and often moving use. Please treat it with the weight it deserves: keep it private unless you have good reason not to, and think carefully before publishing a grid about a person who did not ask for one.

A note on grids you publish. Everything above applies with more force to a grid you publish at a public link, because you are then handing it to strangers rather than keeping it on your own machine. See §13 for the rules that apply specifically to published content, and §12.4 for what happens when they're broken.

We may block access if the service is being used in these ways. Where the use involves an account or a published grid we can act directly — unpublishing the grid, suspending or terminating the account. Where it doesn't, our ability to intervene is genuinely limited: a signed-out grid never reaches us, so there is nothing on our side to remove.

6. The service is provided "as is"

We offer the service as is and as available, without warranties of any kind, whether express or implied — including any implied warranties of merchantability, fitness for a particular purpose, accuracy, or uninterrupted availability.

Specifically:

Please keep your own copies of anything you care about by exporting it. This is the honest advice in both modes.

None of the above takes away a right you have that can't be taken away. If you're a consumer, your local law gives you things — that a service will be performed with reasonable care and skill, that digital content will be as described — which no disclaimer of ours can switch off, and we don't try to. Where the law says a term like this doesn't bind you, it doesn't bind you. See §7.

7. Limitation of liability

Please read this one. It says what you can and cannot get from us if this goes wrong.

We are not liable for indirect or consequential loss. That means: lost profits, lost opportunities, lost time, distress, or anything that follows on from a problem rather than being the problem itself.

We are not liable for the loss of your grids, your stories, or anything else you keep here, and there is no recovery service. Signed out, we hold no copy and cannot get one back (§6). Signed in, we hold a copy so it survives a cleared browser and a new device — but that is a convenience, not a guarantee, and we do not promise to be able to restore anything. What you keep here is often irreplaceable. Export what you care about.

Where we are liable, our total liability to you is limited to what you have actually paid us for the service in the twelve months before the problem — which, for the service as it stands, is nothing, because it is free. If a court decides that limit cannot apply, our liability is limited to the smallest amount the law allows.

Grids and stories that other people publish are theirs, not ours. We host what users choose to publish; we do not write it, check it before it goes up, or adopt it as our own. If something published here is unlawful or harms you, §13.4 is the route — a real person reads it, we act on genuine reports, and we take content down when a report is justified. We are not liable for content another user published, except to the extent the law makes a host liable once it has been told and has failed to act.

We do not exclude what cannot lawfully be excluded — liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or any consumer right that cannot be waived where you live. If a term here is unenforceable against you, it does not apply to you and the rest still stands.

Written by the person who runs the service, not by a lawyer. These terms have not been reviewed by outside counsel. We would rather tell you that than let the formatting imply otherwise.

8. Privacy

How we handle data is set out in the Privacy Policy, which forms part of these terms. The headline: signed out, your birthdate and your grid never leave your device; signed in, we hold a copy because that is what you asked for; and our analytics is anonymous and cookieless either way.

9. Age

There is no minimum age. Accounts, publishing, and purchases are open to everyone, and no age check runs anywhere — see Privacy Policy §9.

If you are old enough to be held to an agreement where you live, these terms are that agreement. If you are not, a parent or guardian is agreeing to them on your behalf by letting you use the service — and either of you can write to privacy@notify.offloadfoundry.com to have the account and everything attached to it deleted.

Given the subject matter, we'd suggest that younger users approach this tool with an adult around.

10. Governing law and disputes

These terms are governed by the laws of Singapore, and the courts of Singapore have jurisdiction. That is where the service is run from and it is the only country with a real connection to whoever is answering your email.

Two qualifications:

Please email first. Write to privacy@notify.offloadfoundry.com and describe the problem. Most things that reach a court could have been fixed by someone reading the message. There is no arbitration requirement, no class-action waiver, and no fee you have to pay to complain to us.

11. Changes to these terms

We may update these terms — to reflect a new feature, a change in the law, or a change in how the service works. What we won't do is change them silently and treat your next visit as agreement.

12. Accounts

You do not need one. The full tool — grid, milestones, chapters, exports, share links — works signed out, forever, and that is the default. An account exists for one reason: so your grid survives a cleared browser and follows you to another device.

12.1 Registration

12.2 Your responsibility for the account

Your Google account is the key to your OYLIW account, so keep it secure — that mostly means keeping it under your own control and not sharing access. You're responsible for what happens under your account. If you think someone else has got into it, tell us at privacy@notify.offloadfoundry.com and we can end all its active sessions.

12.3 What we do with a saved grid

We store it, we show it back to you, and we serve it at a public link if and only if you published it. Nothing else. See §3 and the Privacy Policy §2.2.

What "a copy of your grid" includes. All of it, as you entered it: your exact date of birth, and the exact date of every milestone and chapter. Dates are the substance of a life-in-weeks grid rather than incidental metadata, and we store them precisely because a grid that has been rounded off is not the grid you made. Earlier versions of this service stored a birth year instead and offered exactness as an opt-in; that is no longer how it works, and there is no longer anything to opt into. If you would prefer that we did not hold your exact dates, use OYLIW signed out — the default — where nothing is uploaded at all.

12.4 Suspension and termination

By you. Delete your account whenever you like, from Settings. It is a real deletion: your account record, your saved grids, your milestones and chapters, your sessions, and any published links all go, immediately and permanently. Published links stop working at once. We cannot undo it, and we cannot get it back for you afterwards — export anything you want to keep first.

By us. We may suspend or terminate an account, or unpublish a grid, if:

How we'll handle it. If we suspend an account, terminate one, or unpublish a grid, we will tell you — what we did, what specifically caused it, whether the ground was these terms or the law, and how to challenge it. That is not a best-efforts promise; it is something we owe you, and the only latitude we take is on timing: where there is serious or ongoing harm, a legal order, or a risk to someone else, we may act first and explain immediately afterwards. If you think we got it wrong, write to privacy@notify.offloadfoundry.com; a real person will read it, and we will reconsider rather than restate the original decision. We act proportionately — the usual answer to a bad grid is to unpublish that grid, not to close an account.

Effect of termination. Termination ends your right to use the account.

If we shut the service down, we'll give reasonable notice and a window to export your grids before anything is deleted. We won't just switch it off with your data inside it.

12.5 Written life stories

If you ask us to, we will write a short prose story from entries you pick out of your grid. It is optional, it is off until you ask, and everything below applies only to it.

How it is made. We send the labels you picked — your own words — and your age in whole years at each one to a language-model company, and we show you what comes back. We do not send your birthdate or any date on your grid. Before anything is sent you are shown a dialog naming the company and saying what leaves; nothing is sent unless you accept it. The Privacy Policy §6 names them and states, plainly, the limits of what we have agreed with them.

It is yours. A story we write for you is your content, on exactly the same footing as everything else in §3. We claim no ownership of it and no licence over it beyond storing it and showing it back to you. We will not sell it, publish it, put it in our marketing, or train anything on it.

We warrant nothing about it. A language model wrote it. It will sometimes say things about your life that are not true — not only wrong dates or invented details, which we check for and strip, but wrong meaning: a confident sentence about what a period of your life was like, or what one thing led to, that you never said and would not agree with. We do not warrant that a story is accurate, truthful, complete, fair, or a reasonable reading of anything. Please do not treat it as a record of your life, do not rely on it for anything, and do not give it to anyone else as fact. §2 applies to it with at least as much force as it applies to the grid.

We may occasionally pause story writing. If we do, it is our fault and not your limit. We keep an overall safety limit on how many stories the service writes, sized from what the people using it are entitled to write. It exists to catch something going wrong on our side — usage that our own records cannot explain, or someone abusing the feature. It is not a way of rationing what you have paid for, and in a normal month it does not come near you. If it stops you writing a story, we will say so in those words: the service is paused, your own allowance has not been touched, and nothing on your grid has changed. If it ever costs you something you had paid for, tell us at privacy@notify.offloadfoundry.com and we will put it right.

It is content under §13 if you ever make it public — but you cannot make it public here. Publishing a grid does not publish its story, there is no setting that does, and the public page never carries one.

What happens to it. We keep a story until you delete it — there is no expiry, and nothing removes it on a timer. Four things delete one, all of them yours and all of them immediate: deleting the story, deleting the grid it belongs to, deleting your account, or the "withdraw permission" control, which deletes every story we hold for you, on every grid, at once. ⚠️ That is the trade: do none of those and we hold the text indefinitely. This replaces the 90-day deletion promised by v2.4 and v2.5 — see the Privacy Policy's section 8 for what that gains you and what it costs you. Deleting your account destroys stories in the same operation that destroys everything else, not afterwards and not on request. What the language-model company does with what we sent them is governed by their terms, not ours, and the Privacy Policy says so.

13. Published grids

Publishing puts a read-only copy of a grid at a public link that anyone with the link can open. It is off by default, chosen per grid, and reversible.

13.1 What you're confirming when you publish

Publishing a grid publishes the dates in it. A published grid shows the exact date of birth it is drawn from and the exact date of every milestone and chapter on it, to anyone holding the link. There is no setting that publishes the picture and withholds the dates — the dates are the picture. By creating a share link you accept that those dates become publicly available, for as long as the link is live and, realistically, for as long as anyone who opened it keeps what they saw. If that is not acceptable to you, do not create the link: your grid stays private, and every other part of the product works without it.

Beyond that: that you have the right to publish it, and that publishing it is a decent thing to do. Concretely:

13.2 Content standards

A published grid must not contain content that is illegal, hateful, harassing, defamatory, sexually explicit, sexually exploitative of minors, or that promotes self-harm or violence. Labels and chapter names are content: the same rules apply to a chapter title as to anything else you'd publish on the internet.

13.3 Search engines

We ask search engines not to index published grids, so they shouldn't appear in search results. That's a request, not a guarantee — we control what we ask, not what every crawler does.

13.4 Unpublishing and takedown

14. Placeholders — coming with later phases

These sections do not exist yet because the features do not exist yet. They will be added when they ship:

15. Contact

Questions about these terms: privacy@notify.offloadfoundry.com (mark it "Legal").

Version history

Version Date Change
2.8 2026-08-16 Editorial only — no term, right or obligation changes. Sentences in which the document commented on its own writing rather than stating a term (§6 "Specifically, and honestly", §7's opening line about the section being skipped, §10's "because a clause like this is often written to sound like more than it is", §12.5's "and this is not boilerplate") are cut or shortened. Every operative clause is untouched: the exclusions and the cap in §7, the Singapore clause and both of its qualifications in §10, the no-warranty and retention wording in §12.5, and the §13.4 takedown commitments all read exactly as they did in v2.7. A non-material change under §11.
2.7 2026-08-11 A named limit on how many stories the service writes, and a promise about what it is not. §12.5 gains a paragraph: there is an overall safety limit, it is sized from what subscribers are entitled to write, it exists to catch a fault or an abuse on our side, and it is not a way of rationing what you have paid for. Published now, before anything is sold, because a term like this has to be read rather than discovered — and published in the narrow form because owner decision D11(a) made the limit derive from live entitlements, so it can only trip on a fault. The clause commits us to three things a bare reservation of rights would not: to say plainly that the pause is ours, to leave your own allowance untouched, and to put it right if it ever costs you something you paid for. Owner-written, not counsel-reviewed (D7), like the rest of §7 and §10. No existing term, right or obligation is weakened — §6 and §7 are untouched, and the clause gives you a commitment where there was previously silence.
2.6 2026-08-11 Written life stories are no longer deleted after 90 days. §12.5's retention paragraph is rewritten: a story is kept until you delete it, and the four things that delete one — the story, the grid it belongs to, your account, or withdrawing permission — are listed with the note that doing none of them means we hold the text indefinitely. This gives you more and protects you less, and the clause says both. §6's bullet needed no change — it is about accuracy, not retention, and it is untouched. ⚠️ One promise that v2.4 made was not being kept and now is: deleting a grid was stated to destroy its stories immediately, but a deleted grid is retained so it can be restored, so nothing was actually removing them until the 90-day sweep caught up. That sweep is gone and an explicit deletion has replaced it. No other term, right or obligation changes — ownership, the no-warranty clause, and the rule that publishing a grid never publishes its story are all unchanged. Corresponds to Privacy Policy v3.1.
2.5 2026-08-10 The placeholders are gone, and what replaced them is owner text. Owner decision D7 — there will be no legal counsel — so §7 and §10 are written out plainly instead of waiting: §7 states an actual position (no indirect loss, no data-preservation guarantee and no recovery service, total liability capped at fees paid, which is zero, hosted content is the publisher's with §13.4 as the route, mandatory rights untouched) and ends by saying in the published text that these terms were not reviewed by a lawyer; §10 names Singapore law and courts and then qualifies it twice — it does not displace your local consumer protections, and nobody has assessed whether it survives a challenge elsewhere. Two [TBD]s become numbers: the §11 change-notice period and the §12.4 export window are both 30 days. The §13 Digital Services Act block is kept but relabelled — its "still open for counsel" list is now accepted unreviewed, which is not the same as closed. §14 no longer says the payments section is counsel-drafted. §12.5 needed no change: the story's ownership and no-warranty clauses were already written. No user-facing commitment was weakened in this revision.
2.4 2026-08-10 Written life stories. New §12.5, covering an optional feature that sends labels you wrote and your whole-year ages to a language-model company and shows you the prose it returns. Four things are settled in it: the story is yours (§3's terms, unchanged — no ownership, no licence, no training, no marketing); we warrant nothing whatsoever about its accuracy, and the clause says outright that it will sometimes be wrong about your own life in ways an accuracy check cannot catch — not merely that it is "AI-generated"; publishing a grid does not publish its story, and no setting exists that would; and it is kept 90 days, destroyed immediately on withdrawal of permission or deletion of the grid or account. §6 gains a matching bullet and the short version gains a sentence. No existing term, right or obligation is altered — this covers a feature that did not exist when v2.3 was written. Corresponds to Privacy Policy v2.9.
2.3-r1 2026-08-09 First publication. These terms are now served at /terms, rendered from this file at build time — the same arrangement the Privacy Policy has at /privacy, so the document legal reviews and the document you read are one file. No term, right or obligation is altered by publishing it. The team's working notes — the counsel items still open on §7 (liability), §10 (governing law) and §13 (DSA duties), and the drafting placeholders in §11 and §12.4 — are stripped from the published page rather than resolved; they remain open, and remain in this file. One clarification is published with them: §11 now states that the change notice will say when the change takes effect, which is what the notice period bullet was waiting on. A non-material change under §11.
2.3 2026-08-09 Controller name changed to Offload Foundry. The controlling entity is unchanged — same company, same contact addresses, same processing; only the name it trades and is identified under has changed, from "Offload Solutions". §1 and the §13 counsel note updated. A non-material change under §11 — no term, right or obligation is altered. Corresponds to Privacy Policy v2.8.
2.2 2026-08-04 Exact dates, and what publishing one means. A saved grid now stores your exact date of birth and the exact date of every milestone and chapter, replacing the birth-year storage and the exact-date opt-in described in v2.0–2.1. §12.3 says what "a copy of your grid" includes and points anyone who would rather we did not hold it at the signed-out mode. §13.1 now opens with the consequence: publishing a grid publishes the dates in it, creating the link is how you accept that, and there is no setting that publishes the picture while withholding the dates. The short version and the "grid about someone else" bullet carry the same warning, because someone publishing a grid about a partner or a child is publishing that person's date of birth. Corresponds to Privacy Policy v2.6.
2.1 2026-07-30 Age restriction removed. The service is safe for all ages, so §9 no longer excludes under-16s from accounts, publishing, or purchases, and the automated age check it described is gone from the product. §9 rewritten around capacity to agree rather than a threshold, with a deletion route for a parent or guardian. §12: "the account holder turns out to be under 16" removed from the grounds for termination. §12 account rules: the 16+ warranty dropped. §13 counsel note: the under-16 block is no longer cited as exceeding DSA Art. 28.
2.0-r1 2026-07-27 Compliance review pass. §6: "change, break, or discontinue at any time without notice" was both indicatively unfair (UCTD Annex 1(f)/(g)) and contradicted §12.4's shutdown-notice promise — now subject to §12.4; added the mandatory-rights carve-out that §6 lacked. §9: disclosed the age check as automated with a route to contest it. §11: unilateral change now requires advance in-product notice and preserves a right to leave, instead of treating continued use as consent (UCTD Annex 1(j), DSA Art. 14(2)); notice period [TBD]. §12.4: statements of reasons made mandatory rather than best-efforts (DSA Art. 17), proportionality stated, and an export window added where we terminate. §13.4: added acknowledgement of receipt and notification of decision with redress information (DSA Art. 16). §13 counsel-review block narrowed to the duties that genuinely attach at micro/small size, with the Art. 19 and Art. 15(2) exemptions identified and the residual questions listed.
2.0 2026-07-27 Accounts and published grids. Added §12 (registration, account security, suspension/termination and its effects, shutdown notice) and §13 (publishing consent, content standards, search-engine posture, unpublishing and takedown), filling the v1.0 §12 placeholders. Revised §3 (a limited operating permission for hosted grids, no ownership transfer), §5 (enforcement is now real for accounts and published grids), §6 (a saved copy is not a backup guarantee), §8, §9 (server-side age check, 16+ warranty). Added a second counsel-review block to §7 for hosted-content liability. Governing law (§10) remains a counsel placeholder. Not yet published.
1.0 2026-07-23 Initial Phase 0 terms. Free on-device tool only. Governing law (§10) and liability wording (§7) left as counsel placeholders.