Privacy and data use
Contact BJURNY at info@bjurny.com about access, correction, export or deletion of your information. The published BJURNY user agreement provides additional information.
Accounts and private records
Account information supports sign-in and your profile. Personal plant lists, private records and unpublished contributions are restricted to authorized users. Organization membership controls workspace access. Publishing a collection or contribution makes its approved public fields and public images visible to visitors.
Visitor photographs
Signed-in visitors can submit photos of published collection plants. The original and processed images remain private while processing and review are pending. We record the photographer name, requested attribution, permission for garden display and a separate choice about global plant profile use. A garden reviewer decides whether a photo appears on its collection profile; BJURNY separately reviews any global use. Approved photos display the supplied attribution. The contributor can withdraw a photo in the app; new image requests stop immediately. An image already displayed in a browser may remain visible until that page is closed. Rejected and withdrawn media are queued for deletion, and abandoned submissions expire.
Public journey counts
BJURNY counts searches, QR landings, onboarding visits and approved photo contributions in daily totals without storing search text, visitor identifiers or cookies in those counters. Seller referral and billing records remain separate.
Seller referrals
Outbound seller links may generate a charge to the seller. BJURNY records referral context and uses pseudonymous identifiers to limit repeated events. Signed-in referral events may be associated with an account. Referral income does not determine botanical content or search ranking.
Catalogue generation
Seller onboarding can send bounded, sanitized samples of public product pages to OpenAI to propose a catalogue configuration. BJURNY requests that generated responses are not stored as API application state. Routine offer refreshes use the tested configuration and do not call the model.
Payments
When support payments are enabled, checkout and billing management use Stripe. Payment and subscription identifiers, amounts and status are used to reconcile payments. Card numbers are entered with Stripe, not in BJURNY forms. Seller billing records also include accepted terms and the supplied business contact details.
Public images and hosting
BJURNY uses Supabase for account and application data, Cloudflare for application/media delivery and seller processing, and Vercel for the public website. Organization logos and cover images can be served by the organization's own website; that website receives an image request from your browser.
Your choices
Review visibility before publishing. Withdraw public content through the applicable workspace controls. Use Delete my account on the Account screen to delete a personal account or register a deletion request where shared, financial or media records need review. Contact info@bjurny.com for export requests. Some accounting and audit records may need to be retained after an account request; we will explain what applies to your request.