How Trimora handles your account, your manuscript, and who owns it

This page explains what Trimora stores, where it lives, who can reach it, and — plainly — that your book stays yours.

Effective date: October 12, 2026 · Applies to: Trimora, at trimora.ysmsolutions.app · Governing entity: YSM Solutions LLC, a Pennsylvania limited liability company

1. Who we are

Trimora is a manuscript-formatting service for authors preparing a book for Amazon KDP, operated by YSM Solutions LLC, a Pennsylvania limited liability company ("YSM Solutions," "we," "us"). You upload a manuscript once, and Trimora produces three edition-specific outputs from it — a Kindle EPUB, and paperback and hardcover print PDFs — along with the front matter, back matter, and cover-facing illustrations you configure along the way.

This policy covers Trimora itself: the account you create, the manuscript and book settings you enter, and the files you export. It does not cover Amazon KDP, or anything that happens after you upload a finished file there — that's governed by Amazon's own terms.

2. Information we collect

Category	What it includes	Where it comes from
Account information	Name and email address associated with your sign-in	Provided when you create an account (including via Google sign-in, if you choose it)
Manuscript & book content	Your uploaded manuscript, chapter text, titles, subtitles, dedication and epigraph text, author bio, and any images you attach — a cover illustration, an author photo, a publisher logo, or a chapter-opener illustration	Entered or uploaded by you while working on a book
Book & edition settings	Trim size, margins, fonts, header/footer text, ISBNs you enter, and similar formatting choices	Entered by you on each edition's settings page
Subscription status	Whether you have an active subscription and which plan — not your card number or billing address	Reported to us by our payment processor after checkout, and whenever your subscription changes
Basic technical data	Standard web request information (e.g. IP address, browser type) that any server sees, used for security and troubleshooting	Generated automatically by your browser when you use the app

We do not collect payment card details ourselves at any point — see Section 6 for how payment is actually handled.

3. Where your data lives

Everything you enter into Trimora — manuscript text, chapter HTML, front and back matter, uploaded images, and edition settings — is stored in a hosted database operated on our behalf by our infrastructure provider. Nothing about your book is stored on your own device by Trimora itself, other than the file your browser holds briefly while you're uploading a manuscript or downloading a finished export.

When you open a print preview, Trimora renders the actual PDF you'd get from a real export and may keep a short-lived copy of that rendered file so a second look at the same, unchanged preview doesn't require regenerating it from scratch. That cached copy is discarded and rebuilt automatically the moment you change anything the PDF depends on.

4. Encryption in transit and at rest

Trimora's database — everything described in Sections 2 and 3 — is hosted on Neon, a managed PostgreSQL provider that encrypts all stored data at rest using AES-256, and requires a TLS-encrypted connection for every connection made to it — including the one Trimora's own server uses to read and write your books. Your connection to Trimora itself is served over HTTPS, so nothing you type into the app — your manuscript, your settings, your sign-in — travels unencrypted between your browser and our server.

The two specialist providers named in Section 6 go further, because of what they specifically hold:

Stripe, which processes your payment, is certified to PCI Service Provider Level 1 — the most stringent level available in the payments industry — and states that card numbers are encrypted at rest with AES-256. Trimora never receives your card number in the first place (Section 2), so this protection applies before that data would ever reach us.
Clerk, which manages your sign-in credentials, states that it protects account data both in transit and at rest using "industry standard encryption technologies." Clerk's own published materials don't name a specific cipher, so that claim is reported here as Clerk states it, not independently verified by us.

Links above go to each provider's own current security documentation, so this section can be re-checked against their live claims whenever this policy is reviewed.

5. Your data is isolated to your account

Every book, chapter, front-matter page, back-matter page, and edition setting in Trimora is tied to the account that created it. Every request the application makes to read or change that data is scoped to the signed-in owner of that book — there is no feature in Trimora for viewing, editing, or exporting a book that belongs to another account, and no shared or public workspace exists. Signing in as yourself is the only way to reach your own books.

As with any hosted service, a narrow set of authorized personnel may access account data where necessary — for example, to investigate a bug you've reported, respond to a legal request, or maintain the security of the system. That access is not something any other Trimora user has, and it is not used to read or repurpose your manuscript for any other reason.

6. The services we rely on

Trimora doesn't build its own authentication or payment systems from scratch — we rely on specialist providers for both, and each only receives the narrow slice of data it needs to do its job:

Clerk handles account creation and sign-in, including "Continue with Google." Clerk manages your credentials directly; Trimora never sees or stores your password.
Stripe handles billing for your subscription (monthly or yearly) and any plan change, cancellation, or refund you make. Stripe collects and stores your payment details directly; Trimora only ever learns your subscription's status and which plan you're on, and stores nothing more than that against your account.
Our hosting and database provider stores the application's data (Section 3) and runs the server that renders your previews and exports.

Each of these providers has its own privacy policy governing the data it holds directly: Clerk's Privacy Policy and Stripe's Privacy Policy.

7. Your content, your copyright

You own everything you put into Trimora. Your manuscript, your title and cover text, your illustrations, your author bio — all of it remains your copyrighted work, exactly as if you'd formatted it yourself in any other tool. Uploading a manuscript to Trimora does not transfer, license, or assign any ownership or rights in that work to us.

We use your content for exactly one purpose: to generate the previews and exports you ask for — the Kindle, paperback, and hardcover editions of your own book. We do not read, use, or repurpose your manuscript for any other reason. In particular, we do not use your manuscript, your illustrations, or any other content you upload to train artificial intelligence or machine-learning models of any kind, ours or anyone else's, and we do not sell it or license it to any third party.

When you delete a book (Section 8), the copy Trimora holds is removed — that action is yours to take at any time, on any book, for exactly this reason.

8. Retention & deletion

You can delete any book from your dashboard at any time. Doing so permanently removes that book's chapters, front matter, back matter, edition settings, uploaded images, and any cached export for that book — this isn't a soft delete or a trash folder, it's real removal from the database.

You can also request that your entire account and everything associated with it be deleted outright — contact us (Section 12) to request this. Doing so permanently removes your account and every book, chapter, and image tied to it, subject to anything we're required to retain for legal, security, or fraud-prevention purposes.

9. Cookies & sessions

Trimora itself doesn't set advertising or tracking cookies. Clerk sets a session cookie so you stay signed in between visits, and Stripe may set cookies of its own while you're completing a purchase on its checkout page. Neither is used by Trimora to track you across other sites.

10. Children's privacy

Trimora is intended for authors preparing a book for publication and is not directed at children. We do not knowingly collect information from anyone under 16. If you believe a child has created an account, contact us and we'll remove it.

11. Changes to this policy

If this policy changes in a way that meaningfully affects how your data is handled, we'll update the effective date above and make reasonable efforts to let signed-in users know before the change takes effect.

12. Contact

Questions about this policy, or a request to delete your account, can be sent to [email protected].

Back to Trimora