Is my data safe?
yazar.io uses Supabase for its database, accounts, and file storage. Thanks to Row Level Security (RLS), every user can only access their own books and content; the content you create is never sent to product analytics.
Row Level Security (RLS)
At the database level, every query checks who's signed in and only returns the rows that user owns - this rule is enforced by the database itself, independent of the application code. No other user can reach your books, characters, or notes, even if they know or guess a link.
The only surface kept public is the Author Card you deliberately choose to publish - your books themselves are never visible through that card.
Images and analytics
Book and character images are stored in private storage and are only shown through time-limited links tied to your account - a permanent, public image URL is never written to the database.
Analytics tools only run once you consent to them in your cookie preferences, and the content you create - books, characters, lore, notes - is never sent to analytics systems; only categorical information, like how often you use a given section, is collected.
Can another user view my book if they know the link?
No. RLS rules are enforced at the database level - only the book's owner can access it (except the Sample Book, which is deliberately public and read-only).
Is the text I write (lore, notes) sent to analytics?
No. No user-generated content (book titles, character/location names, lore text, notes) is ever sent to analytics systems.
Related Content
Start building your world on yazar.io
Bring your characters, locations, and every thread of your world together in one place - no credit card required.