Privacy Policy
Last updated: September 9, 2026
Version: privacy-v10
Worldbuilders Inc. ("we", "our", "us") operates the Yumeship mobile application ("Yumeship" or the "App"). This Privacy Policy explains how we collect, use, store, share, and protect information when you use the App.
Some Yumeship terms used below: "F/O" means a fictional other; "F/O spaces" are Shippers spaces organized around a fictional other; "doubles" are users who share the same F/O; "Moots" means saved-access Picshare sharing; and hidden F/O preferences such as non-sharing or voidsharing are settings used to control how certain F/O spaces appear to you.
1. Information We Collect
1.1 Content You Create
The App may store the text, images, profiles, templates, albums, stories, messages, reminders, links, customization choices, and other creative or social content you provide.
1.2 Local Device Data
Yumeship is local-first. Your ship data is stored on your device unless a backup, sharing, account, purchase, diagnostics, or sync feature is enabled by the App or your device settings.
When you choose photos, images, or files, the App may access the items you select so it can display, save, edit, export, or share the artifact you requested. Yumeship does not need precise device location for its core private scrapbook features. Location labels in Picshare-style posts are user-entered text unless a future build clearly asks for device location permission.
1.3 Platform Backup
Yumeship may use Apple iCloud / CloudKit private database features, Android Auto Backup, device transfer, or similar platform backup features to help preserve private ship data. Platform backup data is associated with your Apple ID, Google account, or device backup account and handled under that provider's terms and privacy practices. Platform backup is intended for private backup only, not public sharing.
1.4 Optional Account-Linked Backup
If you opt in, account-linked backup uploads supported private content and limited operational metadata to private access-controlled storage. It is separate from social storage, does not publish content, and does not use a custom client-side content-encryption layer. We and our storage provider may access it as needed to operate, secure, troubleshoot, or support the feature.
Backup is not real-time sync. Restore requires your action and may replace local data. We retain supported snapshots as reasonably needed to provide and protect the feature; cross-platform restore may not be supported.
1.5 Account and Sign-In Data
If you sign in for Picshare, Moots, Shippers, comments, or other account features, we may collect account information such as your Sign in with Apple identifier, Google sign-in identifier, name or email address if the sign-in provider provides it, internal user ID, Yumeship username, authentication tokens, and the version and timestamp of your Terms, Privacy, Community Guidelines, and 13+ confirmations.
Your Yumeship username and Shippers profile information are visible to other signed-in Yumeship users within social features when you post, comment, vote, join visible F/O spaces, or use sharing features. Your Apple ID, Google account ID, and email address are not shown to other Yumeship users by us.
1.6 Picshare and Moots Sharing Data
If you enable Picshare or Moots, we upload the sharing-safe profile you select, including its names, profile details, images, captions, user-entered labels, comments, link data, and storage references. Signed-in people with access may view, comment, forward, copy, or capture shared content.
We also process access records, interactions, reports, blocks, moderation status, IP address, request metadata, logs, rate-limit signals, authentication status, and pseudonymous account-linkage or restriction signals to operate and protect sharing.
1.7 Shippers Social Data
If you use Shippers, we collect the profile, posts, media, comments, votes, memberships, preferences, Chat activity, reactions, paid-placement data, reports, blocks, hides, counts, timestamps, and moderation state needed for its features. Visible social data is shown to other eligible users according to the feature and your settings; hidden preferences remain private to you.
Reports, appeals, and moderation records may include account identifiers, reasons, content snapshots, nearby context, decisions, notes, audit logs, linked-account indicators, safety signals, and support messages. Chat messages are ordinarily retained for up to seven days, but reports may preserve relevant content and context longer.
We may review and send shared or social content and related signals to manual reviewers, automated systems, Google Cloud, OpenAI, hash-matching tools, or other safety providers to classify content, investigate reports, prevent abuse or evasion, preserve evidence, and comply with law.
Shippers does not automatically publish private content. A copy you choose to post becomes social content. We do not scan private local content or backups for social moderation unless you submit it to a social feature, report, or support request.
We may retain an opaque device restriction claim after logout or account switching for enforcement, security, and support. It is not a raw sign-in ID, username, or private-content copy and normally clears when local App data is removed.
1.8 Analytics, Public-Content Uses, and Internal Measurement
We may analyze identifiers, platform and app version, feature usage, purchase and entitlement events, sharing and social activity, public votes, reactions, follows, memberships, engagement, notifications, exports, crashes, performance, requests, rate limits, paid-placement activity, related metadata, and aggregated or de-identified trends for analytics, business reporting, research, dataset development, ranking, safety, fraud prevention, support, commercial product development, and service improvement.
We may select content that you intentionally publish through Picshare, Moots, Shippers, or another sharing or social feature, including content made available through KinChat or another connected service, together with its public username, profile name, avatar, caption, handle, voice, likeness, engagement, or other public attribution and metadata, to create, test, publish, monetize, and distribute marketing, paid or unpaid advertising, promotional, app-store, press, research, product-demonstration, and official social-media materials for Yumeship and related services. We and the partners acting for us may edit, crop, resize, excerpt, translate, caption, combine, remove metadata from, or reformat that content for those purposes. We do not use private ship documents, private local scrapbook content, private backups, sign-in identifiers, email addresses, or hidden preferences for advertising.
Subject to applicable law, we may in the future use text you intentionally share publicly through Yumeship for AI model training, after providing notice describing the use and obtaining any legally required consent. Notwithstanding any other content license in our Terms, neither we nor third parties we authorize may use artwork, uploaded media, text extracted from that media, or private content for model training or training datasets. We may use automated tools to review shared content for safety and enforce our policies.
We do not sell your personal information for money or share it for cross-context behavioral advertising, and we do not use third-party advertising trackers. We do not use your private ship documents, private local scrapbook content, or private backups for advertising. If we ever want to use this private content for a materially new purpose, we will ask for your opt-in consent first.
For users who accept Terms containing these uses and acknowledge this Policy, the uses apply to eligible shared or social content and public social activity that remain associated with the account, including material published before that acceptance. If you do not want the expanded uses to apply to existing content, do not accept the Terms; use the available account-deletion process or contact us to request deletion.
1.9 Feedback and Support
If you submit feedback, a bug report, feature request, support message, or similar request, we may collect the message you submit, any optional contact information you provide, your account ID if you are signed in, the source screen or feature, platform, app version, build number, device or operating system details, timestamps, request metadata, and limited anti-abuse signals such as IP address or a derived rate-limit identifier. We use this information to respond to you, understand reported issues, improve the App, and prevent spam or abuse.
1.10 Purchase and Subscription Data
If you purchase Yumeshipper Pro, a Pin Pass, or another paid feature, payments are processed by Apple through the App Store or by Google through Google Play. We use RevenueCat to help validate and manage purchases, purchase status, entitlement access, consumable grants, refunds or reversals, and any legacy subscription status. We do not receive your full payment card information.
We may receive or create account, product, store, transaction, entitlement, environment, status, timestamp, refund, recovery, fraud-prevention, and audit records. Pin Pass ledgers also record grants, balances, consumption, placements, reversals, and eligibility results. Placement labels may be public, but payment identifiers and balances are not.
1.11 Notifications
If you enable notifications, Yumeship may schedule local notifications on your device, including private notes, reminders, anniversaries, or F/O notification text that you create or approve.
1.12 Diagnostics
We may receive basic diagnostics, crash reports, purchase events, subscription events, feature usage events, or app performance information through Apple, Google, RevenueCat, PostHog, or similar service providers. We do not use third-party advertising trackers and do not sell your personal information.
2. How We Use Information
We use information to:
- Provide the App and save your private creative artifacts
- Let you create, edit, organize, export, and share templates, albums, outfits, storylines, shrines, private post-style artifacts, messages, scenarios, and reminders
- Restore or back up data when supported
- Schedule notifications you request
- Provide Picshare sharing, Moots access, Shippers feeds, profiles, posts, comments, Chat, reactions, F/O spaces, usernames, notifications, and "Shared with me" revisit lists
- Validate purchases, maintain consumable balances and purchase ledgers, manage subscriptions and paid access, activate Pinned Posts, process refunds or reversals, recover eligible unused purchases, and prevent duplicate grants or fraud
- Run internal analytics, measure feature usage, understand retention and conversion, improve stability, and fix bugs
- Create, test, publish, monetize, and distribute marketing, advertising, promotional, app-store, press, research, and official social-media materials for Yumeship and related services using eligible shared or social content, public activity, related metadata, and public attribution
- In the future, train artificial-intelligence or machine-learning models using publicly shared text, subject to the notice, consent, and content restrictions in Section 1.8
- Respond to feedback, bug reports, feature requests, and support requests
- Enforce our Terms of Use, investigate reports, prevent abuse, operate blocks and access controls, run manual or automated safety checks, and protect users
3. How Information Is Shared
We do not sell your personal information or share it for cross-context behavioral advertising.
We may share limited information with:
- People or services you choose when you export an artifact, use the system share sheet, save to another app, or open a pasted music or media link
- Other signed-in Yumeship users who have access to a Picshare profile you choose to share, including your shared profile content, visible Yumeship username, and comments
- Other signed-in Yumeship users who can view Shippers social surfaces, including visible profile details, visible posts, comments, Chat messages and reactions, images, visible F/O-space memberships, and related social activity
- Picshare profile owners, who may see your visible Yumeship username and comments on their shared posts
- Apple, for Sign in with Apple, App Store purchases, iCloud/CloudKit, notifications, diagnostics, and device-level services
- Google, for Google sign-in, Google Play purchases, Android backup, diagnostics, device-level services, and Google Cloud services that help with content safety, classification, and moderation
- OpenAI, when configured to provide automated text or image safety classification and moderation
- RevenueCat, for purchase, subscription, and entitlement management
- PostHog, if analytics or diagnostics are configured for the build you use
- Service providers who help operate, host, store, deliver, diagnose, moderate, or support the App, including backend and image-storage infrastructure
- Advertising agencies, creative contractors, app stores, publishers, social-media services, and distribution partners that help us create, place, or deliver Yumeship promotional materials using eligible shared or social content
- Technology, research, and model providers for any future model-training uses of publicly shared text described in Section 1.8, subject to the same notice, consent, and content restrictions
- Legal authorities, NCMEC, or other appropriate safety organizations if required by law or needed to report apparent child exploitation, threats of harm, serious illegal activity, abuse, or risks to users, the App, or our rights
We require service providers that process personal information for us to use it only for authorized services and to protect it consistently with this Privacy Policy, our agreements, and applicable law.
Yumeship is private by default. We do not publish your private ship document. When you turn on Picshare or Moots sharing, only the shared projection and shared images are uploaded for that feature. When you use Shippers, the profile, posts, comments, votes, F/O-space activity, and images you submit to Shippers are stored for that social feature.
When you export an image or share content outside Yumeship, the privacy practices of the destination app, website, or person also apply. We cannot control copies, screenshots, downloads, reposts, or saves made outside Yumeship.
4. Children and Teen Users
Yumeship is not directed to children under 13. We do not knowingly collect personal information from children under 13.
If you are 13 to 17, you may use Yumeship only with permission from a parent or guardian.
If you believe a child under 13 has provided personal information through the App, contact us so we can take appropriate action, which may include deleting the account or related data.
5. Sensitive Content and Personal Information
Yumeship is designed for private creative expression. You should avoid adding real addresses, phone numbers, school names, passwords, financial details, or other sensitive personal information to your ship content.
Do not upload or create content that violates the rights or privacy of another person.
6. Data Retention and Deletion
Local content remains on your device until you remove it. Platform, exported, transferred, and offline copies remain controlled by you or their provider. You can manage account backup, sharing, links, comments, blocks, and social content through available App controls.
You may delete your account in the App, at yumeship.app/delete.html, or through support@worldbuilders.app. We complete verified deletion requests within the period required by applicable law, except for records lawfully retained for legal, dispute, transaction, moderation, fraud, abuse, security, or enforcement purposes. Infrastructure backups are removed or overwritten through our normal rotation.
Retained records may include limited purchase, refund, ledger, placement, moderation, report, appeal, audit, safety, restriction, and linked-account information. Reports may preserve relevant content and context after source content is changed or deleted.
Routine API access and security logs are generally retained for up to 90 days. We may preserve limited relevant records longer when they are connected to a safety report, security investigation, legal obligation, dispute, fraud, abuse, or enforcement matter.
Subject to applicable law, deleting shared or social content does not require recall or destruction of advertising or promotional materials already created, commissioned, committed, scheduled, or distributed. Archival, compliance, distributed, and non-identifying derived materials, including aggregated measurements and system improvements, may remain. Any future retention of trained models or safety classifiers derived from your content is subject to the model-training restrictions in Section 1.8 and applicable law.
For support with privacy, access, correction, deletion, or other privacy rights questions, contact us at support@worldbuilders.app.
7. Security
We use reasonable safeguards to protect information we process. However, no method of storage or transmission is completely secure. You are responsible for keeping your device, Apple ID, Google account, App Store account, and Google Play account secure.
8. Your Choices
You may avoid sign-in, sharing, social features, backup, notifications, and paid placements and continue using available local features. Manage permissions and data through the App and your device, Apple, or Google settings.
Changing accounts, deleting, logging out, or reinstalling does not defeat a continuing social restriction. Use support to request review.
Depending on where you live, you may have privacy rights such as requesting access, deletion, correction, or information about how your personal information is used. You can contact us to make a request.
9. Changes
We may update this Privacy Policy from time to time. We will update the "Last updated" date when changes are made. If changes are significant, we may provide additional notice in the App or on our website and require acknowledgment before you continue using affected online features.
10. Contact
Questions about this Privacy Policy can be sent to: