Herbarium privacy policy
1 Operator and service scope
Herbarium's operator is Jingya. The service helps record yarn, knitting projects, colours, swatches, private patterns and a knitting calendar. For privacy and support, contact jingya.swiss@outlook.com.
The service is currently limited to existing invited adult testers; the App is not generally available.
2 Data and purposes
| Data category | Purpose |
|---|---|
| Sign-in email, account identifier, session state and necessary verification information | Deliver sign-in emails, verify identity, maintain sessions and separate account data |
| Verified linked +86 phone number, SMS code and send state | Attempt phone sign-in for a specific existing test account, verify identity and limit repeat sends. The phone entry does not create or automatically merge accounts and is not open to external testers. SMS delivery through the product entry has not passed acceptance |
| Yarn details, photographs, purchased and remaining quantities, and custom yarn entries | Maintain personal inventory and yarn information |
| Project names, notes, status, dates, photographs and yarn usage | Record plans, progress and completed-project usage history |
| Colour combinations, swatch measurements, photographs, source images and recolouring results | Maintain colour and gauge records and perform image recolouring |
| Imported PDFs, images, filenames, pattern notes, reading position, marks and counters | Read private patterns and restore reading progress |
| Calendar dates, text, linked projects or yarn, photographs and stickers | Display activity records and calendar markers |
| Language, measurement units, device text size and unfinished drafts | Retain preferences and recover unfinished input |
| Upload, deletion and retry states, task identifiers, timings, image dimensions and byte counts, and necessary error information | Troubleshoot problems and prevent duplicate saves, incorrect deletion and data loss from delayed or uncertain operations |
| Email address, description and attachments voluntarily sent to support | Respond to questions, investigate problems or handle privacy requests |
| Network request information produced when accessing pages or requesting services | Processed by the relevant providers to serve pages, transmit requests or protect their services. Exact fields, logs and retention differ by provider; see section 4 |
Images, PDFs and filenames may contain personal information you provide, as well as metadata within the files. Select only content you intend the relevant feature to process and have the right to use. Importing an original file does not automatically remove all location or other metadata.
3 Processing on your device and in the cloud
Some unsubmitted forms, selected-file copies, recovery state and text-size preferences are stored on the device running the browser or App. Local drafts are not automatically synchronised to another device. Language can follow the system or be set to Simplified Chinese or English. The choice involves local storage and a language-preference cookie; an explicit language choice may also sync to the existing account preference. It changes the App's own interface, not your notes, brand information or PDF content.
Pattern display, image recolouring, calendar-sticker cutout and manual edge editing run on the device. Cutout uses model and runtime files downloaded from the current entry point and does not call a remote image-inference API. Saving a cloud record is a separate step that uploads relevant content or files. Reading or exporting a private pattern may download its original cloud file.
Saved business records and private files are primarily served by Supabase database and file storage; Supabase Auth handles sign-in. Cloudflare serves the invited App entry, while a separate platform-restricted web entry uses OpenAI Sites. The App gate asks Supabase to verify an issued access token and uses a short-lived secure cookie containing an account identifier. The browser or App also stores session information to restore sign-in. Normally closing the App does not sign you out or clear drafts. Account-based access is not end-to-end encryption and does not mean the operator or providers cannot process data when providing the service.
Supabase generates and verifies sign-in codes. +86 phone sign-in is restricted to a specific existing test account with a verified linked number. It neither creates nor automatically merges accounts and is not available to external testers; Alibaba Cloud Phone Number Verification Service attempts delivery. SMS delivery through the product entry has not passed acceptance, and an on-screen countdown is not proof of delivery. The identity-verification method for deleting a phone account has not been verified; please contact support about such a request. See the support page for code-entry guidance.
Historical project-configuration records place the Supabase project in a Singapore region. This is not a guarantee that every service, network request, log or internal copy is processed only there. Provider roles and known location limits are described below.
4 Third-party services
| Service | Purpose, relevant data and known limits |
|---|---|
| Supabase | Provides authentication, database, private file storage and backend functions; processes sign-in information, a linked phone number, account data, saved content and operation state. Historical project configuration shows a Singapore region, not that all processing occurs there. |
| Resend | Delivers sign-in emails through the existing mail configuration, receiving recipient addresses, message content and delivery information. A controlled deletion-notice integration does not establish completed cloud deletion or inbox receipt. See its US storage and retention information below. |
| Alibaba Cloud Phone Number Verification Service, SMS verification | Attempts code delivery for restricted +86 sign-in, processing the phone number, code and delivery information needed to send. A timed-out call does not prove non-acceptance or non-delivery; log and internal-copy periods and actual processing locations remain unverified. |
| Cloudflare | Serves App pages, program resources and the access gate, processing network requests and gate information. Business files are primarily stored with Supabase; this does not mean every image passes through the page server. Specific log/copy periods and locations remain unconfirmed. |
| OpenAI Sites | Hosts another platform-restricted web entry, with a platform identity separate from the Herbarium account. Sites does not provide the stated data or inference residency; this does not mean Herbarium uses all platform storage or AI capabilities. |
| Consumer Outlook.com and mail delivery services | Receive and transmit the address, description and attachments you send to support. Specific storage location and internal-copy/log periods for this consumer mailbox remain unconfirmed. |
| Apple device features | Provide camera, photo and file selection, page execution and file previews. Copies exported to Photos, Files or another destination are managed there. |
| Google Fonts Web API | Delivers some App interface fonts. Existing styles request its stylesheet and may fetch font files. The font request URL contains no sign-in email, account identifier, code or user-entered text; actual accompanying network fields have not been measured one by one. |
Resend's guidance places customer data such as email content and delivery records in the United States. It states that active Free, Pro and Scale accounts retain emails and logs for 30 days; backups have a separate seven-day rule, so adding the periods together would not establish an all-copy erasure deadline. Resend also discloses limited trust-and-safety sampling of emails on RunPod infrastructure it operates; this does not establish that any particular Herbarium email was sampled. Its subprocessor list and data-processing information are available.
Microsoft's Outlook.com guidance says messages removed from Deleted Items can still be recovered for 30 days. This is a rule for user-recoverable items, not an internal-copy or log erasure deadline. The consumer mailbox's specific storage location and those periods remain unconfirmed; enterprise assurances are not assumed.
Sites documentation does not offer the stated data or inference residency, so the restricted Sites entry cannot be described as Singapore-only. Platform support for storage and AI features does not mean Herbarium uses all of them; specific log and internal-copy periods remain unconfirmed. Cloudflare's self-serve terms and data-processing addendum are available, but do not establish a fixed all-copy deadline following deletion of an individual App account.
Google Fonts guidance describes request information that may include IP, requested URL and browser headers. This is provider-wide guidance, not a field-by-field observation of Herbarium's phone traffic. Existing App styles still request the service; not all fonts are self-hosted. This policy page itself does not load fonts. Specific font-service log/copy periods and locations remain unverified and cannot inherit another service's periods. Google's general retention information is not a Fonts-specific schedule.
Open-source PDF-reading and on-device cutout components are software dependencies; using them alone does not mean their authors receive your files. Other providers' request logs, internal copies and processing locations must be considered separately. Deleting content from the App interface does not prove that every provider copy is immediately erased.
5 Permissions and access
The camera is used when you initiate capture. Photos and files can be imported through the system's selection controls; exports go to the destination you choose. Choosing one file does not mean every selection requires access to the whole photo library or file directory. You can adjust applicable camera or photo permissions in system settings. Refusal may prevent the corresponding action, but does not delete previously saved data.
Private business records are restricted by account. Public yarn information, licensed reference material and policy pages are separate from private records. Treat temporary private-file links as access credentials and do not forward them. Link expiry is not file deletion.
6 Retention, deletion and recovery
Data categories have different retention and deletion methods. Where no consistent deadline or complete cleanup has been implemented, the table says so. Provider copies are also distinguished in section 4.
| Data category | Current period or end condition | Deletion method and limits |
|---|---|---|
| Saved cloud records and files | No uniform automatic expiry has been established for all records. Saved content supports recording, synchronisation and reading until relevant deletion is verified. | Available per-record features can initiate deletion. Submission or disappearance from a list does not prove cloud-file cleanup. Shared references, inflight uploads and uncertain files need separate checks. The complete account-deletion flow remains unverified. |
| Some local forms and pattern-import drafts | Some drafts have a 24-hour threshold after writing, checked only on later access to draft storage. Uncertain or partly successful uploads may remain for reconciliation. | Explicitly discarding the current pattern-import draft removes that local file copy and input, not a cloud record or an original in Photos or Files. This is not timed erasure of all local content. |
| Recolouring/calendar drafts and local late-write guards | Recolouring and calendar drafts have no uniform automatic expiry; their own save/cancel actions apply. The content-free identifier and time retained after discarding a pattern draft currently have no automatic expiry rule. | Cancelling one action does not clear other drafts. The late-write guard prevents an old operation from restoring input and cannot be removed without establishing safe conditions. |
| Sessions, language and other preferences, operation states | Used to restore sign-in or preferences and reconcile upload/deletion results; the draft threshold does not apply uniformly. | Sign-out, preference changes and business-record deletion are separate. Closing the App does not automatically clear sessions or drafts, and uncertain tasks should not be silently discarded. |
| Controlled SMS send reservations | The operator-controlled reservation records store request digests, counts and times, not raw phone-number input or verification codes. Their expiry cleanup has not been fully verified. | This statement applies only to the operator-controlled reservations; it does not mean the authentication or SMS provider does not process phone numbers or codes. A digest is not automatically anonymous. Reservations and provider delivery logs or copies are handled separately. |
| Deletion requests, notices and completion receipts | An unresolved request is not a completion receipt. Pending, inflight or uncertain notices can retain the recipient address and, after a send attempt begins, the message body; no separate automatic expiry cleanup is implemented for these states. Production cleanup of completed receipts is not fully implemented either. | The address and body should be cleared after confirmed provider acceptance, but production cleanup and reconciliation of uncertain results have not been fully verified. The deletion outcome needs its own check; whether a completion notice was sent, accepted by the provider, delivered and received by you are separate checks. |
| Cloud write-prevention markers | Related account and request identifiers are retained to stop old sessions or inflight work from writing back to an accepted deletion account. Their final period or safe exit condition remains undetermined. | These markers are separate from completion receipts and the backup recovery ledger. They prevent old sessions or inflight tasks from writing data back and may still be linked to your account. Their final retention period and safe cleanup conditions have not been set. |
| Support email and operator-controlled copies | Used for replies, follow-up and actual disputes. No uniform expiry cleanup has been implemented across inbox, sent, archive, attachments and exports. | A specific request can be checked and handled, but clearing operator mail does not establish erasure of Microsoft recoverable items, internal copies or logs. |
| Encrypted manual backup and independent deletion-recovery ledger | Two limited encrypted manual captures have been completed; only the earlier one has passed limited offline restore verification. One separate encrypted snapshot of accepted-deletion-request metadata was also saved. The earlier backup and that ledger use the earlier original data-capture time, while the newer backup uses its own original capture time, for their respective 28-day restoration cutoffs. Copying, saving a separate ledger, retrying or restoring does not restart the clock. Automatic backup and physical expiry cleanup are not in place. | Any future restore still needs fresh independent deletion-state evidence and must stop without it. The old snapshot is not continuous recovery protection. Denying restore after expiry is not physical disposal, and the one-copy result is not a universal backup policy already executed. |
| Provider logs, internal copies and copies at other destinations | Periods and locations vary by provider or destination; some remain unconfirmed. | Originals, exports, offline-device content and other-destination copies are not automatically removed with one cloud record. App list state cannot prove provider-copy cleanup. |
Account deletion is not a single step: submitting a request or removing a list entry does not mean the data is gone. The full cloud deletion flow has not been verified. We confirm the deletion outcome only after checking how the relevant cloud files, business records, inflight operations and login identity were handled. Sending and delivery of a completion notice are checked separately; provider acceptance does not mean you received it. A failed or uncertain notice does not undo a verified data-deletion outcome, but the notice still needs follow-up and is not blindly resent. Sending or accepting a notice cannot replace verification of data deletion.
The earlier encrypted manual backup and its limited offline recovery cover only captured business-data fields and committed files, not the full database, identity service or disaster recovery. A second limited encrypted capture was completed on 16 October 2026, but isolated restore acceptance has not been run for it. Frozen-account material remains isolated rather than restored as a usable account. A separate encrypted snapshot of accepted-deletion-request metadata is not continuous protection. Any future restore needs fresh deletion-state evidence so old sessions, uploads and tasks cannot recreate deleted material. A restoration cutoff is not physical disposal at expiry or erasure of every copy.
We retain the time a privacy request was first received to check applicable deadlines; retries or provider waits do not restart it. An exception explanation, a pending reply or clearing a local draft does not constitute completed cloud deletion. Offline-device content, local originals and exports must be managed at their respective destinations.
7 Your choices and contact
Use available features to view, change or delete relevant records and adjust system permissions. Contact Jingya at jingya.swiss@outlook.com to request access, correction, a copy, deletion or account deletion. For personal-information processing based on consent, you can request withdrawal of consent through that email address and learn which features may be affected. Sending an email does not automatically delete all data immediately.
Account-related requests require appropriate account-holder verification. Never send passwords, sign-in codes, access tokens, private file links or unnecessary identity documents. There is no self-service account-deletion entry and the full cloud deletion flow has not passed acceptance. We retain the original request-receipt time and assess applicable deadlines; retries or provider waits do not restart that time. You can ask for progress through the same email address.
8 Policy updates
We will update this policy when data purposes, providers, processing locations or deletion practices materially change, and notify affected users where required. Publishing this invited-testing policy does not itself complete formal-store or regional release requirements.