Privacy policy.

Who controls your data

PublisherFriendly, operated by Abdülkadir Altan, Türkiye, is the controller for the data described on this page. Data protection contact: [email protected].

Identity

Sign-in and authentication are handled entirely by Clerk — your password, if you have one, is never seen by our server. Clerk holds your credentials and session. If you choose to continue with Google, Google confirms who you are to Clerk under Google’s own privacy policy. What we store on our side is your Clerk account id and, once we know it, your email address. A purchase is matched to your account by your account id, which our server puts on the checkout; the email typed at checkout is not used for that.

Our Canva apps keep the user id Canva gives each app for you, with no sign-in and no email, to give you the app’s free monthly credits and keep the books you make there. If you confirm a link to your PublisherFriendly account, that id and its books are added to the account, and the app can then spend the account’s credits. The id stays until you ask [email protected] to delete it.

Payment

Paddle.com is our payment processor and merchant of record. All card and billing details are collected and held by Paddle directly — our server never receives, transmits, or stores card numbers. After a purchase, Paddle sends our server a signed notification of the order or subscription: what was bought, the amount, Paddle’s ids for the customer and the payment, and your account id. It can also name the card’s type, last four digits, expiry and holder; we drop those before anything is stored.

What we store about your books

The settings you choose for a book (trim size, title, author name, and similar), the generated interior and cover PDFs, and — for word search books — the underlying word lists a model wrote, so a book can be reprinted with different formatting later without generating different words. This data is what a customer library entry and the “adjust and reprint” feature are built from.

Retention: files are kept for as long as your account is open. Write to [email protected] and we delete them within 30 days. Files are held in Railway’s file storage; each download is served through a link that expires a few minutes after it is issued, but that expiry is about link security, not about deleting the underlying file.

Usage and credit records

Every credit movement on your account — a plan grant, a paid top-up, a reservation when a job starts, a release if a job fails, a refund — is written to an internal ledger tied to your account, along with the balance it left you at. This is kept for accounting and support purposes: if you ask why your balance changed, this is the record we check. A Canva app’s free monthly credits have a record of their own, kept the same way: what each book took from them and what came back.

AI models

Some parts of a book are written or drawn by AI models: the words of a word search book, the pictures of a coloring book, and an illustrated cover. For these we send what the book itself needs — the theme you typed, the choices you made for the book, and the words that appear on its cover (title, subtitle, and the author or imprint name) — to Wiro, an AI model service, which passes them to the model that does the work. Today those models are made by OpenAI and Anthropic. Your email and account details are never part of these requests. Sudoku puzzles are made by our own program, without AI.

Where you came from

The first time you open a page here, we remember how you arrived: the campaign tags in the link (such as utm_source), the website that sent you, and the page you landed on. This sits in one cookie of our own, pf_ft, for 30 days. If you make an account in that time, it is stored with your account once, so we can tell which channels bring people who find the product useful. It is not shared, it is not used for advertising, and this site runs no third-party trackers.

Running the service

The site, our server, its database and the stored files run on Railway. Cloudflare serves our domain, so your requests pass through it on their way to us. To notice failures quickly, our server sends Better Stack technical records: which page or action ran, whether it worked, how long it took, and our internal record ids. Your email and the content of your books are not in those records. If you write to support, your email is kept in our mailbox at Zoho.

Who else processes your data

• Clerk — identity and session management
• Google — only if you choose to continue with Google when you sign in
• Paddle — payment processing, billing and sales tax, as merchant of record
• Wiro — AI model service for word lists, coloring pages and covers, from the book’s own details only
• OpenAI and Anthropic — the AI models Wiro passes those requests to
• Railway — hosting, database and file storage
• Cloudflare — domain and network delivery
• Better Stack — error and performance monitoring
• Zoho — the support mailbox

Some of these services process data outside your country, including in the United States.

Contact

Questions about this policy or your data: [email protected].