Privacy Policy

Juno Labs LLC (Juno, we, us) operates planwithjuno.app and the Juno applications. This policy covers our websites, couple and planner workspaces, connected-account features, guest-facing wedding websites, RSVPs, registries, and support. It explains information handling; it is not consent to marketing or permission to access a mailbox.

Couples, planners, and other workspace organizers decide what information to add and whom to invite. When a planner handles information for a client, the planner may have separate privacy obligations and policies. Contact the organizer about its decisions and contact Juno about our service or a privacy request. Third-party websites and services have their own policies.

Account and contact information: names, email addresses, phone numbers, profile details, sign-in identifiers, authentication records, connected-account permissions, legal acknowledgments, and communication preferences. We receive information from you and the identity provider you choose.

Planning and collaboration information: wedding dates and locations, budgets, quotes, venue and vendor selections, contracts or files you upload, tasks, notes, messages, room blocks, guest lists, households, seating, meal preferences, accessibility requests, RSVPs, invitation status, and other details you or an authorized collaborator adds.

Guest and public-site information: names and contact details supplied by an organizer or guest, RSVP responses, meal and attendance choices, website stories and photos, registry links, reported gifts, contributions, and gift-link activity. A gift report is not necessarily a verified payment.

Connected-service information: the account identity, authorization tokens, messages, message status, contacts, or calendar information needed for the integration and permissions you enable. Specific email practices appear below. We may receive delivery status and other service events from providers.

Billing and support information: subscription plan, purchase and transaction identifiers, entitlement status, billing history, support messages, and information you supply about a problem. Payment processors and app stores handle payment credentials; Juno receives the information needed to administer access, accounting, refunds, and fraud prevention.

Technical and usage information: IP address, browser and device details, app version, timestamps, diagnostic and security events, pages and features used, visitor and session identifiers, referral sources, campaign parameters, and outbound clicks. We may associate activity with an account when you sign in. Venue and vendor information may also come from public sources, providers, partners, or the business itself.

We use information to create and secure accounts; maintain workspaces; research and compare options; organize conversations and planning records; provide drafting and planning assistance; process invitations and RSVPs; operate websites and registries; run user-enabled reminders, notifications, and sync; manage subscriptions; provide support; detect misuse; troubleshoot performance; and meet legal obligations.

We also use service activity and referral information to understand acquisition, attribution, product performance, and relevant partner referrals. Optional marketing preferences are separate from the service messages necessary to operate your account. We do not use connected Google data for advertising.

Connecting Google is optional. The permission screen identifies the scopes requested. Identity information identifies the connected account. Gmail access supports reading relevant inbox and sent conversations, associating replies with planning records, showing thread content, and sending messages you authorize. Contacts access supports the contact-import feature and the contacts you select.

To identify relevant conversations, Juno may process message information against saved planning contacts, linked threads, domains, and wedding-related signals. The Gmail thread store retains limited conversation identifiers, timestamps, reply status, and planning associations rather than persisted copies of Gmail message subjects, snippets, bodies, or participant lists. Message content can be fetched to display a conversation. If you copy information into a note, guest record, message draft, or other saved planning content, that saved record is separate from the Gmail thread store. Classification can make mistakes; review linked conversations and sharing settings.

Juno’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use that information for the permitted user-facing features you choose. We do not sell Google user data, use it for advertising or creditworthiness decisions, or use Google Workspace API data to train generalized AI or machine-learning models.

Access or transfers of Google data are limited to what the Google policy permits, including providing or improving the relevant user-facing features, security, applicable law, and a qualifying business transfer with the required consent. Human access to Google data is restricted to your affirmative agreement to view specific data, necessary security purposes, compliance with applicable law, or permitted internal operations involving only aggregated and anonymized data. General support or service maintenance is not an unrestricted permission to read your mailbox.

You can disconnect the integration through its account controls or revoke Juno’s access in your Google Account permissions. Removing authorization stops future authorized access; it does not recall messages already sent or erase information separately saved by you, recipients, or collaborators. Contact us for help deleting retained Juno records.

If you connect Microsoft Outlook or another supported provider, Juno processes the permissions, account information, mailbox content, and status needed for the enabled workflows. Unlike the Gmail metadata-only thread store described above, the provider-neutral email service can retain encrypted message subjects, snippets, bodies, and synchronization cursors, together with message identifiers, participants, folders, and timestamps. Not every provider or feature is available to every account.

Access depends on your provider authorization and the workspace or planner permissions you grant. Disconnecting an integration and deleting an account are different actions. You may also need to revoke access at the provider. Provider-side copies, delivered messages, and information independently saved by others are governed by those parties. Never connect an account you are not authorized to use.

Inviting a partner, planner, staff member, or collaborator can give that person access to the relevant workspace and its planning information. Review the displayed role and permissions before sharing. An organizer may add information about guests or vendors who have never created a Juno account. Guests can contact the organizer or Juno about information relating to them.

Publishing a wedding website makes the selected story, photos, schedule, travel information, registry, and other visible content accessible through its public link. A link is not a password or a guarantee of privacy. People may forward it, copy content, or retain screenshots, and public content may be discovered or indexed. Avoid publishing access codes, private addresses, guest lists, or other sensitive information you do not intend to share.

Unpublishing or hiding content limits future access through Juno, subject to processing and cache delays. It cannot remove copies already retained by visitors, recipients, search engines, or third-party services. Editing a shared workspace or deleting your personal account does not necessarily delete an independently owned workspace or other people’s records.

When an AI feature is used, the prompts and relevant planning context required for that feature may be processed by an AI service provider. Juno uses Anthropic for certain assistant features. Context can include saved planning details, tasks, budgets, vendor information, or other material included in the particular feature. Avoid supplying information unrelated to the task or secrets such as passwords and payment credentials.

AI outputs may be inaccurate and should be reviewed before sending or relying on them. Google API data remains subject to the restrictions above, including the prohibition on training generalized models. This policy does not promise that every third-party provider retains no data; processing and retention depend on the applicable service and contractual terms.

At your direction: to invited workspace participants, guests, message recipients, venues, vendors, planners, or visitors to content you publish. Sending a message or submitting a form necessarily shares its contents with the recipient.

To service providers: hosting and infrastructure, database and storage, authentication, email and push delivery, payment processing, AI, diagnostics, security, and support providers as needed to operate the relevant services. Current integrations include Vercel, Supabase, Google, Microsoft, Resend, Anthropic, Stripe, and Apple, depending on the features used. Some providers also act independently for their own accounts, payment services, or legal obligations.

For operations and safety: authorized personnel may access information needed for support, troubleshooting, fraud prevention, security, or legal compliance, subject to applicable restrictions. The stricter Google-data access rules above continue to apply.

For legal matters or business changes: we may disclose information when required by law or reasonably necessary to protect rights and safety, address fraud, or establish or defend a claim. Information may be disclosed in a financing, reorganization, merger, acquisition, or asset transfer with appropriate protections. A transaction does not remove existing privacy obligations or Google Limited Use requirements.

Juno uses cookies and similar browser or app storage for sign-in, security, workspace selection, preferences, session continuity, and usage measurement. Referral identifiers and campaign parameters help attribute visits and conversions. Links to retailers or partners may carry attribution parameters; the destination may independently collect information under its own policy.

Browser settings let you remove or restrict cookies and site storage, although doing so can sign you out or affect features. Use available in-product privacy controls or contact us to request an opt-out of optional analytics. A browser’s Do Not Track signal does not by itself configure every Juno feature. Where applicable law requires recognition of a valid universal opt-out signal, those legal rights apply; contact us if your preference is not being honored.

If processing constitutes a sale, sharing for cross-context behavioral advertising, or targeted advertising under a law that applies to you and Juno, you may request the applicable opt-out. This statement does not reclassify a third-party provider’s practices or imply that every referral is a sale. Google user data is not sold or used for advertising.

We retain information for the purposes described here while it is needed to operate your account or shared workspace and, where necessary, for security, legal obligations, billing records, dispute resolution, and enforcement. Retention depends on the type of record, whether a workspace remains active, your choices, technical dependencies, and applicable requirements. We do not promise one universal deletion period for all data.

Use available account controls to edit information, export your data, disconnect a provider, or request account deletion. You can also email us. Account deletion removes or initiates removal of the account and associated data under the service’s deletion workflow; storage cleanup may require retries. Backups, legally required records, and narrowly necessary security or transaction records may remain until their retention purposes end. Retained information remains subject to applicable protections.

Disconnecting email prevents further integration access and removes the connection as supported by that integration. It is not the same as deleting every planning record derived from prior activity. Revocation at a provider may require separate action if a revocation request fails. Data held by another workspace owner or recipient may remain independently of your account. Uninstalling the iOS app alone does not delete your account or cancel an app-store subscription.

Email codymiller@wolfdig.com with the subject Privacy request and describe your request and relationship to the account or wedding. Do not send passwords, full payment-card details, or unnecessary identity documents. We may need proportionate information to verify identity, authority, and the affected records before disclosing or changing data. An authorized agent may contact us, subject to verification of authority.

Depending on your location and whether a law applies, you may have rights to access or know the categories and sources of information, correct it, receive a portable copy, delete it, restrict or object to certain processing, withdraw consent, or opt out of specified uses. California residents may have rights concerning sale or sharing and certain sensitive information; other US state laws may provide targeted-advertising opt-outs and appeal rights. These rights are subject to legal exceptions and do not necessarily apply to every record or service.

Where applicable, you may appeal a decision by replying to our response or emailing us with Privacy appeal. We will handle requests, extensions, reasons for a refusal, and appeals within the deadlines required by applicable law. We do not discriminate against people for exercising protected privacy rights. You may also complain to the regulator responsible for privacy in your location.

For individuals whose information is subject to EEA, UK, or similar requirements, applicable rights may include objection, restriction, consent withdrawal, and a complaint to a supervisory authority. Where those laws apply, processing bases may include providing the requested contractual service, legitimate interests such as security and administration where not overridden by your rights, legal obligations, or consent for the relevant optional processing. A consent withdrawal does not undo prior lawful processing.

Juno uses safeguards including encrypted transport, access controls, database permissions, encrypted integration tokens, and encryption for certain stored email content. No system is completely secure, and these measures do not guarantee prevention of every incident. Tell us promptly if you suspect unauthorized access. We address incident notifications as required by applicable law.

Juno is operated from the United States. Information may be processed in the United States and other countries where our providers operate, which may have different privacy laws. Where a legally required transfer mechanism or safeguard applies, it must be used; using Juno is not a waiver of those requirements.

Juno is not directed to children under 13 and does not offer accounts to them. Adults may include children in guest lists or seating and meal arrangements. That information is supplied by the responsible organizer, not an invitation for children to create accounts. Organizers should have appropriate authority, minimize details, and avoid publishing children’s information unnecessarily.

Meal, accessibility, religious, or health-related details can be sensitive. Provide only what is reasonably needed for planning and share it with appropriate people. If you believe a child supplied information directly without appropriate authorization, or sensitive information was added improperly, contact us so we can assess and address it.

Optional marketing choices can be changed through available account controls or the unsubscribe instructions in a marketing message. Service, security, billing, and requested planning communications are distinct from marketing. Device notification permissions can be changed in your device settings; this does not necessarily disable email or notifications within Juno.

We will post revisions here and update the effective date. For material changes, we will provide notice appropriate to the change and as required by law. If a change requires new consent, we will seek it before relying on that consent. Changes do not authorize retroactive uses that require additional permission.

Privacy, deletion, and security requests: Juno Labs LLC, codymiller@wolfdig.com. The Terms of Service explain the contractual conditions for using Juno.