← Back to Home

Privacy Policy

Last updated: June 26, 2026

1. Overview

Parable Post (“we,” “us,” “our”) provides personalized children’s stories, illustrations, proofing, gift, and mailing services for parents and guardians. This Privacy Policy explains what we collect, how we use it, and when service providers process it for us.

Parable Post is designed for adults. We do not ask children to create accounts or provide information directly. Child information is provided by a parent, legal guardian, gift buyer, or parent-approved recipient as part of creating or delivering a story.

2. Child Information and Parent Consent

Parents and guardians are responsible for providing any child information used by the Service and for reviewing child-facing content before it is shared with a child. Depending on the product flow you use, child information may include:

  • Child first name, age or birthday age, pronouns, interests, family details, developmental goals, accessibility needs, and special requests.
  • Optional appearance descriptions or photo-analysis descriptions used to guide illustrations.
  • Generated stories, titles, illustrations, proof status, approval/rejection status, delivery status, and related order or gift details.

We use child information to personalize, review, print, mail, support, and improve the requested Parable Post experience. We do not sell child information or use it for behavioral advertising. We do share or disclose child information to service providers when necessary to operate the Service, as described below.

3. Information We Collect

From parents, guardians, gift buyers, and account users:

  • Name, email address, phone number, mailing address, account credentials, consent preferences, support messages, and notification preferences.
  • Payment, subscription, gift, refund, cancellation, chargeback, and checkout metadata processed through Stripe. We do not store full card numbers.
  • Newsletter opt-in details, marketing source, referral, UTM, click-ID, and attribution data when you interact with marketing pages or forms.

From your use of the Service:

  • Story prompts and preferences, generated stories and illustrations, proof links, approval choices, delivery events, email/SMS interaction details, and support/chat content if enabled.
  • Device, page, referrer, analytics, localStorage, cookie, log, diagnostic, and security data used for attribution, reliability, fraud prevention, and site operations.

4. AI, Photos, Illustrations, and Proof Links

Personalized stories and illustrations may be generated or reviewed using AI providers. Current source-backed product paths use Google Gemini and may use OpenAI as a fallback when configured. Inputs can include child name, age, pronouns, interests, family details, developmental goals, appearance descriptions, accessibility needs, story text, and illustration prompts.

If a photo-analysis feature is used, the uploaded photo is sent to Gemini Vision for analysis and the Service returns a short appearance description. The app code states that the photo itself is not stored by that route, but the resulting description may be used for illustration personalization.

Generated illustrations and proof assets may be stored or rendered through public or bearer-style URLs unless a product flow says otherwise. Do not include information in prompts, photos, or proof flows that you are not comfortable having processed by Parable Post and its service providers for the requested story, proof, and fulfillment purposes.

5. Analytics, Cookies, and Local Storage

Parable Post uses analytics and attribution tooling to understand traffic, marketing performance, and product reliability. This can include Google Analytics/Google Tag Manager, LexyAlgo/first-party attribution collectors, Mautic tracking when configured, Cloudflare analytics, and browser localStorage/sessionStorage for anonymous IDs, sessions, landing pages, UTM parameters, and advertising click IDs.

We do not use child information for behavioral advertising. Analytics and attribution tooling may still run on public product pages unless disabled for a specific route.

6. Service Providers

We use service providers to host, secure, generate, communicate, process payments, fulfill orders, measure performance, and support the Service. Depending on which features are enabled and which flow you use, service providers may include:

  • Supabase/Postgres and Prisma-backed infrastructure for app data, accounts, generated content, and operational records.
  • Stripe for checkout, subscriptions, invoices, refunds, disputes, gifts, and payment metadata.
  • Google Gemini and, if configured, OpenAI for story, title, illustration, photo-analysis, and content-quality workflows.
  • Lob for printing and mailing physical letters, including recipient address, child name, story/illustration content, and fulfillment metadata needed to mail the item.
  • Twilio for SMS notifications when you opt in or when a product flow sends operational text messages.
  • Hostinger SMTP/Nodemailer or other configured email infrastructure for account, approval, proof, and delivery emails.
  • Mautic for parent newsletter and marketing automation when you opt in or when tracking is configured.
  • Google Analytics, LexyAlgo attribution, Cloudflare Insights, Sentry, and optional Chatwoot for analytics, attribution, error monitoring, infrastructure, and support chat.

Service providers are used to perform services for Parable Post. We do not sell personal information or child information.

7. SMS and Email Communications

If you opt in to SMS messages, we may send recurring automated texts about account updates, story approvals, proof links, delivery notifications, and occasional promotional offers. Consent to SMS is not a condition of purchase. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help.

We also send operational emails for account, proof, approval, rejection, delivery, support, and subscription purposes. Marketing emails are sent only where we have an opt-in or another permitted basis.

8. Security

We use safeguards intended to protect personal information, including HTTPS/TLS in transit, hashed passwords, role-based/admin restrictions, production monitoring, and application-level access controls. Some child-name encryption and audit/logging controls depend on the current production configuration and product path; we do not promise that every field, log, provider record, email, SMS, payment metadata field, proof page, or fulfillment record is encrypted or hidden from administrators.

No online service can guarantee absolute security. Please use strong account credentials and avoid submitting unnecessary sensitive information.

9. Retention, Review, and Deletion

Parents may review and update child profiles and generated content through available account features. Child-profile deletion is available in the dashboard where implemented. Full account closure, deletion of generated content, payment records, fulfillment records, logs, backups, and service-provider records may require contacting us and may be limited by legal, security, tax, accounting, dispute, backup, or operational retention needs.

To request access, correction, deletion, or withdrawal of consent for child information, contact [email protected]. We may need to verify your identity and relationship to the child before fulfilling a request.

10. Contact

For privacy questions or requests, contact [email protected].