Name Jar Privacy Policy

This policy covers the Name Jar mobile app, including its limited testing releases, operated by Green Bean Studio. For privacy questions or requests, contact support@greenbean.studio. Website visits are covered by our website privacy policy.

Testing notice: Features differ by platform and build. The current Android closed-test build uses test ads and disables new purchases. Shared features require a working account connection and may be unavailable in a test build. The descriptions below explain data handling when each feature is available; they do not promise access to unfinished features.

Solo names stay on your device

You can browse names and use a free solo jar without an account. Saved names, categories, decoration, and selections are stored in the app's local storage. Name Jar does not automatically sync or upload that solo jar when you sign in or purchase a shared jar. Removing app data or uninstalling can remove your only copy. Your operating system's backup and restore settings may separately affect local app data.

You can explicitly export a solo backup and choose where to save or share it. The exported file contains your saved names. Import previews let you confirm what to merge. Copying selected solo names into a shared jar is a separate confirmation and uploads only the selected content; the original solo jar remains local.

Accounts, shared jars, and invitations

When you use connected features, Firebase Authentication processes your sign-in identity and provider profile information, such as account ID, email address and display name where supplied. Firebase/Google Cloud stores and processes shared jars, membership roles, invitations and expiration, names you submit, categories, selections, and the records needed to operate and protect these features. Technical services may process IP addresses, device or app information, request times and security signals. App Check and Play Integrity help check whether requests come from an authentic app and device.

A shared jar is visible to its authorized participants according to their roles. Treat invitation links as private: someone who receives a valid invitation may be able to join. Name Jar does not include your saved names or invitation codes in advertising keywords or custom analytics parameters.

Suggestions are conditionally anonymous

Contributors sign in, and the Name Jar service can associate them with their suggestions. While a jar is open, owners and other contributors do not see who submitted a suggestion. When a name is selected, the owners can see the contributors who independently submitted that name. This is anonymity from other participants until selection, not anonymity from the service. A reveal already shown to someone cannot be withdrawn from their memory, screenshots or copies.

Advertising and consent

On Android, free solo users and invited contributors can be eligible for Google AdMob banners. Free solo discovery can also show occasional interstitials after a completed name choice. A paid jar's owner and co-owner do not request or display ads while using that jar. Name Jar does not offer rewarded or app-open ads, and the current iOS integration does not request ads.

Android ad requests are non-personalized and restricted to G-rated ad content. Non-personalized does not mean that no data is processed. Google and its advertising partners may process IP-derived approximate location, device or app identifiers, device characteristics, ad interactions and technical diagnostics for ad delivery, security, frequency limits and reporting. Name Jar sends no names, pregnancy or relationship information, jar contents, or discovery filters as ad-targeting keywords.

Eligible placements use Google's User Messaging Platform (UMP) to check consent requirements before requesting ads. If the consent check fails, no ad request is made. Open Settings & privacy → Ad privacy options to review choices when Google requires or provides a privacy form. Choices depend on region and provider configuration. Test ads can still involve SDK network requests. See Google's privacy policy and how Google uses information from apps that use its services.

Optional analytics and diagnostics

In builds that support it, Firebase Analytics starts collection only after you opt in. It can process automatic install, app-launch and session events, app-instance identifiers and technical device information. Name Jar does not set a custom user ID or send saved names, profile identities, jar identifiers, invite codes, relationship information or other user-entered content as custom analytics data. Analytics consent does not grant advertising storage, ad-user-data sharing or personalization consent. You can turn analytics off in Settings; the app disables collection and resets local analytics data. This does not itself erase reports already processed by the provider.

Support diagnostics shared by the current app contain bounded categorical status/error information. You choose whether and where to share them. Backend services and hosting providers can process operational and security logs. TestFlight, Google Play and your device platform may separately process testing, crash or usage information under their own settings and policies.

Purchases, when available

Apple or Google handles storefront payment information; Green Bean Studio does not receive your full payment-card details. A supported shared-jar purchase is a one-time purchase for that jar, not an account-wide subscription. Verification can process product and package identifiers, purchase evidence, order references, one-way purchase claims, credits, license status and refund/security records. Android purchase tokens are sent for verification but are not stored or logged by Name Jar's verifier. A purchase does not automatically upload your solo names. New purchases are disabled in the current Android closed test.

Notifications and optional on-device features

If you opt into shared-jar notifications, Name Jar processes the private device push token and notification preference. A selected-name notification avoids putting the chosen name, jar or contributor identity in lock-screen text. You can disable notifications in the app or device settings.

When enabled on supported Apple devices, optional intelligence features process prompts and generated results on the device with no cloud-model fallback. These inputs and outputs are not uploaded or retained by Name Jar. Optional taste memory is off by default and stores only a bounded list of public catalog identifiers and keep/pass choices locally, excluded from device backup. Turn it off or choose Forget discovery choices to erase that memory. These features may be absent in testing releases.

Retention and deletion

Local data remains until you remove it, clear app storage or uninstall, subject to device backups. Shared account and jar data is kept to provide the connected service until the applicable account or jar is deleted. Exported files and copies made by other people remain under their control.

Account deletion removes the account, profile, devices, memberships, and every jar owned by that account, including its invitations, suggestions and licenses. Open-jar contributions are withdrawn. In a finalized jar owned by someone else, previously disclosed selection history can remain until that owner deletes the jar; private authorship is detached from the deleted account.

Minimized purchase replay-prevention records and deletion-job receipts may remain for fraud prevention, transaction reconciliation and reliable completion of deletion. The current testing service does not automatically expire these records, so they may be retained indefinitely for those purposes. Support correspondence, security and operational records may be retained while needed to resolve requests, protect the service, handle disputes or meet legal obligations. These exceptions do not retain a backup of deleted jar contents. Provider-managed records follow the relevant provider's policies and service configuration. Contact us to ask which records remain in your case.

Use the app's Delete account action when available, or request deletion without reinstalling the app through our account-deletion page. We verify ownership before deleting cloud data. Signing out or uninstalling alone does not delete a server account. Deletion is not complete until the service or support confirms completion.

Service providers, security, and your choices

Data is processed by Green Bean Studio and providers needed for the features above, including Firebase/Google Cloud, Google AdMob and its partners, Apple/Google storefronts, hosting and email providers. Providers may process data outside your country. We may disclose information when required by law or reasonably necessary to protect users, prevent abuse or resolve legal claims. Networked services use encrypted connections, but no system is completely secure.

You can use solo features without creating an account; control analytics, ad privacy and notification choices; export available data; leave a shared jar; or request account deletion. Depending on where you live, you may also have rights to access, correct, delete, restrict or object to processing. Contact support@greenbean.studio to exercise rights or ask a privacy question.

Feedback you choose to send

If you submit in-app testing feedback, the service receives your message, feedback category, account association, app version, build, platform and current app screen. It may also receive the diagnostic metadata attached by the feedback feature, such as device model, manufacturer, operating-system version, language/locale, physical-device status and a test-session identifier. We use this information to investigate problems and improve the app. Do not include sensitive names or private links in feedback. Account-linked test feedback is removed by the account-deletion process.

Children and support

Name Jar is intended for parents and other adult participants, not as a service directed to young children. If you believe a child has supplied personal information, contact us so we can investigate and handle the request.

If you email support, we receive your email address, message and any attachments you choose to provide. Do not send passwords, authentication codes, payment-card details or private invitation links. We will update this page when Name Jar's data practices change.