Spud Bud (“the app”) is developed by Neil Anderson (“we”, “us”). This policy explains what the app stores on your device, what it sends when you ask it to share, and how hosted share links work. The short version: your buds stay local by default, and Spud Bud sends content off your device only when you explicitly choose “Share a link”.
What Spud Bud handles
Spud Bud has no accounts, login, or sender identity. It does not use analytics, advertising, tracking SDKs, crash reporting, or AI services. It does not request access to your contacts, camera, or location, and it does not send notifications.
- Buds and sign text are stored locally by default.
- The app has no user account, login, or sign-up process.
- The app does not use your content for tracking, advertising, analytics, personalization, or AI services.
Data stored on your device
Your collection, buds, sign text, and selected appearance settings are stored locally on your device (in an app storage container shared between the app and its widget). This local data does not leave your device unless you use one of the sharing options below or it is included in Apple's standard device backups (iCloud or local), which are governed by Apple's privacy policy.
Deleting the app deletes this data.
When you choose a share action
Spud Bud creates a generated image from the selected bud. The app only sends or saves that image according to the action you choose:
- Share bud: Spud Bud hands the generated image to the iOS system share sheet. Spud Bud does not upload or retain the image. The service or app you choose from the share sheet may handle it under its own privacy policy.
- Save image: Spud Bud writes the generated image to Photos using add-only Photos permission. The app does not read your existing photo library.
- Share a link: Spud Bud uploads only the selected bud's validated payload and a generated JPEG to share.corduroying.com. The payload contains the sign text and selected bud appearance settings, such as vegetable style, yarn color, background, and font. It does not upload your collection, subscription state, device details, or sender identity.
Hosted share links
Hosted links are anonymous, public-by-link links. They are not private or access-controlled: anyone with the link can view the selected bud. Links are not listed on a public search page and are marked noindex, but that does not make them private. Only share a link if you are comfortable with anyone who receives it being able to view the bud and its sign.
Hosted share records are intended to expire after 90 days. The hosted service stores a manifest and generated image in Google Cloud infrastructure. Because it runs on Google Cloud, the service may also process standard request metadata such as an IP address, user-agent, timestamps, and request details in Cloud Run or Cloud Logging request logs. Retention of that technical metadata is separate from the 90-day share-record expiry and follows the service's configured Google Cloud logging settings. Spud Bud does not use this metadata for tracking or advertising.
For App Store privacy purposes, the sign text and bud information sent when you choose “Share a link” are Other User Content used for App Functionality—creating and displaying the hosted share link. Spud Bud does not use this content for tracking.
Purchases
Subscriptions are processed entirely by Apple through the App Store. We never see or store your payment details. Apple provides us no personally identifying information about subscribers. See Apple's privacy policy for how Apple handles purchase data.
Children's privacy
Spud Bud does not ask for names, email addresses, or other identity information, and its normal bud and sign data stays on the device. A user-created sign can be sent off the device only when the user explicitly chooses “Share a link”; in that case, the selected bud payload and generated image are handled as described above. Parents and guardians should remind children not to put personal information in a public-by-link sign.
Changes to this policy
Hosted sharing is a material app feature, so we will update this policy if the sharing flow, hosted-link visibility, storage, or technical-data handling changes. The updated version will be posted at this page with a revised effective date.
Contact
Questions about this policy: nano@corduroying.com