Plumly Privacy Policy
Version: September 28, 2026. Effective when published at plumly.app/privacy, subject to any advance notice or consent required by law.
1. Who we are
Cedarline Technologies LLC, a company registered in Florida, United States, operates Plumly. This policy covers the Plumly app, plumly.app, public profiles and guides, invitations and RSVP features, and support interactions. It applies to account holders, guests, creators, invitation respondents, and website visitors.
Contact us at contact@plumly.app, or write to Cedarline Technologies LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702, United States.
2. Guest use, accounts, and profiles
You can use core local features without an account. Guest use does not mean every feature is offline: importing links, interpreting content, opening shared pages, and other connected features can involve remote processing.
When you sign in with Apple, we process your account identifier, Apple authentication identifiers, session information, and the name and email Apple supplies. Your email may be an Apple private relay address. We do not receive your Apple Account password.
You can provide profile information such as a name, photo, handle, and biography. Profile information is used to display and manage your identity in Plumly and, when associated with public creator features, to identify you to viewers. Review your creator profile before sharing or publishing. Do not use a public profile for information you intend to keep private.
3. Information you save and create
Plumly handles the text, images, screenshots, URLs, notes, dates, locations, plans, reminders, and guide contents you supply or import. It also processes extracted or suggested details, such as titles, categories, event times, and venue addresses, and the relationships between saved items.
We use this information to provide the capture, organization, interpretation, planning, and sharing features you request. Information can come from you, permissions you enable, external sources you import, or other people whose content you view or save. Captures can contain personal information about you or others; avoid including unnecessary sensitive information.
Your personal library is stored on your device. Account, publishing, remote interpretation, and backup features can separately process information on our backend. Device storage can also include preferences, profile state, image caches, temporary capture files, and data shared with Plumly's share extension.
4. Automated interpretation
Plumly uses local processing and remote interpretation to classify content and suggest useful details. For remote classification, Plumly sends relevant images and extracted or supplied text through its Supabase backend to Anthropic's Claude API. Text can include pasted-link context or dictated text. The content itself may identify people, even without a separate account identifier.
We use the results to provide the requested features. Results may be inaccurate; you can review and edit them. Optional library backup is separate from remote interpretation, so not making a backup does not prevent interpretation requests from leaving your device.
Plumly does not use your content to train AI models. Our Terms do not grant permission to use it for model training. Provider processing and retention are governed by the applicable commercial arrangements; this policy does not promise that remote processing has zero retention. Anthropic describes its commercial practices in its Privacy Center.
Do not submit content for remote interpretation if you do not want it processed for that purpose. Contact us about processing choices or deletion of information already submitted. Accepting our Terms does not replace any separate permission required by applicable law.
5. Library backups
Library backup and restore are manual actions you initiate. Plumly does not automatically synchronize your personal library.
A library backup can include each item's identifier, category, title, subtitle, notes, source link, image URL, and relevant place address, city, coordinates, or event start time. Records are associated with your account and include update information. Supabase provides the backend storage used for these records.
Not making another backup does not delete a backup previously created. Deleting the app is also different from deleting server records. Use account deletion or contact us about removing information held on our backend. Copies stored through your device's own backup services are governed separately by those services.
6. Guides, public profiles, and sharing
Saving an item is different from publishing a guide. Guide visibility has these meanings:
| Visibility | What it means |
|---|---|
| Draft | Not published for public discovery. Draft does not necessarily mean device-only storage. |
| Public | Available for public viewing and discovery, including public guide and creator listings. |
| Unlisted | Accessible through its link. The link can be forwarded; unlisted is not password protection or sharing restricted to approved recipients. |
Published guides display their contents and associated creator information. Public creator information can include the name, photo, handle, and biography you provide. Do not publish private addresses, personal plans, or another person's information unless you have an appropriate basis to share it.
People can save supported guide contents into their own Plumly, copy or screenshot content, and forward accessible links. Editing, unpublishing, or deleting an original does not necessarily remove independent copies. External services may cache or index public material. Contact us about removal if the available controls do not address your request. Copies hosted within Plumly remain subject to applicable privacy obligations.
When you share to Messages, email, a calendar, or another service, the selected information is provided to that destination. That service controls its own delivery and retention. Opening a share sheet does not establish that a message was delivered.
7. Invitations and RSVPs
Supported invitation features allow responses without signing in. Responses can include a name, response status, guest count, note, invitation identifier, device identifier, and submission time. A response without an account can still contain personal information.
The invitation owner's authenticated roster includes respondents' names, statuses, guest counts, notes, and submission times, together with aggregate counts. The roster service restricts this access to the invitation owner. Organizers may separately retain or share information they receive; provide only the information needed for your response.
A device identifier can associate a response with a previous response from the same device to the same invitation. It is not an advertising identifier. Unsigned responses are not reliably associated with a Plumly account, so deleting an account does not automatically identify every unsigned response submitted by that person.
To request correction or deletion of an unsigned response, email us with the invitation link or identifier and enough context to locate the response. We may need additional verification to avoid changing another person's response. Do not send passwords or unrelated sensitive information. Changing an RSVP status is not necessarily deletion of the response record.
8. Permissions and connected features
You control device permissions through iOS settings. Available permissions depend on the feature and app version.
- Photos and camera: selecting or capturing images, importing screenshots, and adding profile photos.
- Microphone and speech recognition: supported voice capture and transcription. Dictated text can be processed as described in section 4.
- Calendars: supported calendar import and export can require calendar access, including full access where requested. Exported calendar entries may remain in the calendar service after a Plumly item or account is deleted.
- Notifications: local reminders are scheduled on the device. Remote notification features use an Apple push token stored on our backend for supported event and RSVP alerts.
- Location: enabled nearby-place and proximity features use location access. Depending on your permission settings, iOS can provide precise location and allow background access. Location-related information can also appear in saved venue details, event lookup requests, and library backups; this policy does not describe all location-related data as device-only or anonymous.
- Contacts: supported contact-selection features use the access you grant.
- Music: supported music features use artist information from Apple Music and Shazam. Recent artist observations from the system music player are stored locally in a list capped at 50 entries and approximately two weeks. Artist names and a city can be sent to Ticketmaster or SeatGeek to look up events. We do not sell this information or share it for advertising.
Withholding permission can limit the corresponding feature. Revoking permission does not itself erase information already saved, transmitted, or exported. Contact us about those records separately.
9. Providers and other disclosures
The services used to provide Plumly include:
| Provider | Role |
|---|---|
| Apple | Sign in with Apple and supported platform services, permissions, maps, speech, music, and notifications. |
| Supabase | Authentication, backend database, object storage, and server functions. |
| Anthropic | Remote interpretation of relevant image and text content. |
| Cloudflare | Website hosting and delivery. |
| Ticketmaster and SeatGeek | Event searches using relevant search information, such as artist names and city. |
External websites receive requests when you import or open their content. What they receive depends on whether the request originates from your device or our servers. Network services process connection information needed to handle requests, and may maintain operational or security records under their applicable practices. This policy does not promise the absence of infrastructure logs.
We also disclose information when you direct us to share it, when legally required, or when legally permitted and reasonably necessary to protect people, investigate abuse, or establish, exercise, or defend legal rights. A lawful business transfer remains subject to applicable law and the privacy commitments made when information was collected.
10. Advertising and tracking
We do not sell or rent personal information, show advertisements, or track people across other apps and websites for advertising. Plumly does not include third-party advertising, attribution, or analytics SDKs. Providing requested information to service providers is distinct from selling it or using it for advertising.
Plumly's static website pages do not use advertising or analytics scripts. Hosting and security services can still process requests. Device settings, consent records, and identifiers used to associate an RSVP serve functional purposes; they are not a permission to use information for cross-site advertising.
11. Retention and deletion
Different records have different purposes and deletion paths. We keep personal information for the service purpose for which it is handled and any applicable legal obligations. The criteria include whether your account or content remains active, whether the information is needed to provide a requested feature or resolve a request, and whether retention is necessary for a legal obligation or claim.
| Record | Treatment |
|---|---|
| Local library and settings | Stored on your device until removed through the relevant controls or cleanup process. Device backups and other devices require separate consideration. |
| Account, profile, cloud content, guides, and owned uploads | Subject to the relevant content controls and account-deletion process. Unpublishing and deleting are different actions. |
| Library backups | Stored separately from local content; not making further backups does not remove an existing backup. Account deletion removes account-associated active backend records. |
| Unsigned RSVPs | Managed as invitation responses rather than reliably account-linked records. Request removal using the route in section 7; do not assume account deletion or the event date automatically deletes them. |
| Remote processing and infrastructure records | Subject to the provider's applicable processing, backup, security, and legal-retention arrangements. Deletion from an active service does not guarantee simultaneous physical erasure from every provider backup. |
| Support and privacy requests | Retained while reasonably necessary to resolve the request and afterward only for applicable legal obligations or legal claims; deleted or de-identified when those purposes no longer require identifiable records. |
| Deletion recovery receipts | Retained indefinitely for the recovery purpose described below. |
Account deletion. Use Delete account in Plumly's account settings, or contact us if you cannot access your account. Our deletion process removes account-associated active backend records and owned uploaded files and clears account-specific content and identity information on the device performing cleanup. If cleanup cannot finish, the app provides a retry or recovery flow. Uninstalling the app alone does not request server-side account deletion.
Deletion recovery receipts. After account deletion, we retain the deleted account's identifier, a one-way hash of a device-generated recovery code, and the completion timestamp. The identifier is account-linked, not anonymous. The receipt contains no saved content or profile information. It is retained indefinitely only so a device that lost the deletion response can verify that deletion completed, and is not used for marketing or tracking.
Account deletion does not automatically retrieve independent recipient copies, delete external messages or calendar entries, erase every offline device or external backup, or identify every unsigned RSVP. These limits do not remove our obligation to respond to a valid request under applicable law. Where limited records must be preserved for a legal obligation or claim, retention is restricted to that purpose.
12. Your choices and rights
You can use supported controls to edit or remove content and profile information, manage device permissions, choose whether to make a library backup, and request account deletion.
Email contact@plumly.app to request access, correction, deletion, or an available copy of information we hold. Information stored only on your device may not be accessible to us remotely. We may request proportionate verification to protect your information and other people's information.
Depending on applicable law, you may also have rights to object to or restrict processing, withdraw consent, request portability, use an authorized agent, appeal a decision, or complain to a privacy regulator. We will respond within applicable legal time limits and explain any applicable exception. We will not unlawfully discriminate against you for exercising privacy rights. Withdrawing consent does not affect the lawfulness of processing before withdrawal.
13. Age, security, and international use
Plumly is intended for people aged 13 or older, subject to higher local minimum ages and parental-permission requirements. If you believe a child below the applicable minimum has provided personal information, contact us so we can investigate and take appropriate action.
Plumly is operated from the United States and is available internationally. Service-provider processing can occur outside your location. Local mandatory privacy and consumer rights continue to apply; worldwide availability does not waive them. Contact us for information about processing relevant to your request.
No electronic service can guarantee absolute security. Protect access to your device and account, and avoid publishing information you wish to keep private.
14. Changes and contact
We will post revised policies and identify their version. Material changes will be accompanied by appropriate notice and any consent required by law. A revised policy does not retroactively authorize uses inconsistent with commitments made when information was collected.
Contact: contact@plumly.app.
Cedarline Technologies LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702, United States.