Disclaimer

Hey! You clicked on The Blogfather’s Disclaimer page! That means you probably know by now that this blog may have a tendency to present things that require its owner (me) to protect his (my) ass afterwards.

I’ve worked in a law firm long enough to know legal jargon probably isn’t going to cut it with you, so I’m going to try and make this Disclaimer more readable; it’s the least I can do, seeing as you’ve already made it to the second paragraph.

And if you’re a lawyer, feel free to nitpick at my language; I reserve the right to ignore you.

User Agreement (a.k.a. The “ai lai mai suah” Clause)

By engaging with The Blogfather via this blog, you accept this disclaimer in full. If you disagree with any part of this disclaimer, go find another dad blogger to troll. The Blogfather reserves the right to modify these terms at any time, so come back to this page whenever you can to see if I added anything  funny.

Of course I’ll understand if you decide not to come back; The Blogfather knows in all practicality, no one is that free to read people’s disclaimers every day, so here’s the deal. By using this site after The Blogfather makes any changes, you agree to accept those changes, whether or not you have reviewed them.There; ai lai mai suah.

Copyright and Intellectual Property

Unless otherwise credited, all images, writing, opinions and ideas (herein known as ‘content’) published on The Blogfather are protected by Singapore copyright and intellectual property laws and owned by The Blogfather.

That said, if you find anything in here that you know came from somewhere else other than me, please let me know before you make a police report.

Unless stated otherwise, you may access and consume the content published in The Blogfather only for personal, non-commercial use. You may not copy, reproduce, distribute, publish, display, perform, modify, create derivative works, transmit, or in any way exploit any content by The Blogfather, mostly because I installed this neat little plug-in that disables the right-click copying function. If you want to seek permission to do so, ask me. Sometimes I might say, “Okay”.

Sometimes.

Accuracy of Information

Contrary to popular belief, The Blogfather can be wrong sometimes. All information expressed in this blog has been obtained from, or is based on, sources which The Blogfather tried his darn best to fact-check and reasonably believed be reliable at the time of writing, but is not guaranteed as to its accuracy, completeness or validity and should not be relied upon, and has not been independently verified.

The information expressed by The Blogfather is current only as at its publishing date and may no longer be valid, true or complete when viewed. All information presented by The Blogfather may be changed or amended any time without prior notice, although The Blogfather admittedly doesn’t have a habit of reviewing posts for errors every 6 months or so. Visitors who use and rely on any information presented by The Blogfather do so at their own risk.

Content Suitability

The Blogfather’s content is largely family-oriented; The Blogfather’s content has been known to crop up in parenting publications, at  junior college General Paper lectures, and even on the smartphone screens of giggly tweens. But The Blogfather’s opinions, while mostly grounded in logic and reason and open to interpretation and debate, can be controversial at times. Also, I have been known to swear (mostly to drive a point).

So if you are under 16, please seek the guidance of a parent or guardian while you allow The Blogfather to influence your innocent mind. I know it’s a lot to ask of a 16-year-old; after all, The Blogfather was 16 once, too.

And I also know you’re not that innocent.

Third Party Content and External Links

Very often, The Blogfather talks about things other people talk about, so I’ll refer to content on other websites by posting external links or embedding content within my own posts. While The Blogfather does make every effort to ensure any third party content and external links is accurate, up to date and relevant at the time of writing, The Blogfather can’t be held responsible for content and websites created and managed people who aren’t me, and The Blogfather does not necessarily endorse the views expressed within them.

Reader Responsibility: The “Don’t Be a Dick” Clause (hat tip to the late Oren Miller)

All comments in this blog are moderated, though most opinions will receive approval in the spirit of encouraging discourse; The Blogfather respects and encourages the right of everyone’s opinion, whether agreeable, dissenting or neutral, as long as it’s not personal in any way (derogatory, discriminatory or self-promoting). But views expressed in comments are the commenter’s own, and unless I explicitly say I agree or disagree with said views, don’t assume I lean either way.

Also, don’t use The Blogfather’s website in any way which is unlawful, illegal, fraudulent or harmful, or in connection with any unlawful, illegal, fraudulent or harmful purpose or activity. The Blogfather accepts no responsibility for any loss or harm incurred through the use of the content presented in this blog.

So stay on topic, not on the person, don’t be a dick and don’t be a criminal nor an accessory to crime. Play by these rules of engagement – not just with The Blogfather, but anywhere in life, online and off – and you’ll do just fine.

Website Uptime, Security and User Protection

Regardless, bad people will be bad people even if you don’t want them to be, and bad things can and will still happen on the World Wide Web, and The Blogfather, as intimidating as he can be online or in person, does not warrant that functions available on this website will be uninterrupted or error free, that defects will be corrected, or that the server that hosts this blog is free of viruses or bugs. Users are responsible for the knowledge, security and protection of their own computing devices an themselves against viruses, hackers and all those other nefarious concoctions of digital deviance.

Leave a Reply

Your email address will not be published. Required fields are marked *