Terms & Privacy
Terms of Service and Privacy Notice for Fablemancer.
Terms of Service
Last updated: 2026-09-08
1. Acceptance of Terms
These Terms govern your access to and use of Fablemancer, a web-based immersive reading service provided by Moonridge AB ("Fablemancer", "we", "us", or "our"). By creating an account or using the service, you agree to these Terms.
If you use Fablemancer with a child, you confirm that you are the child's parent or legal guardian, or that you have permission from the parent or legal guardian to supervise that use. Accounts are intended for adults, not for children to create independently.
2. Service Status
Fablemancer is in an early launch stage. Features, content, pricing, availability, and technical behavior may change as we develop the service.
We aim to provide a stable and careful service, but we do not guarantee that it will always be uninterrupted, error-free, or available on every device or network.
3. Accounts and Security
You may sign in with an email and password or, if you choose, with Google. You are responsible for keeping your sign-in method secure and for activity that happens through your account. You should use an email address or Google Account that you control and tell us promptly if you suspect unauthorized access.
We may restrict or suspend access if we reasonably believe an account is being misused, creates security risk, violates these Terms, or is required to comply with law.
4. Parent and Guardian Use
Fablemancer is built for family reading experiences, but the account holder remains responsible for supervising any child who uses the service.
Do not submit child names, ages, school information, or other child personal data unless we have introduced a specific feature that asks for it and explains how it will be handled.
Optional analytics consent is separate from accepting these Terms and can be refused or withdrawn without losing service access.
5. Content and Intellectual Property
The service, software, artwork, audio, text, designs, and other content are owned by us or our licensors and are protected by intellectual-property laws.
We grant you a limited, personal, non-exclusive, non-transferable right to use Fablemancer for its intended reading experience. You may not copy, redistribute, sell, publicly perform, reverse engineer, or create derivative services from the service or content except where we expressly permit it. A media file being technically reachable through a public delivery URL does not grant any additional permission to use or redistribute it.
6. Acceptable Use
You agree not to:
- Use the service unlawfully or in a way that infringes another person's rights.
- Attempt to bypass access controls, security controls, or role restrictions.
- Interfere with the service, scrape it at scale, or overload its infrastructure.
- Upload or submit content unless a feature explicitly allows it.
7. Payments and Paid Features
Apprentice is free and includes one complete book and story-audio customization. Mage includes the full published library and story-audio customization for 49 SEK per month or 490 SEK per year, including applicable VAT. The selected Mage period renews automatically until canceled. There is no launch trial or promotion-code program.
Stripe provides the hosted checkout and billing portal and handles payment-card details. Mage access begins only after payment is confirmed. You can use the portal to update your payment method, view invoices, switch between monthly and yearly billing with Stripe's displayed proration, or cancel at the end of the current billing period. Access normally continues until that period ends. Failed payments may be retried and can eventually end Mage access.
To use a 14-day right of withdrawal at launch, contact us. We will handle the request manually by immediately canceling the subscription and issuing a full refund where that right applies. This does not limit mandatory consumer rights. Other refund requests are assessed under applicable law and the circumstances of the request.
8. Disclaimers and Liability
Fablemancer is provided on an "as is" and "as available" basis during its early launch. To the extent permitted by law, we disclaim implied warranties of availability, fitness for a particular purpose, and non-infringement.
Nothing in these Terms limits rights that cannot be limited under mandatory consumer law. To the extent permitted by law, our liability is limited to direct losses that were reasonably foreseeable and caused by our breach of these Terms.
9. Changes to the Service or Terms
We may update the service and these Terms as Fablemancer develops. Material changes will be reflected by updating this page and, where appropriate, giving additional notice.
If you continue using the service after updated Terms take effect, the updated Terms apply to your continued use.
10. Governing Law and Contact
These Terms are governed by Swedish law, except where mandatory consumer-protection rules give you additional rights in your country of residence. Disputes should first be raised with us so we can try to resolve them informally.
Email: support@fablemancer.com
Privacy Notice
Last updated: 2026-10-11
1. Who We Are
Moonridge AB is the controller for personal data processed through Fablemancer. Fablemancer is an immersive reading service for parent- or guardian-led family reading.
This Privacy Notice explains what we process at launch, why we process it, the legal bases we rely on, how long we keep it, and the rights you have under the GDPR.
2. Launch Data We Process
We currently keep data collection narrow:
2.1 Account and authentication
We process your email address, password/authentication credentials handled by Supabase, session tokens, sign-in state, and password reset information so you can create and access your account. If you choose Google sign-in, Google and Supabase provide us with a Google account identifier, your email address and verification status, and basic profile information such as your name and profile picture where available. Fablemancer does not receive your Google password, request access to Gmail, Contacts, Drive, or other Google services, or intentionally retain Google provider access or refresh tokens for API use. Legal basis: performance of a contract.
2.2 Profile and preferences
We process your user ID, role, and reader/audio settings such as preferred audio level, volume defaults, and marker-control mode. Legal basis: performance of a contract and our legitimate interest in providing a reliable, role-aware service.
2.3 Technical, security, and support data
We process technical logs, request metadata, device/browser information, errors, and support messages where needed to operate, secure, debug, and support the service. Legal basis: legitimate interests and, where applicable, legal obligation.
To limit automated abuse, we keep security counters in our EU database using keyed hashes derived from IP addresses or account identifiers, without storing those raw values in the counters. Counter windows expire within one hour; expired records are removed when the next limited request is processed. Legal basis: our legitimate interest in securing the service.
2.4 Analytics and performance
Without optional analytics consent, we count limited daily service outcomes: catalogue requests, published book content served, access gates, and categorized server failures, including checkout and billing-portal service failures. These counters contain no visit identifiers or individual event histories. Existing account and billing records provide business totals separately. Our legal basis for these limited secondary operational statistics is our legitimate interest in understanding demand and service friction, balanced against family users’ interests. You can object to optional aggregate usage counting in Privacy settings. Landing-page document deliveries are also counted by opening variant, language and existing consent category. These are requests, not unique visitors, views or conversions. No experiment cookie or fingerprint is created without consent.
Only if you allow analytics do we connect actions within a short visit and measure coarse reading interactions, including active interaction time, progress bands, tutorial outcomes, control choices, library filter categories and sign-in/sign-up outcomes. With consent already valid when a document loads, we classify its referral as search, social, another site, an internal link or no referrer reported. We store only the category, not the referring URL, hostname, path or campaign text. Visits consented after load and older visits remain unattributed. Supabase stores this product analytics; Vercel supplies optional performance measurements with sanitized route URLs; Vercel Web Analytics is not mounted. Legal basis: consent. We do not collect search text, raw words, email addresses or account IDs in journey events, infer reading ability, create child profiles, or use analytics for advertising. For the current landing-page comparison we record the displayed four-scene version, observed opening and final-scene exposure, link destination and placement, demo attempts and six logical sound cues, sound activation outcome, and subsequent free-book reading starts and attributable checkout/payment outcomes. Historical landing-opening-v1 records keep their original displayed-opening identity. We record no pointer paths or microphone data and do not replay activity from before consent. The displayed variant is attached only to the existing consented visit. Updated analytics choices require fresh consent; an earlier objection to aggregate usage remains effective while that choice is pending. Vercel flag configuration receives no account identifiers or visit tokens; flag evaluation metrics and browser reporting are disabled.
A random first-party visit token expires after 30 minutes without activity or 24 hours at the latest. Visits are not connected across devices or visits. A consenting checkout can temporarily be associated with its visit to confirm the first payment from billing records. Missing attribution is not treated as refusal. Withdrawal stops optional collection; other open pages apply the change on focus or within a minute. Our server checks the account choice before accepting new journey events. Withdrawal also stops pending collection and deletes the current retained visit detail and pending checkout association; anonymous totals cannot be traced back and removed.
2.5 Transactional email
Supabase uses Resend as our email-delivery provider for account confirmation, password reset, and other necessary service messages. Resend processes the recipient email address, message content and headers, delivery events, and technical logs needed to send, troubleshoot, and secure those messages. Legal basis: performance of a contract and our legitimate interests in reliable and secure delivery.
2.6 Payments
If you start or manage a Mage subscription, Stripe processes account and billing contact details, billing address and location evidence, payment method and card details, subscription, invoice, tax, payment, refund, and fraud-prevention data. Fablemancer stores only internal plan intent, Stripe Customer/Subscription/Checkout references, billing interval and status, renewal/cancellation dates, and minimal webhook event identifiers needed to provide access, prevent duplicate processing, support you, and meet legal obligations. We do not receive or store full card numbers or CVCs and do not retain raw Stripe webhook payloads. Legal bases: performance of a contract and legal obligation.
Fortnox's native Stripe integration receives live Stripe customer, transaction, invoice, fee, refund, dispute, balance, and payout information needed for bookkeeping, reconciliation, tax returns, and legal accounting records. The Fablemancer application does not send data directly to Fortnox, and the Stripe sandbox is not connected to Fortnox. Legal basis: legal obligation and our legitimate interest in accurate financial administration.
3. Children and Family Use
Accounts are intended for parents or legal guardians. Children may use the reading experience with adult supervision, but we do not ask children to create accounts and we do not intentionally collect child names, ages, school information, or child profiles at launch.
If you believe a child has provided personal data directly to us without appropriate adult involvement, contact us so we can review and delete it where required.
4. Cookies, Local Storage, and Similar Technologies
Necessary browser storage supports authentication, language, theme, sign-in redirects and logout. The fm_privacy cookie remembers your analytics choice, aggregate objection, notice version and date. Guest choices last 180 days. Signed-in choices are saved with your account for 365 days and restored across devices without renewing the date. We keep only your latest choice, separately from reading data, based on our legitimate interest in respecting privacy preferences. Expired account choices are deleted within 15 minutes, or immediately when the account is deleted. Material changes to analytics purposes require fresh consent. The optional HttpOnly fm_visit cookie holds a random visit token only after consent. No persistent offline analytics queue is stored.
If you choose Google sign-in, you leave Fablemancer for Google's authentication page. Google may use its own cookies or similar technologies there under Google's privacy terms; Fablemancer does not place Google advertising or analytics scripts on its own pages for this sign-in flow.
Allowing and declining optional analytics are equally available and do not affect access or price. Change your choice or object to optional aggregate counting in Privacy settings in the site navigation, footer or reader More menu. Necessary security and billing processing continues. We do not use advertising trackers. An adult should make the privacy choice when reading with a child.
5. Processors and Sharing
We do not sell personal data. We share personal data only where needed to provide, secure, support, or comply with legal obligations for the service.
Current providers include Supabase for authentication and the database; Vercel for web hosting, performance measurement, and public Blob media storage; Resend for transactional email; Google as an optional independent sign-in provider chosen by the user; Stripe for hosted checkout, subscriptions, invoices, tax, receipts, refunds, payment methods, fraud prevention, and payment webhooks; and Fortnox for live bookkeeping and reconciliation through its native Stripe integration. We aim to use providers under appropriate data-processing, confidentiality, security, and transfer terms.
Story images and audio are stored in a public Blob store for efficient delivery. Anyone who obtains an exact direct Blob URL can technically access that file. At launch these files contain Fablemancer story media, not account/profile data or ordinary user uploads.
News drafts are stored as records in our EU Supabase database, and uploaded article images are stored in a separate private EU Blob store. Only authorized editors can preview unpublished content. Publishing makes the selected article and image variants publicly accessible; withdrawing an article cannot recall copies already downloaded or retained by search and social platforms.
6. International Transfers
Fablemancer's primary Supabase authentication and database project is located in Stockholm, Sweden. This improves proximity and keeps primary account/database storage in the EU, but it does not mean every provider operation stays in Sweden.
Resend's primary processing and account-data storage, including email metadata and delivery logs, takes place in the United States. Google, Vercel, Stripe, Fortnox, and provider subprocessors may also process data outside Sweden or the EEA. Where a restricted transfer occurs, we rely on applicable safeguards such as EU adequacy decisions, standard contractual clauses, or other lawful transfer mechanisms.
7. Retention
We keep personal data only for as long as needed for the purposes described in this notice. Account, Google sign-in linkage, profile, and settings data are kept while your account is active. Transactional email delivery records, support data, and security records are kept according to the active provider settings and only as long as needed for delivery, support, security, legal claims, fraud prevention, or legal obligations.
Billing, invoice, tax, refund, payout, and related support records are kept for the periods required by Swedish tax, accounting, consumer-rights, fraud-prevention, and legal-claims rules, including after account closure where required. When no continuing purpose or legal obligation remains, we delete or anonymize app billing references according to the applicable provider and backup lifecycle.
Consented visit detail is retained for at most seven days plus the 15-minute maintenance interval, temporary checkout associations for at most 24 hours, and coarse daily analytics aggregates for 13 months. Admin reports suppress small breakdowns and never expose individual sessions. Vercel’s separate optional performance reports and any previously retained Web Analytics reports follow the active provider retention settings; these are not the Supabase seven-day store. Provider backups follow their separate lifecycle.
Editorial drafts, published articles, and their images are retained while needed for publication, revision, or the news archive. Editors use the existing account role for authorization; articles display a team byline rather than a personal author profile.
8. Your GDPR Rights
Subject to the GDPR's conditions and limits, you may have the right to:
- Access personal data we hold about you.
- Correct inaccurate or incomplete data.
- Delete data or ask us to restrict processing.
- Object to processing based on legitimate interests.
- Receive data portability where applicable.
- Withdraw consent where processing is based on consent.
To exercise these rights, contact us at the address below. You also have the right to lodge a complaint with Integritetsskyddsmyndigheten (IMY), the Swedish Authority for Privacy Protection.
9. Security
We use technical and organizational measures intended to protect personal data, including account authentication, server-side access controls, row-level database policies, role checks for creator/admin features, minimized analytics payloads, and a separate server-only token for the active media store. Public story-media URLs are not treated as an access-control mechanism. No service can be guaranteed perfectly secure, but we design for data minimization and controlled access.
10. Changes and Contact
We will update this notice when our data practices materially change, including before introducing child profiles, ordinary user-generated content, marketing tracking, broader analytics, referral processing, or AI-assisted story creation.
For privacy questions or rights requests, contact us via:
Email: support@fablemancer.com
