Privacy Terms
Sign in

Terms of Service

Last updated 2026-07-31 Applies to brickdocket.com and the BrickDocket app Operated by Otron_TV

Effective date: 2026-07-31 · Version 1.0

Read these Terms alongside the Privacy Policy, which forms part of them. Where these Terms describe what data goes where, the Privacy Policy is the fuller version.

These are the terms for using BrickDocket at brickdocket.com. They are written to be read, not skimmed past. If something here is a limitation, it is written as one.

1. Who provides BrickDocket

BrickDocket is made and run by one person: Otron_TV. There is no company behind it, no team, no support desk and no legal department. When these Terms say "I", that is who it means. When they say "you", that is the person using BrickDocket.

You can reach me at otrontv@gmail.com.

2. BrickDocket is free

BrickDocket costs nothing. There is no fee, no subscription, no paid tier, no advertising, no in-app purchase and no upsell.

Free does not mean guaranteed. It does not entitle you to continued availability, to any particular feature staying, or to a support response. I build this because I want it to exist, and I will keep it honest, but I am not promising you a service level I cannot personally staff.

3. Accepting these Terms

Using BrickDocket means you accept these Terms. If you do not accept them, do not use it.

4. Age

You must be at least 13 years old to use BrickDocket.

If you are under the age of majority where you live, or the law where you live sets a higher age for agreeing to online terms, you may use BrickDocket only with the permission of a parent or legal guardian, and they agree to these Terms on your behalf.

Some optional features rely on your consent rather than on what BrickDocket needs to work — away-delivery, Discord webhooks and ntfy push. In parts of the EU and EEA, the age at which you can give that consent for yourself is 16 unless national law lowers it, and it can be as low as 13. If you are under the age at which you can consent for yourself where you live, a parent or guardian must approve those optional features. The core app does not depend on them and works fine with all of them off, which is how they ship.

If I find out an account belongs to someone under 13, I will close it and delete the server-held data attached to it — the account record, uploaded files, published snapshots and grants, and any away-timer schedule with its credentials. A parent or guardian can ask me to do the same at otrontv@gmail.com and I will act on everything I can reach. I will also explain what sits only in that child's own browser, which section 9 means I cannot touch, and how to clear it.

Your clients may be children too. Roblox commissioning is full of minors. Record only what you actually need about a client — a handle and a project note is usually enough. Never record a child's real name, home address, school, photograph, phone number, or any government or payment identifier. That is a rule of these Terms, not a suggestion.

5. Your account and sign-in

You sign in with an identity provider: Google, Discord or Roblox. The sign-in page shows which providers are live at any given moment; that set can change.

BrickDocket never sees, receives or stores your password for any of those services. The password exchange happens entirely on the provider's own site, and BrickDocket offers no email-and-password sign-in of its own.

Because of that, I cannot recover your provider account, reset it, unlock it, or vouch for you to Google, Discord or Roblox. If you lose access to the account you signed in with, you lose access to the BrickDocket workspace attached to it. Keeping that account secure — and keeping its recovery options working — is on you.

One person per account. Do not share your sign-in with someone else. Everything done under your account is treated as done by you.

6. What BrickDocket is

BrickDocket is a record-keeping tool for people who take commissions. You write down clients, projects, priced tasks, deadlines and notes. It totals things up, tracks what is done and what is paid, and gives you a link you can send a client so they can see their own project.

That is the whole product. It is a notebook that does arithmetic and publishes a page.

7. BrickDocket never touches money

This is the most important clause in this document, so it is stated plainly and without hedging.

BrickDocket never handles, holds, receives, transmits, escrows, releases, refunds, reverses, converts or guarantees any payment, in any currency, ever. Not fiat, not Robux, not cryptocurrency, not gift cards, not anything else.

BrickDocket is not:

Every payment happens off-platform, directly between you and your client, using whatever method the two of you chose. BrickDocket records what you tell it happened. When you mark a task paid, that is you making a note. Nothing was verified, nothing was collected, and no money moved through anything I run.

Totals, priced-task figures, balances and anything that looks like an invoice are documents you generated for your own reference. They are not a bill, not a receipt, not proof of payment, not a contract, and not financial, tax or legal advice.

BrickDocket has no access to your Robux balance, your Roblox transactions or your Roblox account beyond the two read-only profile scopes in section 23. It does not facilitate the sale, purchase or exchange of Robux, Roblox accounts, items or in-experience content.

If there is a dispute about money, scope, delivery, quality or a refund, it is between you and your client. I am not a party to it, I have no role in resolving it, and I will not mediate, arbitrate, adjudicate, hold funds, freeze anything, take sides or act as a witness. I have no record of your dealings to produce even if I wanted to — see section 9.

8. Currency conversions are indicative only

BrickDocket can show a US dollar reading beside an amount priced in Robux or in cryptocurrency. Those readings are estimates. They are not prices, and nobody is billed one by me.

Robux. The dollar reading uses a fixed default of $0.0035 per Robux ($350 per 100,000) — the Developer Exchange cash-out rate Roblox published when this was written. It is a constant baked into the app, not a live lookup, so if Roblox changes its rate the app keeps showing the old one until I update it. You can also replace it with your own figure in Settings, and if you do, that figure is what your client's page shows too. DevEx is what an eligible creator receives on cash-out; it is not what a buyer pays to purchase Robux, which is several times higher, and it only applies if you meet Roblox's eligibility requirements. Treat any Robux-to-dollar figure as a rough orientation and nothing more.

Cryptocurrency. The dollar reading comes from a live third-party market rate fetched from Coinbase. It can be delayed, cached, stale, unavailable, or simply wrong. Crypto prices move while you are reading them.

BrickDocket does print a converted figure to your client. When a commission is priced in dollars and you list a crypto wallet, the client's page shows a live coin amount beside that address. That figure is generated from a third-party rate at the moment the page is drawn, it does not include network fees, and it will not match by the time a transfer settles. It is not an invoice and I do not stand behind it. The amount your client owes is the amount you and your client agreed, in the currency you agreed. If you do not want a converted figure on your client's page, turn it off in Settings.

9. Your records live in your browser, and that has consequences

Everything you create in BrickDocket — your clients, commissions, tasks, prices, notes, settings — is saved in your web browser's local storage, on the device and browser profile you are using. It is not copied to a server. There is no account database holding your records, no nightly backup, and no support tool that can look them up.

That is true of your records. It is not true of everything: files you upload, the snapshot behind any client link you publish, and your away-timer schedule if you switch it on are all held on my servers, because they have to keep working when your browser is closed. Section 10 lists them, and section 24 covers removing them. Read this section as being about your records specifically.

This means, as a term of this agreement:

Backups are your responsibility. BrickDocket has an export button that works in every browser, and an automatic backup that rewrites one file on your own disk on a schedule. Automatic backup needs the File System Access API, which today means Chrome and Edge only — Firefox and Safari cannot do it, and on those browsers Export is the whole of your safety net. Even where it works, automatic backup only runs while a BrickDocket tab is open, and after a browser restart it will silently wait for you to re-allow access to the file. Check Settings occasionally to confirm it actually ran. Export regularly regardless, and keep the file somewhere other than the same browser — a cloud drive, an external disk, an email to yourself. Restoring is done by importing that file. If you do not keep a backup and you lose your browser data, that outcome is yours to bear, and this section is the notice that made it foreseeable.

10. The things that do leave your device

The local-first story is real but it is not total, and pretending otherwise would be false. These specific things leave your device, and only these:

No per-link preview card is uploaded or stored anywhere. When a client link is opened at brickdocket.com/p/<token>, the page is served with BrickDocket's generic preview card; the title, description and thumbnail you configure for it stay in your browser.

The Privacy Policy sets all of this out in full, item by item, including exactly what a snapshot contains and what is deliberately left out of it.

A client link is a URL you create and send. You decide who gets one, whether it covers one commission or every commission you have for that client, which files are released, whether it needs a passcode, and when it expires.

Understand what a link is: anyone holding the URL can open it, subject to the passcode and expiry you set. It is unlisted, not secret. If your client forwards it, the person they forwarded it to can open it. Search engines are told not to index it, which keeps it out of results but does not make it confidential. Never post a client link publicly.

What a link shows the holder: your studio name and branding, your payment destinations (including PayPal, Stripe or Ko-fi URLs, Cash App handles, and crypto wallet addresses and networks), that one client's name and emoji, and the commission itself — title, status, deadline, brief, tasks and add-ons with their prices, paid flags and any note you attached to the line, the revision allowance for that commission, milestones, updates, approvals, revisions, reference images, external links, and every file row — including ones you are still holding back, which appear by name, size and version and are marked as held. Only the contents of a held file are withheld, not the fact that it exists. Your private commission notes, your client's contact details and private note, your integrations, and every other client's work are not in it. A client-scope link covers all of that one client's active commissions, so check the scope before you send it.

Links always expire. The storage service forces a ceiling of thirty days from the moment a link is published, and a link you keep working with keeps refreshing its own window. Revoking a link deletes the grant, the snapshot and the queued client messages together, immediately.

Two limitations worth knowing before you rely on deletion:

Your client cannot reach your records directly. What they do on the page is written to a short queue on my server; your app collects it and applies it on your own device. Applying is automatic, not a request you approve one by one — a client approving something marks it approved in your records, and a client requesting changes moves the commission to "revisions", spends one of that commission's revision rounds, and adds their message to its history. Your app re-checks the revision ceiling against your own data, so a client cannot spend more rounds than you allowed. Anything queued is deleted the moment you collect it.

You do not need an account to open a client link, and opening one does not make you a BrickDocket user under these Terms. What you should know:

The page was created and filled in by the creator who sent you the link, not by me. Everything on it — including any payment address — is theirs. I do not check it, verify it, endorse it or guarantee it, and I am not a party to whatever you and that creator agreed.

Before you pay anyone, confirm the payment details with the creator through a channel you already trust. A link can be forwarded, and a page can be shown to you by someone who is not the creator. I never handle payments (section 7), so a payment made on the strength of one of these pages is entirely between you and them.

The page is provided as is, with no warranty, and to the extent the law allows I have no liability to you arising from it.

If your own information appears on a page and you want it corrected or removed, or you think a page is fraudulent or abusive, email otrontv@gmail.com. I will act on what is held on my servers, and I will tell you honestly what I cannot reach.

13. Watermarking is a deterrent, not protection

BrickDocket can stamp your own mark onto images you upload. It happens entirely in your browser; on success the original never leaves your device and only the marked copy is stored.

Marking is destructive. The stored copy is also downscaled and re-encoded — by default the longest edge is capped at 1,600 pixels and the file is re-saved as WebP at reduced quality — and your original is not kept. Keep your own copy of every source file. BrickDocket is not an archive of your work.

A watermark does not protect an image. It can be cropped, painted out, cloned away, or removed by anyone who wants to badly enough, and tools for doing so are freely available. All it does is raise the effort and make casual reuse obvious. It does not make an image safe to hand to someone you do not trust. Do not treat a watermark as a substitute for withholding the final file until you have been paid — which is what the release control is for.

By default, files you tick as final delivery on the drop zone are not watermarked. That is a setting, not a guarantee: Settings offers "Every image, finals included", and if you choose it your finals are marked too. The decision is made at upload time from the final-delivery checkbox — ticking "final delivery" on a file after it has been uploaded does not undo a watermark, because the original was not kept.

Only ordinary raster images are marked — JPEG, PNG, WebP, AVIF and BMP. GIF, APNG and SVG are refused on purpose, and anything that is not an image is stored exactly as you uploaded it, unmarked. If the marking fails for any reason, your original is stored untouched rather than lost.

14. Timers and notifications are best-effort

Timers are a convenience. They are not a scheduling guarantee.

While the app is open, timers run in your browser, and a browser that is closed, asleep, backgrounded, throttled, or on a device that is off will not fire anything.

Away-delivery is the opt-in switch that lets a reminder fire with the tab closed. Turning it on uploads a schedule to the storage service. What goes up is the reminder itself: its time, its title, and its body — which is the note you typed on the timer, plus that commission's title if the timer is attached to one — along with a repeat interval, an expiry, a link back to your own timers page, and the delivery addresses: your Discord webhook URL and your ntfy server, topic and token. Your commissions, clients, prices, private notes and files stay in your browser and are never uploaded for this. Switching away-delivery off deletes the whole schedule, including those credentials; if that delete fails, the file stays until a later delete succeeds, so try again when you are back online or email me.

Away-delivery has real limits, stated plainly: only reminders due within the next twenty-one days are uploaded at all, so a reminder set further ahead will not fire unless you open BrickDocket again before it comes into range; the schedule stops sending fourteen days after it was last refreshed by your browser; conditional reminders expire three days after they were due, because nothing on the server can re-check whether a balance is still unpaid; the sweep runs about once a minute; and a limited number of sends go out per sweep. Delivery also depends on Discord, ntfy, and general network reality, all of which are outside my control.

Notifications carry more of your records than the word "notification" suggests: depending on the event, the message body contains the commission title, a task title, an amount, the balance outstanding, your client's name, and — for a client message — the text your client typed. Every notification also links to the client page, token included.

Do not rely on a timer for anything with legal or financial consequence. Not a filing deadline, not a contractual delivery date, not a payment, not a court date, not anything where a missed reminder costs you. Use a tool that is contractually obliged to deliver for those. BrickDocket is not, and this section is why.

15. Information about other people

When you type a client's name, handle, contact or project details into BrickDocket, you decide why and how that information is collected and used. That makes you the controller of it. I am, at most, a processor, and only for the parts that actually reach my servers.

For records that never leave your browser I am neither controller nor processor. I cannot read them, search them, back them up, produce them in answer to a request, or delete them. That is not a policy position; it is a physical fact about where the data is.

As a condition of using BrickDocket, you agree that:

  1. You have the right to record the information you enter about other people.
  2. You will tell your clients you use BrickDocket to track their project, what you record, and how they can ask you to correct or delete it. Because your client never handed their data to me or to my software directly, the duty to tell them is yours, not mine. In practice the first message you send a client is the moment to do it.
  3. You will record only what you actually need.
  4. You will never record special-category data about anyone — health, religion, sexual orientation, biometrics, political views — and you will never record a government identity number, a payment card number, a home address, a school, a photograph, or a phone number about any client, child or adult.
  5. You will delete client records when the project is done and there is no reason to keep them.
  6. You will answer your clients' requests about their own information yourself, promptly. I cannot answer them for you, and I will say so if they ask me.
  7. You accept that treating this as "personal or household" activity is wrong. The moment you take a paid commission, you are acting professionally.

If a client contacts me directly about their information, I will tell them honestly that I cannot see or reach anything held in your browser, point them to you, and act on anything server-held that I can actually identify — an uploaded file or a published snapshot.

16. Data processing terms

These terms apply to the three flows where your clients' information genuinely reaches my servers: uploaded files, published client snapshots, and away-timer payloads. For those, you are the controller and I am the processor. This section is our data processing agreement.

What the processing actually is. Subject matter: running the file storage, client-link publishing and away-timer features you switch on. Duration: for as long as the content stays published or the feature stays enabled, and until you delete it, revoke it, or close your account. Nature and purpose: storing, serving and transmitting that content so those features work — nothing else. Types of data: whatever you put into a commission, an upload or a timer body, typically client names or handles, project titles, task descriptions, prices, dates and files. Categories of data subject: your clients, and anyone who appears in what you upload — who may be children.

I commit to the following, and they are binding:

17. Acceptable use

Do not:

You must comply with the Roblox Terms of Use. That is a requirement of using BrickDocket, not just of using Roblox.

If something on my servers — an uploaded file or a published snapshot — breaks section 17, infringes someone's rights, or has to come down because the law requires it, I can remove or disable that content and revoke the link serving it, without ending your account. I will tell you what I removed and why, unless the law stops me.

If you believe something published through BrickDocket infringes your copyright or another right you hold, email otrontv@gmail.com with the link, enough detail to identify the material, what right you hold, your contact details, and a statement that you believe in good faith the use is not authorised. I act on complete reports, and I will pass the report to the creator whose workspace published it so they can answer it. If you think I removed something wrongly, tell me and I will look again.

Accounts that repeatedly publish infringing material are terminated. Knowingly false reports are themselves a breach of these Terms.

19. Your content, and the limits on it

You own everything you enter and upload. I claim no ownership of it, no rights to reuse it, and no licence to show it to anyone else or to publish it. It is yours.

You grant me only the narrow technical permission needed to run the features you asked for: to store, transmit, cache and serve your files back to you and to whoever holds a client link you created; to publish the snapshot for links you chose to publish; and to relay reminders you configured. That permission is limited to those purposes and ends when you delete the content or your account.

There are hard limits, set to keep a free tool from becoming an unfunded storage bill. As things stand: 100 MB per file, 100 MB and 40 files per commission, 2 GB and 500 stored files per account, 10 live links per client and 500 per account, 60 timers with a five-minute minimum repeat, 30 notifications an hour, 20 active commissions, 150 clients, 5 accounts per device, 80 tasks and 25 add-on lines per commission, 20 reference images per commission, and roughly 4.6 MB of browser storage in total. Executable files are refused. "Active" means any commission that is not Delivered and not Archived — delivering or archiving one frees a slot, and archived work stays readable.

These numbers can change, and changing them is not a breach of these Terms. If I lower a limit, I will not delete content that is already stored because of it — the new limit applies to what you add next, and I will tell you in the app before it takes effect.

20. BrickDocket itself

The software, the name BrickDocket, the site, the themes and the code behind them are mine. While these Terms are in force you have a personal, non-exclusive, non-transferable, revocable licence to use BrickDocket as it is offered, for your own commission work. That licence does not let you copy, sell, sublicense, rent or redistribute the software, run your own copy of it as a service, or use the BrickDocket name or branding in a way that suggests I made or endorsed something I did not. Nothing here stops you doing anything applicable law lets you do regardless of a contract term, and nothing here affects your ownership of your own content under section 19.

21. Availability, changes and shutdown

BrickDocket is provided on a best-effort basis. There is no uptime commitment, no service level agreement, no guaranteed support response, and no promise that any feature will still exist next month. I may add, change, degrade, suspend or remove features.

If I decide to shut BrickDocket down permanently, I will post notice in the app and on brickdocket.com, and I will keep the export function working for as long as the site is up so you can take your records with you. I aim to give around 30 days, but I am not guaranteeing a notice period. One person cannot promise an orderly wind-down against every circumstance — a hosting provider, an identity provider or a legal requirement can end a service faster than that, and I would rather tell you now than write a number I might not be able to honour.

Given that your records live in your browser anyway, a shutdown does not delete them — but files and client links, which depend on my servers, would stop working. Keep an exported backup. That is the protection here, not a promise from me.

22. Third-party services

BrickDocket depends on services I do not control: Roblox, Google (sign-in and web fonts), Discord, Cloudflare, Supabase, jsDelivr (which serves one script), ntfy and Coinbase. Each has its own terms and privacy policy, each governs your use of it, and none of them is bound by these Terms. If one of them goes down, changes its API, or refuses you service, BrickDocket may stop working in part or in whole, and that is not something I can fix or be held to account for.

If you configure a Discord webhook URL, an ntfy topic or an ntfy token, keeping them secret is your job. A public ntfy topic can be read by anyone who guesses its name — the app warns you about this where you type it. Notifications also include a link back to the client page, which means the link token travels into whatever channel you pointed the webhook at. Point it somewhere private.

23. Roblox

BrickDocket is independent software for Roblox creators. It is not affiliated with, endorsed by, sponsored by, or in any way connected to Roblox Corporation.

Specifically, and as required:

  1. These Terms are between you and me only. Roblox is not a party to them.
  2. Roblox is not affiliated in any way with me or with BrickDocket.
  3. Roblox is not responsible or liable for any party's use of, or access to, BrickDocket.
  4. Roblox has no obligation to provide any maintenance or support service for BrickDocket.
  5. By using or accessing BrickDocket, you acknowledge and agree that you waive and release any and all claims, liabilities, damages, losses and expenses against Roblox arising from or related to BrickDocket.

You must also agree to and comply with the Roblox Terms of Use when using BrickDocket.

When you sign in with Roblox, BrickDocket asks for the openid profile scope only — sign-in and basic profile, the smallest permission set available. From what Roblox returns, BrickDocket keeps three things: your Roblox user ID, your username, and your avatar image URL. It does not ask for, keep or use your email address or your age, and Roblox does not hand those out for this scope in any case. Your account is keyed on your Roblox user ID, never on a username, because usernames change. Data obtained through Roblox's APIs is never sold, never used to train AI models, never used to track anyone across experiences, and never combined with data from anywhere off Roblox. If BrickDocket's access to Roblox's APIs ends for any reason, I will delete the data obtained through them. If BrickDocket ever changes hands, I will notify Roblox as their policy requires.

24. Termination

You can stop using BrickDocket whenever you like. Delete your workspace from the app, and clear the site data in your browser if you want nothing left behind.

I can suspend or end your access if you break these Terms, abuse the service, or where I am legally required to. I will give notice where that is practical, and act immediately where the abuse is serious.

When your account ends. Clearing your workspace from the app removes your records from this browser. It does not reach my servers on its own. Anything already on my servers — uploaded files, published client links and their snapshots, and any away-timer schedule with its delivery credentials — has to be withdrawn separately: revoke each client link, delete each commission's files, and switch away-delivery off, all before you clear the workspace. If you have already cleared it, email otrontv@gmail.com from the address on the account and I will remove what is left by hand. Left alone, published links stop working within thirty days and an away-timer schedule stops sending within fourteen days, but the underlying objects are not deleted until someone deletes them. Records held in your browser are not deleted, because I cannot reach them. They stay on your device until you clear them yourself, using the in-app control or your browser's site-data settings.

These sections keep applying after you stop using BrickDocket: 7 (BrickDocket never touches money), 8 (currency conversions are indicative), 9 (your records live in your browser), 12 (if you are the person opening a client link), 13 (watermarking is a deterrent), 15 (information about other people), 16 (data processing terms), 18 (removal, takedown and copyright), 19 (you own your content), 20 (BrickDocket itself), 23 (Roblox), 25 (no warranty), 26 (limitation of liability), 27 (if someone sues me because of something you did), 29 (governing law and disputes), 30 (feedback) and 31 (the standard bits) — along with any other term that by its nature is meant to outlast the account.

25. No warranty

BrickDocket is provided "as is" and "as available", with no warranties of any kind — express, implied or statutory. That includes any implied warranty of merchantability, fitness for a particular purpose, non-infringement, accuracy or reliability, and any promise that the service will be uninterrupted, timely, secure or error-free. It is one person's free software.

I do not warrant that your records will be preserved, that a reminder will fire, that a file will still be there, that a total is arithmetically right for your situation, that a currency reading reflects any real price, or that a client link will render for a given person on a given device.

Some countries and states do not allow implied warranties or consumer guarantees to be excluded, so some of the above may not apply to you. Nothing here takes away a right you have under mandatory consumer protection law where you live.

26. Limitation of liability

To the extent the law allows it, I am not liable for indirect, incidental, special, consequential, exemplary or punitive damages; for lost profits, lost revenue, lost business or lost goodwill; or for lost, corrupted or unrecoverable data — including records destroyed when browser data is cleared, a reminder that did not fire, a file that was not delivered, or a payment dispute with a client.

Where I am liable, my total liability for everything arising out of or relating to BrickDocket is US $50. You have paid me nothing, so fifty dollars is more than you ever put in.

That cap is small because this is a free tool made by one person with no revenue behind it. If a $50 ceiling is not enough protection for what you are doing, BrickDocket is the wrong tool and you should use something commercial with an SLA and insurance.

You pay nothing, and that is part of the bargain. BrickDocket is supplied gratuitously. Where the law allows a lower standard of care or a narrower liability for something provided free of charge, that lower standard is what applies here, and nothing in these Terms should be read as accepting a higher one.

Things I do not control are not my liability. I am not liable for any failure, outage, change, suspension, rate limit, API change or refusal of service by Roblox, Google, Discord, Cloudflare, Supabase, jsDelivr, ntfy or Coinbase, or by your browser, your device, your network or your operating system — including a reminder that did not arrive, a file that would not download, a client link that would not open, or a sign-in that stopped working. Section 22 lists those dependencies; this is the liability consequence of that list.

Time limit on claims. To the extent the law allows it, any claim arising out of or relating to BrickDocket must be brought within one year of the date the thing you are complaining about happened. After that it is too late. Where your local law sets a minimum limitation period that cannot be shortened by agreement, that period applies instead.

Nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be excluded. Some places — including New Jersey and Massachusetts among others — restrict how far a consumer's remedies can be limited, so parts of this section may not apply to you. The cap also governs only claims between you and me under these Terms. It cannot and does not limit any right your client, or anyone else who is not a party to this agreement, has to bring a claim directly against me under data-protection law — a contract between the two of us cannot take away a third person's statutory rights, and this section does not pretend to.

27. If someone sues me because of something you did

In plain words: if your content, your use of BrickDocket, your breach of these Terms, or the way you handled information about another person causes someone to bring a claim against me — including one of your own clients — you cover what that claim actually costs me.

To the extent applicable law allows it, you agree to cover the reasonable costs and any settlement I actually incur because of such a claim, so far as those amounts reasonably follow from what you did.

This does not cover any part of a claim caused by my own breach of these Terms, my negligence, or my failure to do something the law requires of me. I will tell you promptly about any such claim, give you the chance to take it over and defend it, and I will not settle a claim you are covering without talking to you first.

If you are a consumer, this section applies only as far as consumer law where you live permits. If you are under the age of majority, it binds only the parent or guardian who accepted these Terms on your behalf under section 4. This is meant to be proportionate for a free tool, not a corporate-style blank cheque.

28. Changes to these Terms

I can change these Terms. When I make a material change, I will update the effective date and version number at the top and post a notice in the app before it takes effect. There is no fixed notice period, no mailing list, and no promise to keep or supply superseded versions — this is a free tool with one person behind it, and maintaining a version archive and a notification pipeline is work that would come out of building the product. The current version is always the one at brickdocket.com/terms, and the date at the top tells you when it changed.

Continuing to use BrickDocket after the effective date means you accept the new version. Changes are not applied retroactively — anything that already happened is governed by the terms that were in force at the time.

29. Governing law and disputes

No country's law is named here, on purpose. I am one person, not a company with a registered seat, and picking a jurisdiction to sue me in — or to force you into — would be a piece of theatre rather than a real term.

What that means in practice:

30. Feedback

If you send me a suggestion, I may use it without owing you anything for it. You are not giving up anything you own by telling me an idea; you are just not acquiring a claim on the product by mentioning it.

31. The standard bits

If any part of these Terms turns out to be unenforceable, the rest still stands and that part is cut back to whatever is enforceable. If I do not enforce something straight away, I have not given it up. These Terms plus the Privacy Policy are the whole agreement between us about BrickDocket. You cannot transfer your rights under them to someone else; I can transfer mine if BrickDocket itself changes hands, with notice in the app first. Neither of us is responsible for a failure caused by something genuinely outside that person's control. Headings are there to help you find things and carry no legal weight. These Terms are written in English, and the English version governs.

Notices. Notices from me — a change to these Terms, a shutdown, a new sub-processor, a suspension — are posted in the app and on brickdocket.com. That is the only channel, and I do not undertake to email you. I keep no mailing list, and for most people I hold no email address on any server I control. Opening the app occasionally is on you: a notice posted there is still notice even if you did not read it, and it takes effect on the date it says it does. You reach me at otrontv@gmail.com, and a notice to me takes effect when I acknowledge it, or seven days after you send it, whichever comes first.

32. Contact

otrontv@gmail.com — for questions, for problems, for a dispute you want to raise before it becomes one, and for abuse or takedown reports.

If you are someone's client and you have found your information in a BrickDocket workspace, write to me at that address. I will tell you honestly what I can and cannot reach, act on anything held on my servers that I can identify, and point you to the creator for everything else.