Privacy Policy
Only Fine Charms
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Only Fine Charms stores your jewelry designs, component positions and connections, finishes, variants, set proportions, creative-brief progress, workshop name and preferences in a SQLite file on your iPhone. No account, email address, password or social sign-in is requested. Synchronization is optional and off by default. When enabled, the app sends saved designs, modification timestamps, deletion markers and completed brief identifiers to our backend. The workshop name, language, mass units and motion preference remain local. The backend issues a random installation secret, stored in this iPhone's Keychain; it stores a SHA-256 hash to authorize access to that installation's records. The service and Railway infrastructure receive network requests, which include an IP address and technical connection information. Opening this website also sends a request to Railway. The app does not include advertising or analytics SDKs and does not access location, contacts, camera, microphone or your existing photo library.
How we use information
Local data lets you build, reopen, compare and export virtual jewelry and remember your preferences. Optional server storage synchronizes the collection and creative-brief completion for the same installation key and resolves changes by modification time. The installation secret provides private authorization without an account. Network metadata is processed to route requests, operate the service and enforce request limits. Photo-addition permission is used only when you ask to save a PNG or animated GIF. Export files are created temporarily on your iPhone and can be shared using Apple's system share sheet.
Service providers and sharing
The backend is hosted by Railway, which processes stored data and technical requests as our infrastructure provider. Network infrastructure may handle IP addresses, request paths, timestamps, status information and operational logs. Our application server does not write request addresses, authorization secrets or design contents to application request logs. We do not sell your data or send it to advertising, marketing or analytics providers. Apple handles Keychain, system photo-library operations and any device backup you enable. When you use the share sheet, the recipient or app you choose receives the exported file under its own privacy practices. The public policy page uses no cookies, login or third-party scripts.
Data retention
Local designs and preferences remain until you delete them or remove the app, subject to iOS backup and restoration behavior. Keychain storage can persist separately from app files; the app's Delete all data action clears its installation key after server deletion is acknowledged. Synchronized records remain on the Railway persistent volume until deleted. A deleted design is replaced on the server by a minimal identifier, timestamp and deletion flag, with its title, parts and other design content removed, so an older offline copy does not reappear. These minimal markers remain until all installation data is deleted. No fixed lifetime is promised for Railway infrastructure logs or provider-managed backups. Backup copies, if any, may persist according to the provider's or your device backup lifecycle and are not necessarily erased immediately with live records. Temporary exports may remain in iOS temporary storage until the app or operating system clears it; copies saved to Photos or shared elsewhere are separate.
Deleting your information
You can delete a saved design from Collection after confirmation. The local visible record is removed and a deletion marker is queued for synchronization if enabled. Delete all data in Settings removes local workshop data and requests deletion of the installation, its collection, deletion markers and brief progress from the live server database, revoking its secret. If offline, the secret is retained only to retry that deletion and a pending message is shown; deletion retries when connectivity returns or the app is active. Local-only data is not uploaded merely to delete it. Turning synchronization off stops future collection transfers but does not by itself delete an existing server copy. Removing the app or losing its installation key can leave a server copy inaccessible; there is no login-based recovery or alternate-device sign-in. You can remove exported images in Photos and manage copies or backups through the services where you saved them.
Permissions and your choices
The only requested permission is add-only access to Photos, requested when you choose Save PNG or Save GIF. This allows adding the exported file and does not provide access to browse your existing photos. You can refuse or withdraw permission in iPhone Settings and continue building and saving locally; the system share sheet remains available for exports. The app does not request geographic location or tracking permission. Disabling synchronization in the app stops optional transfers, while Delete all data removes the existing synchronized installation as described above.
Your privacy rights
You can inspect and edit your designs in the app, export your workshop data as JSON, delete individual designs, and delete all workshop data. You may have additional rights under applicable law, including access, correction, erasure, restriction or objection. For privacy questions or to exercise applicable rights, contact OttolineFothergill@icloud.com. This address is a public privacy contact only; the app has no message-sending or support-ticket feature. Because there are no accounts and we do not request an identifying email address, we may be unable to associate a request with an installation after its secret has been lost. Never send your installation secret by email.
Security
The deployed app communicates with the service over HTTPS. Each synchronized installation receives a cryptographically random 256-bit secret; the iPhone stores it using device-only Keychain protection and the server stores its hash. Every private collection, progress and deletion request checks authorization and scopes database operations to that installation. Public home, privacy and health pages do not expose collection data. The service validates bounded JSON, limits requests, and stores data on a persistent Railway volume. SQLite transactions protect writes; deletion clears live records and attempts to checkpoint the write-ahead log. No security system can guarantee absolute protection, and device or hosting backups have their own protection and retention behavior.
Children’s privacy
Only Fine Charms is a creative jewelry-design utility intended for an adult audience, particularly ages 18 to 35. It is not directed to children and has no account registration or age-profile collection. If you believe a child's personal information has been submitted, contact OttolineFothergill@icloud.com so we can assess the request in light of the installation-based data model.
Changes to this policy
We may update this policy when the app's features, processing or hosting practices change. The effective date above identifies this version. The current public policy is accessible from Settings in the app and at this website's privacy path. Material changes will be reflected in the policy and, when appropriate, in the app before new processing is introduced.