Introduction
This Cookie Policy explains how My Blurbly may use cookies, pixels, local storage, session storage and similar technologies.
Cookies and tracking
How My Blurbly uses cookies, local storage, analytics, affiliate attribution and consent controls.
Last updated: 7 June 2026
Current public policy for My Blurbly V3. These terms are intended to govern the live platform and payment-provider review pages from the date shown above.
This Cookie Policy explains how My Blurbly may use cookies, pixels, local storage, session storage and similar technologies.
My Blurbly means the My Blurbly V3 website, application, tools, public pages, creator websites, community surfaces, Editorial AI features, ARC workflows, payment flows, email funnels and related services. User means any visitor, reader, author, reviewer, creator, influencer, affiliate, publisher, beta tester, customer, subscriber or account holder. Content means text, manuscripts, excerpts, reviews, comments, messages, images, covers, avatars, metadata, links, uploads, prompts, AI outputs, creator website materials and campaign assets. Paid Services means memberships, subscriptions, upgrades, credits, one-off digital tools, reports, ARC campaign upgrades, creator website upgrades or other paid products. Provider means a third-party service used to operate My Blurbly, including Supabase for data storage, Brevo for email, Paddle for payment processing when enabled, hosting providers, analytics providers and AI service providers. Cookies are small files or identifiers stored on a device or browser.
Essential cookies support login, security, load balancing, consent records, checkout state, preferences and requested services. Analytics cookies help understand pages, routes and feature usage. Affiliate and campaign cookies may preserve referral codes, discounts and conversion attribution. Advertising-style cookies are not required for core service operation and should require consent where applicable.
Analytics may collect route visits, click events, referrers, campaign codes, device/browser information, approximate location from IP, and performance data. Analytics should be configured to avoid unnecessary sensitive data collection.
Where required by law, users may accept, reject or change non-essential cookie choices. Users may also clear cookies through browser settings.
Users should understand that disabling essential cookies may break login, checkout, security, account preferences or saved workflow features.
My Blurbly may operate, secure, change, pause, restrict, remove, label, moderate, investigate or discontinue features where needed for safety, compliance, platform integrity, provider requirements, fraud prevention, payment risk, beta testing or legal obligations.
To the maximum extent allowed by applicable law, My Blurbly is provided on an as-is and as-available basis. My Blurbly is not liable for indirect, incidental, consequential, special, punitive or loss-of-profit damages, or for loss caused by user content, third-party providers, payment providers, AI inaccuracies, unavailable features or unlawful user conduct.
Users should first contact My Blurbly at the contact address in this document so the issue can be reviewed informally. If informal resolution fails, disputes will be handled under the governing law and competent courts stated below, unless mandatory consumer law gives the user a different non-waivable forum or remedy.
These terms are intended to be governed by the laws of the Republic of South Africa, unless a mandatory consumer, privacy or platform law in another jurisdiction applies and cannot legally be excluded.
Questions, legal notices, privacy requests, takedown requests, refund questions and account deletion requests should be sent to support@myblurbly.com. My Blurbly should publish any updated support address, business address or provider-required buyer support details before live paid rollout.
This policy supports GDPR/UK GDPR cookie transparency, POPIA lawful processing principles and CCPA-style notice of analytics and sharing practices.