NovelDesk privacy policy
Effective date: October 16, 2026 · Operator: Pentarab (representative 송락규, business registration no. 898-19-00957, 4F, Building 1, Dongwoo Building, 328 Teheran-ro, Gangnam-gu, Seoul, Republic of Korea) · Contact: support@noveldesk.app
In short
- On the free desk your writing is stored only on your device, by your browser. We have no copy and never see it. If the browser clears this site’s data (Safari does after 7 days without a visit), the writing goes with it, so we recommend backup files. With Plus we keep a copy on our servers while you are subscribed (saving to the cloud turns on by itself), and you can turn it off per device. We also see a chapter if you publish it or ask for an illustration.
- No ads. We don't track you as a person: visits are only counted, with Cloudflare Web Analytics, which uses no cookies. We don't sell your data. We don't use your writing to train AI.
- Illustrations (Plus) send one chapter's text to Cloudflare's AI service, which runs open AI models on Cloudflare's own network. Section 5 says exactly where it goes and what is kept.
- Deleting your account removes what we hold on our servers (section 10). Your browser's copy stays until you clear it.
1. Who we are
NovelDesk (noveldesk.app) is run by Pentarab, a company in Korea. Pentarab decides why and how your data is used, so it is the "controller" under the GDPR and the "personal information controller" (개인정보처리자) under Korea's Personal Information Protection Act (PIPA). Privacy contact and officer: 송락규 (representative), support@noveldesk.app.
2. What stays in your browser
Manuscripts, chapters, notes, settings, statistics, version history and pictures you add are stored in your browser (IndexedDB and localStorage) on your own device. On the free desk this is the only copy: they are not sent to us, we have no copy, and we cannot read, recover or delete them. NovelDesk itself never deletes your writing, but your browser can: clearing site data, using a private window, or a browser's storage clean-up (Safari can clear script-written data of a site not visited in 7 days of Safari use) removes it. We do not guarantee how long writing stored in your browser lasts, and we recommend that you save backup files and keep them somewhere other than this browser. With Plus, saving to the cloud turns on by itself on a device where you have not switched it, and saves your writing to our servers (section 3); turning it off on a device stops uploads from that device.
3. What we collect, why, and for how long
| Data | When | Why | How long |
|---|---|---|---|
| Email address | You sign in | Account, sign-in codes, billing match | Until you delete your account |
| Name and picture link from Google or Apple, and the tokens they return at sign-in. With Apple "Hide My Email", the private relay address Apple gives us instead of your real one | You choose Google or Apple | Show who is signed in | Until you delete your account |
| Sign-in records: session token, IP address and browser (user agent) of each session | You sign in | Keep you signed in, show your signed-in devices, protect the account | Until the session ends (60 days), you sign out, or you delete your account |
| Short-lived security counters tied to your IP address (limits on code requests) and a note that a code was sent to an address | Sign-in attempts | Stop abuse and mail floods | deleted automatically within two days; the "code sent" note is removed within about an hour |
| Sign-in codes (6 digits) | You ask for one | Sign you in | Valid 10 minutes |
| Plan data: plan (month or year), status, period end, cancel flag, your Polar customer id and subscription id | You subscribe | Know whether you have Plus | Until you delete your account |
| Drawing-credit counts and a log of each credit spent or returned (with the illustration id) | You draw | Enforce 20 drawings a month | Until you delete your account |
| The cloud (Plus): manuscripts, chapter text, titles, people-and-places notes, pictures up to 5 MB, and the last 20 revisions of each chapter | Saving to the cloud is on (it turns on by itself with Plus, until you turn it off on a device) | Keep your writing on other devices and as a spare copy | Until you delete it or your account, including after Plus ends (it is then no longer updated) |
| Illustration pictures and a record of each request (owner, style, status) | You draw | Show you the picture | Until you remove it or delete your account. We do not keep the chapter text |
| Published chapters (Plus): your public handle, titles, byline, language, and the chapter text as web pages | You publish | Show the pages at read.noveldesk.app | Until you remove the page or delete your account, or until Plus ends unless you chose to keep your pages online |
| Reader counts for published pages: numbers only, plus a one-way code per reader (section 7) | A reader opens a page | Tell you roughly how many people read | Counts stay while the page is live. Codes are explained in section 7 |
| Visit counts: page address, previous page (referrer), browser, operating system, device type, country and page load timings, collected by Cloudflare Web Analytics without cookies (section 4) | You open a page on noveldesk.app or read.noveldesk.app | Count visits and see how fast pages load | Kept and shown as statistics by Cloudflare under its own schedule; we hold no visitor-level copy |
| Reports about a published page: reason, optional note, optional email, a one-way code from the reporter's IP address | Someone reports a page | Review copyright and abuse reports | 1 year from the report, then deleted |
| Messages you send us | You email us | Reply and keep a record | 3 years (Korea's e-commerce act keeps records of consumer complaints and dispute handling for 3 years) |
We do not collect your writing for any purpose of our own, and we do not look at it except where section 11 allows. Under Korea's Act on Consumer Protection in Electronic Commerce, records of consumer complaints and dispute handling (your support emails) are kept for 3 years; contract and payment records are kept by Polar as the seller.
4. Cookies and similar storage
- One first-party cookie keeps you signed in (name starts with
noveldesk, Secure, SameSite=Lax, up to 60 days). It is needed for the service. Writers who never sign in get no cookie from us. - Settings and your writing use localStorage and IndexedDB on your device.
- Published reading pages set no cookies.
- Visit statistics: every page on noveldesk.app (home, the app, legal pages) and the published reading pages (read.noveldesk.app) load Cloudflare Web Analytics. Cloudflare says it does not use cookies, localStorage or other client-side state to collect these metrics, and does not "fingerprint" individuals from their IP address, user agent or other data. It collects page-view data such as the page address, the previous page (referrer), browser, operating system, device type, country and page load performance. It does not track you across sites.
- Google Fonts: the NovelDesk app and website serve their own fonts. Only published reading pages (read.noveldesk.app) load the Literata, Gowun Batang and IBM Plex Sans typefaces from Google Fonts, so a reader's browser sends Google its IP address and browser details when such a page loads. Google's own policy governs that.
- Checkout is on Polar's page; Polar sets its own cookies there.
5. Illustrations (Plus, only when you press Draw)
When you ask for an illustration, this happens:
- That chapter's text (cut at 24,000 characters) and your optional "what should it show?" note go from your browser to our server (a Cloudflare Worker).
- Our server sends them to Cloudflare Workers AI. A language model there, Gemma 4 (26B A4B), an open model published by Google, writes a short English description of one scene.
- That scene description (not the chapter) goes to an image model on Workers AI, FLUX.2 [klein] 4B, an open model published by Black Forest Labs (Apache-2.0 license), which draws the picture.
- The picture comes back to our server and is stored for you in our file storage (Cloudflare R2).
Cloudflare runs both models itself, on its own network. Nothing is sent to Google, Black Forest Labs, fal.ai, OpenRouter or OpenAI. The only company that handles the data is Cloudflare, Inc., which already hosts our service (section 9).
What is kept, and by whom:
- Us: the picture and a record of the request. Not the chapter text, and not the scene description; both exist only in memory while the request is processed.
- Cloudflare: Cloudflare's Workers AI data usage terms say that it does not train the AI models available on Workers AI, that it does not use your content to train those models or to improve any Cloudflare or third-party services without your explicit consent, and that it does not make your content available to other Cloudflare customers. We do not give that consent. We also send each request with
store: false, which asks Cloudflare not to save the output. Cloudflare's documentation does not say where Workers AI requests are processed; assume anywhere on Cloudflare's worldwide network, which may be outside Korea (section 12).
Please do not put other people's private information in a chapter you send for illustration. Illustrations are optional; nothing else in NovelDesk sends your text to Cloudflare's AI service.
6. Payments
Polar (Polar Software Inc., United States) is the merchant of record: it sells Plus to you, charges your card, calculates tax and sends receipts. Your name, card details, billing address and tax details are handled by Polar (and its payment processor), not by us. We send Polar your account email and our user id so the purchase matches your account. We receive your subscription state and Polar's customer id. We never see your card number. Polar keeps its order records for tax and legal reasons even after you delete your NovelDesk account.
7. Publishing and reader counts (Plus)
- A chapter you publish is public at read.noveldesk.app. Anyone with the link can read it. Search engines are told not to index it unless you choose "indexable". Removing a page deletes it from our servers; copies that readers or search engines have already made are not ours to delete.
- We count readers without cookies. For each reader we compute a one-way code from the reader's IP address, browser details and the publication, mixed with a secret salt that is new every month. We do not store the IP address or the browser details. Salts of past months are deleted by a daily job, so codes cannot be recomputed or linked from one month to the next. Codes are kept only as long as needed to avoid counting someone twice (about today, yesterday and the current month); what remains afterwards is only counts. Bots and prefetches are ignored.
- Our network provider (Cloudflare) still sees reader IP addresses as part of delivering any web page.
- Published reading pages also load Cloudflare Web Analytics, which counts visits without cookies or local storage and does not track individual readers (section 4).
- A report form stores the reason, an optional note (up to 1,000 characters), an optional email you enter, and a one-way code from your IP address (same salt idea) used to limit reports to 5 per hour.
8. Sign-in with Google or Apple
We receive your email, name and picture link (Google) or your email or relay address and name (Apple), and the identifiers that link that login to your account. We use them only to sign you in. We do not read your Google or Apple data beyond that. The tokens Google and Apple return at sign-in are stored in our database with your login record. We do not use them after sign-in, and they are deleted with your account.
9. Who handles data for us (service providers)
| Provider | Role | Data | Country |
|---|---|---|---|
| Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA; legal@cloudflare.com) | Hosting, database (D1), file storage (R2), network delivery, illustration AI (Workers AI), visit statistics (Web Analytics) | Everything stored on our servers; IP addresses in transit; chapter text and scene description while an illustration is made (not stored); visit data (section 4) | United States and Cloudflare's worldwide network. Our database (D1) and file storage (R2) are stored in Cloudflare's Asia-Pacific region |
| Resend (Plus Five Five, Inc.; support@resend.com) | Sends sign-in code emails from signin@noveldesk.app | Your email address and the code | United States |
| Polar Software Inc. (3500 South DuPont Highway, Dover, DE 19901, USA; privacy@polar.sh) | Merchant of record | Email, user id, payment data you give it | United States |
Resend's documentation says it retains email data for 30 days. Cloudflare's data processing terms say it processes personal data only to provide its services, and that data may be processed outside the EEA, Switzerland and the UK under standard contractual clauses and the Data Privacy Framework. We do not sell personal data and we do not share it for advertising. We give personal data to others only as above, or when the law requires it, or with your agreement.
10. Deleting your account
Settings or Account, then "Delete account". We first end any active Polar subscription (immediately, so you are not charged again), then delete your user record, sessions, plan and credit records, illustrations (including the stored pictures), what you saved to the cloud, and published pages and their counts. This cannot be undone. What remains: your writing in your browsers (clear it yourself), Polar's own order records, and copies at outside companies until their schedules expire (for example Resend's 30 days for emails). Deleted data may remain in our database's rolling history (Cloudflare D1 "Time Travel") for up to 30 days. Files in storage are not backed up. Deleting a chapter or a manuscript from the cloud is also possible at any time, with or without Plus.
11. When we look at your data
What you save to the cloud is encrypted in storage by Cloudflare but is not end-to-end encrypted, so we can technically read it. We look at stored content only to run, secure and repair the service, to handle a report about a published page, or when the law requires.
12. Where data goes (international transfers)
We are in Korea; our providers are mainly in the United States, and Cloudflare serves from many countries. When you ask for an illustration, Cloudflare's AI processing may also run in any country on its network, so the chapter text may leave Korea only then. Transfers rely on: your contract with us (processing needed to run the service you asked for); standard contractual clauses and the EU-US Data Privacy Framework where the provider offers them; and, for Korean users, section 28-8 of PIPA (see the Korean version of this policy for the required table). If you are in the EU/UK, you may ask us for a copy of the safeguards used.
13. Legal bases (EU/UK users)
Contract (running your account, Plus and the features you ask for); legitimate interests (security, preventing abuse and spam, counting readers and visits without identifying you); legal obligation (tax and copyright takedown records); consent where we ask for it.
14. Your rights
Depending on where you live (GDPR, UK GDPR, PIPA, CCPA/CPRA) you can ask to see your data, correct it, delete it, restrict or object to some processing, take a copy, and withdraw consent. Write to support@noveldesk.app from your account email; we answer within the time the law allows (one month under the GDPR). Most of this you can do yourself: export a backup, delete what is in the cloud, remove published pages, delete your account.
- California: we do not sell or "share" personal information for advertising, and we do not use sensitive information beyond running the service.
- EU/UK: you may complain to your data protection authority.
- Korea: you may also contact the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118), the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972), the Supreme Prosecutors' Office (spo.go.kr, 1301), or the National Police Agency's cyber crime report system (ecrm.police.go.kr, 182).
15. Security
All traffic uses HTTPS. Files in Cloudflare R2 are encrypted at rest (AES-256). We use no passwords: you sign in with a one-time code, Google or Apple. Codes expire in 10 minutes and allow 5 attempts, and code requests are rate limited. Secrets for our services are kept outside the source code. Only one person, the operator, can reach the servers. No system is perfectly secure; if a breach affects you we will tell you as the law requires.
16. Children
NovelDesk is not for children under 14. Under Korean law a child under 14 needs a parent's consent, which we do not collect. If you live somewhere the age to agree to an online service is higher, use NovelDesk only with a parent or guardian's permission. If we learn we hold data of a child under 14, we delete it.
17. Changes
We will post changes here and change the effective date. For changes that matter, we will tell signed-in users by email or in the app at least 7 days before (30 days if the change reduces your rights). Earlier versions are sent by email on request.
18. Contact
Pentarab, 4F, Building 1, Dongwoo Building, 328 Teheran-ro, Gangnam-gu, Seoul, Republic of Korea, support@noveldesk.app. Privacy officer: 송락규 (representative).