A little clarity.
Then, carry on.

Plantoat is in internal alpha and is not yet available from the App Store or Google Play. You can join the private-beta list from the Coming soon page; we’ll use that email only for beta invitations and meaningful release updates.

The project is configured for iOS and Android, with iPad support enabled. Minimum operating-system versions and public device compatibility are not yet published here. The configured app version is 1.1.4; this is not a claim of store availability.

Use your account email and password. Complete email confirmation when prompted. If you have forgotten your password, use the password-reset option. Initial sign-in and account-security changes require a connection. Never send your password in a support enquiry.

Internal alpha builds are distributed to a small testing group. Compatible JavaScript and asset changes can arrive through app updates; native changes require a new app build. Public enrollment and release timing are not finalized.

Available local planning data can be used offline. Returning access depends on a previously verified identity matching the data on the device, verified within the last 30 days, and a retryable connection error. This is not a guarantee of offline entry in every situation. Invitations, remote vow sharing, account security and cloud sync need a connection. Media must already be available on the device.

Authorized wedding data syncs through cloud services when you have a valid signed-in session and a connection. Local edits and media transfers may remain pending. Check that uploads have finished before switching devices or removing the app. Sync is not a promise that every device is always up to date.

Let pending edits and media transfers finish while connected. Do not clear app data or reinstall to resolve a sync issue while work is still pending locally. Alpha behavior may change; review the instructions accompanying your test build. No migration or data-retention guarantee is announced on this website.

Invitations require an online, signed-in session and permission to manage collaborators. Choose a role and, for an editor or viewer, the appropriate full or custom scope. Superusers can manage editors and viewers; only the owner manages superusers. Review access before inviting someone.

The owner controls the wedding lifecycle and ownership. A superuser has broad access to non-vow information and can manage editors and viewers. A full editor can edit non-vow planning information without collaborator administration. A full viewer can read it. Editors and viewers can instead have custom access. No wedding role automatically grants access to another person’s private vows.

Implemented custom scopes cover Shot List, Setlist and Cheat Sheet; selected timelines have separate schedule, run, comment and media permissions. Style Plan access can be limited to specific people. Budget, checklist, guests, seating, check-in, vendors and vendor readiness currently require full scope. A Cheat Sheet grant includes the whole board: safe and team labels describe outbound sharing, not per-card access.

The server rejects access that is no longer authorized. The app removes protected local rows and associated caches when it receives and processes the access change. An offline device cannot be remotely cleared immediately. An offline edit may be rejected when it reconnects. Files already shared outside the app cannot be recalled through a permission change.

Manually saved drafts and revisions sync to an author-only vault. Wedding ownership and superuser access do not bypass that boundary. A local recovery buffer is separate from a saved draft. Explicit partner sharing creates a sealed snapshot; the recipient sees its content only after the server checks the recipient and reveal time. Deleting a wedding does not itself delete your author vault or existing partner share.

Selected-timeline schedule access alone does not grant comments or media access. Media contributors can upload and remove their own contributions; removing other contributors’ media needs full edit scope. Person-scoped Style Plan access covers that person’s looks, details, measurements, provider information and image metadata.

You can import a CSV, TSV or text file, or paste rows. Map the headers and review the proposed guests before confirming. Duplicate handling offers skip, merge or add. Device-contact import asks for permission and lets you choose contacts and contact details. An Excel workbook import is not described here; export it as CSV first.

Guest lists can be shared as CSV with selected columns. Timeline and event PDFs, and saved-vow PDFs, use the device’s sharing or printing flow. Review private contact details before sharing. These files leave the app’s access controls once shared. These options are not a complete account-data export.

In Settings, open Account security and the Delete account section. A real online session, your current password and the exact confirmation DELETE are required. Resolve pending work first. Deletion removes your account and owned weddings, and account-authored private content. Operational records in weddings owned by others can remain without your actor identity. This action is permanent. Backup and log retention terms are not finalized on this website.

Start with the Contact page and choose account support, a bug report, feedback, planner enquiries, privacy or general contact. This prototype lets you review a draft only: a verified support inbox or submission endpoint is not connected. Do not enter passwords, vows, guest lists or other sensitive personal information.