Privacy Policy
Effective 7 November 2026 · Version 3.1
The short version: your artwork and your stories are yours. We do not train models on them, we do not sell them, and we do not hand them to anyone who would. The rest of this page is the specific, checkable version of that sentence.
Who we are
MangaForge is operated by Mangaforge Pvt Ltd, a company registered in India. For anything in this policy, including requests about your data, write to privacy@mangaforge.jp. Our registered address is Mangaforge Pvt Ltd, Flat No. G1101, Lotus Elise, Sector 99, Khandsa Road, Gurgaon, Haryana, India 122001.
Google Sign-In: data collection and use
MangaForge offers Google Sign-In as an optional way to create and access an account. The full detail is in “Google user data” below; this is the summary.
- Data collected: through the
openid,emailandprofilescopes, your Google account identifier, email address, email verification status, name and profile picture. - Purpose: to authenticate you, create or link your MangaForge account, and show your name and picture in the studio.
- Storage and retention: in our Supabase database, for as long as your account exists. It is deleted when you delete your account.
- Sharing: we do not sell Google user data or use it for advertising. Supabase processes it on our behalf to provide database and authentication services. We share it with no one else.
- Your choices: Google Sign-In is optional. You can revoke access in your Google Account permissions, or ask us to delete your account at privacy@mangaforge.jp.
MangaForge’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we collect
If you joined the waitlist
- Your email address.
- Your language preference, so we write to you in English or Japanese.
- Optionally, what tool you use today, if you choose to tell us. This shapes what we build.
- A record of the consent you gave: the exact wording you agreed to, the time, and the IP address the request came from. We keep this because consent is only meaningful if it can be proven, and because Japanese law requires us to be able to show it.
If you use the studio
- Your account email and display name. If you sign in with Google, also your Google profile picture (see “Google user data” below).
- If you use Translate: the pages you upload to be translated, the text read from them, the translation, and the lettered pages it produces. See “Translate” below.
- If you use picture search on a lore board: the pictures you choose to keep. We do not keep what you searched for. See “Picture search” below.
- Billing records for credits and purchases: amount, date and plan. Card details are handled by our payment processors and never reach us.
- The work you create: stories, scene cards, storyboards, pages and artwork. We store this so the product functions. We do not read it, mine it, or use it to build anything.
- Technical diagnostics when something breaks: error messages, browser and device type. These help us fix faults and nothing else.
Google user data (Sign in with Google)
When you choose Continue with Google, or use the Google One Tap prompt, Google shares with us your Google account identifier, email address, email verification status, name and profile picture (the openid, email and profile scopes). We do not request access to your Google Drive, Gmail, Calendar, contacts or any other Google data.
- How we access it: once, at sign-in, through Google’s OAuth consent screen. We receive a one-time ID token carrying the identity fields listed above, which our authentication provider (Supabase) verifies and turns into your account. We do not receive a Google access token or refresh token, and we do not read any other Google data and we hold no ongoing access to your Google account.
- How we use it: only to create your MangaForge account and sign you in, to show your name and picture in the studio, and to contact you about your account. We do not use it for advertising, profiling, or any purpose beyond operating your account.
- How we store it: in our Supabase database, encrypted at rest and in transit, for as long as your account exists. It is deleted when your account is deleted.
- How we protect it: we treat Google user data as sensitive data. Security procedures are in place to protect its confidentiality: it is encrypted in transit with TLS and encrypted at rest with AES-256, access is limited by database row-level security so only your own signed-in account can read it, and staff access is restricted to what is needed to answer a support request you make. See “How we protect your data” below for the full list.
- How we share it: we do not sell it, transfer it, or share it with any third party other than the processors listed below who host it on our behalf. We do not use it to train any machine learning model, and no human at MangaForge reads it except to answer a support request you make.
- Revoking and deleting: you can remove MangaForge’s access at any time at myaccount.google.com/permissions, and you can ask us to delete your account and data (see “Your rights”).
MangaForge’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we do not use Google user data for advertising, we do not sell or transfer it to data brokers, we do not use it to make credit or lending decisions, and we do not use it to develop, improve or train any generalized or non-personalized AI or machine learning model.
What we never do
We do not use your work to train, fine-tune, evaluate or benchmark any machine learning model. We do not license, sell or otherwise provide it to any third party for that purpose. This is not a preference we may revisit. It is a term of the agreement between us, stated again in our Terms of Service.
If that ever changes, it would apply only to work created after the change, only with your explicit opt-in, and we would tell you plainly rather than by amending a document quietly.
AI in the planning and drawing tools
MangaForge has no image generation. Nothing draws on your behalf, and nothing plans a page on your behalf. The story canvas, the storyboard and the drawing editor do not use a language model: the scenes you write, your dialogue and your artwork are not sent to one.
Until 2 October 2026 one feature did. Staging a storyboard page sent the written text of a scene to Google’s Gemini API, which returned a suggested shot list. That feature has been removed.
Nothing you make in the story canvas, the storyboard or the drawing editor is sent to a third-party AI provider: not a scene, not a line of dialogue, not an image. The only feature that sends anything to one is Translate, and only the pages you upload to it yourself.
One drawing tool, layer separation, runs image models to split a picture you choose into line art and tone layers. Those are models we run ourselves, on our own processing service (hosted on Modal). The picture is processed there and the layers come back to you; that service does not keep it, and it goes to no outside AI provider.
Translate
Translate is an optional service that translates manga pages you upload and letters the translation back onto them. It is for works you own or have licensed, which you confirm each time you submit. It works only on files you upload to it from your device. Nothing in your stories, storyboards or drawings goes to Translate unless you upload it there.
- Where it runs: on our translation service, hosted on Modal, with its files stored on Amazon Web Services (S3). Finding the balloons, reading Japanese text, erasing the original lettering and setting the new text are done there by models and code we run ourselves.
- What is sent to Google’s Gemini API: the text read from your pages, together with any glossary or note you add, so that it can be translated. For a source language our own reader cannot read (at present, Turkish), the cropped image of each piece of lettering is sent to be read, one balloon at a time, never the whole page. On the Pro tier, reduced-size images of the pages being translated are also sent, so the translation can see who is speaking and what is happening.
- Training: Translate uses the paid Gemini API tier, under which Google does not use submitted content to train its models. We do not train anything on your pages or translations either.
- Who can see it: your uploads and results are private to your account.
- How long it is kept: the pages you uploaded, the working data and the translated output are deleted 30 days after the job finishes. You can delete a job, and everything stored for it, sooner.
Picture search
Lore boards can search for reference pictures. It finds pictures that already exist and shows where each one came from; it does not make pictures. It runs only when you type a search.
- What is sent, and to whom: only the words you type. Free-to-use pictures are searched on Openverse, straight from your browser, and on Pexels, through our server. The web tab searches Brave Search, through our server. Our server sends the words alone: not your name, your email, your account or anything from your work.
- Previews: pictures in the results load from the servers of the service that found them, so that service sees your browser’s network address, as with any picture on the web. A search made straight from your browser (Openverse) is seen the same way.
- What we keep: we do not record what you searched for. To keep within the daily limits we note that your account made a search, not what it was, and delete that note after 24 hours. A free-to-use picture you add to a board is copied into your workspace’s storage with its credit: title, creator, licence and the page it came from. A web result you add is kept only as a link and the search service’s preview, marked as reference; the picture itself is not copied.
- Training: nothing here is used to train anything, by us or, through us, by anyone else.
Who processes data on our behalf
We keep this list short on purpose, and we will update it here when it changes.
- Supabase: database, authentication and file storage. This is where your account and your work live.
- Cloudflare: content delivery, security, bot protection on our forms, and email routing for our own addresses.
- Google (Sign-In): authenticates you if you choose Continue with Google.
- Google (Gemini API): translation in the Translate service, as set out above. Nothing else is sent to it.
- Modal: runs the Translate service and the layer-separation tool’s image processing.
- Amazon Web Services (S3): temporary storage of Translate uploads and output.
- Pexels and Brave Search: the words of a picture search made through our server, and nothing else. Searches on Openverse go to it from your browser.
- Resend: sending the email you asked us to send.
- Crisp: the live chat in the studio, so you can write to the people who make MangaForge. While you are signed in, Crisp receives your email address, your display name, your plan, the date you joined, which screen you are on (the kind of screen, never a file or its name), a few milestones such as whether you have made a manga or exported pages, and anything you write in the chat. It never receives your artwork, your stories, your titles or your file names.
- Sentry: error diagnostics, so faults surface before you have to report them. Sentry receives code errors and technical context only, not the content of your work.
- PostHog: anonymous product usage counts, such as how many pages were added or whether sign-up completed. Events reach PostHog through our own servers, carry no IP address, no account identity and no content of your work, and never include a title, text, file name or artwork.
- Stripe and Pay.jp: payment processing, if and when you pay us. We never see or store your card details.
How we protect your data
We treat your account data, your work and any Google user data we receive as sensitive data. Security procedures are in place to protect the confidentiality, integrity and availability of that data, and we use encryption to protect your information. Specifically:
- Encryption in transit. Every connection to MangaForge, and between MangaForge and the processors listed above, uses HTTPS (TLS) encryption.
- Encryption at rest. Our database, file storage and backups (Supabase on AWS, and AWS S3) are encrypted at rest with AES-256.
- Access controls. Row-level security in the database ensures each account can read and change only its own data. Administrative access to production systems is limited to a small number of named staff, protected by strong authentication, and used only to operate the service or answer a support request you make.
- Minimal Google data. We request only the
openid,emailandprofilescopes. We do not store Google access or refresh tokens; sign-in gives us a one-time identity token, and we hold no ongoing access to your Google account. - Secrets management. API keys and credentials are kept in our hosting providers’ encrypted secret stores, never in application code or in your browser.
- Payment data. Card details never reach us; they are handled entirely by Stripe and Pay.jp, which are PCI DSS certified.
- Breach response. If we become aware of a security incident affecting your personal data, we will contain it, notify affected users without undue delay, and notify regulators where the law requires it.
How long we keep things
Your work is kept while your account exists, and deleted when you delete it. Waitlist records are kept until you unsubscribe, plus the period we are required to retain proof of consent. Translate jobs are deleted, with their pages and output, 30 days after they finish. Diagnostics are kept for 30 days and then discarded. Anonymous usage counts are kept for up to 12 months. Support chat conversations are kept so we can follow up on them, until you ask us to delete them.
Your rights
You can ask us for a copy of your data, ask us to correct it, or ask us to delete it. On a deletion request we permanently delete your account, your work and any translation files, including the Google profile data described above. You can withdraw consent to email at any time, using the unsubscribe link in any message or by writing to us. Write to privacy@mangaforge.jp and we will respond within 30 days. These rights apply to everyone, wherever you live, including under the GDPR, Japan’s APPI, India’s DPDP Act and California law. You may also complain to your local data protection authority.
Why we use your data, and where it is processed
To run your account and the studio, to bill you, to keep the service secure and fix faults, to answer you, and to send the email you asked for. We rely on your agreement with us, your consent where we ask for it, and our legitimate interest in securing the service. We do not sell personal data, share it for advertising, or make automated decisions about you. We disclose it only to the processors listed above, where the law requires it, or in a merger or sale of the business with the same protections. Our providers run servers in several countries, including the United States and Japan; where you are in the EEA, UK or Japan we rely on the contractual safeguards those providers offer for the transfer.
Cookies and local storage
We use browser storage to keep you signed in and to remember interface preferences such as your theme. If you use Google sign-in, Google’s sign-in script loads from accounts.google.com and Google may set its own cookies. In the studio, the support chat loads Crisp’s script from client.crisp.chat, which keeps your conversation in its own cookies and browser storage; signing out clears it from that browser. We do not use advertising cookies and we do not track you across other sites.
We also count anonymous product usage so we can see what to fix. The app keeps a random identifier in your browser storage for this, which is not tied to your account and is not shared with advertisers. We send no IP address and no content of your work. We honor Do Not Track and Global Privacy Control, and you can switch usage statistics off at any time in Account & preferences, which also deletes that identifier. On this marketing site we count page views and clicks without storing anything in your browser.
Children
MangaForge is not directed at children under 13 (or under 16 where local law sets a higher age), and we do not knowingly collect their data. If you believe a child has given us personal data, write to us and we will delete it.
Changes to this policy
If we change this policy we will update the date at the top. For any change that materially affects your rights or how your work is handled, we will tell you directly rather than rely on you noticing.
Contact
Mangaforge Pvt Ltd, Flat No. G1101, Lotus Elise, Sector 99, Khandsa Road, Gurgaon, Haryana, India 122001. Email privacy@mangaforge.jp. Website: mangaforge.jp.