Culet is made by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). Privacy questions: captainlongevity@gmail.com.
Is there a Culet server holding my designs and stones?
No. Everything you create — imported .ASC designs (with their original text preserved), adapted copies, cut sessions, logged stones, and stone photos — is stored in the app's local on-device database. There is no Culet backend to read it, restore it, or move it.
Does anything sync to iCloud or my Apple ID?
No. Culet declares no iCloud entitlement and uses no CloudKit; there is no remote sync. Your records may be included in your normal iPhone backup (iCloud Backup or Finder) when you have that enabled — that is Apple's standard backup behavior for on-device data, not a Culet feature. If you delete the app and have no such backup, the data is gone; there is no remote copy.
Device-backup contents and recovery depend on your system settings, a successfully completed usable backup and Apple’s restoration process; enabling backup alone does not guarantee recovery of every record or original file. We cannot retrieve or restore your device backups.
Do you collect analytics, crash logs, or an advertising identifier?
No analytics SDK, no crash reporter, and no advertising identifier. Culet cannot tell how often you open it, which designs you import, or whether you subscribed — except through Apple's ordinary aggregate sales reports.
Every calculation — the critical angle, the tangent-ratio conversion, the windowing grades, the carat estimates — runs on your iPhone with deterministic, rule-based math. The cited materials reference (refractive index, specific gravity, cleavage and heat warnings, recommended angles) is bundled data compiled from published gemological references, each record carrying its citations and a last-verified date, updated through ordinary App Store releases. None of it is sent anywhere.
Culet ships twelve in-house generic classic designs. Other designs come from .ASC files you choose to import; parsing and storage occur locally. The App does not automatically upload a design to the developer. Pro can generate a cutting-card PDF from a built-in, imported or adapted design and present it to the system Share Sheet. The PDF includes the displayed name, index-wheel schematic and tier angles and indices, rather than an export of the complete original .ASC text. A stone share card instead shows the stone's own information and photo, with its design name where recorded, and does not include the design's tier geometry. Check the design's license before sharing either output.
When you attach a photo to a logged stone, Culet uses Apple's photo picker to import the image you choose into its own on-device storage (downscaled). It has no camera permission and reads nothing else from your library.
.ASC text; adapted copies you saveA completed device backup may include this local data, depending on your settings. There is no in-app bulk export, import, or backup feature; individual items leave only when you choose to make a cutting-card PDF or a stone share card and hand it to the iOS Share Sheet.
Culet offers an optional Pro tier (a one-time Lifetime purchase, plus annual and monthly plans) through Apple's StoreKit 2. When you purchase, restore, or when the app checks your entitlement, your device talks directly to Apple. Culet receives only the entitlement status and a purchase identifier — never your Apple ID, payment method, or transaction history. Apple's handling is governed by Apple's Privacy Policy.
Adding a stone photo uses Apple's system Photos picker, which supplies only the images you choose without requiring full-library read permission. Apple's Photos service may first retrieve a selected iCloud image. The App requests no Camera, Microphone, Location, Contacts, Notifications or HealthKit access. Files you import, purchase services, external links and destinations you choose have their own system or provider handling.
Culet is a planning and reference companion for the lapidary craft of gem faceting. It is not an appraisal or valuation tool and makes no claim about a finished stone's brilliance, quality, or value. Angles and estimates are planning aids; proof-cut and verify against your design's instructions. It is not affiliated with any faceting-software publisher; it states .ASC file compatibility only as a factual format note.
Culet is a hobby tool intended for adults. It is not directed to children and does not knowingly solicit children’s personal information through support. Contact us if a child has sent information so we can address the request.
If a future release ever changes how the app handles data — for instance, if a later version ever introduces sync, analytics, or a third-party integration — this policy will be updated and the change surfaced in the app before that feature ships. The "Last updated" date reflects the latest revision.
Culet's widget displays locally prepared summaries of app records. The app and its widget exchange the relevant summary and preferences through an on-device shared container; this is not a developer-operated record upload. Information displayed by a widget can be visible to people able to view the Home Screen or Lock Screen where it is placed. Use the widget and device display settings to control that visibility. Screenshots and independent copies remain separate from the records you later edit or delete.
When you start a supported session, the optional Live Activity can display session progress on the Lock Screen or Dynamic Island. The activity is updated locally and can be ended through the available activity or system controls. Its visible information is separate from the privacy of an unlocked app screen.
Deleting an imported or adapted design removes that design record. Cut sessions retain their own frozen design snapshot, and stone records keep separate identifiers and saved design names; deleting the design does not cascade-delete those records or replenish the trial-import allowance. There is no Recently Deleted recovery for a removed design.
The updated stone editor keeps text edits and new photo selections on the open screen until Save. Failed saves keep those entries available for retry and restore the affected saved record; a new stone can be retried without creating duplicate entries. Cancelling discards unsubmitted form input and in-memory photo selections. These drafts are not a restart-persistent backup. Sharing a stone card still excludes design diagrams.
Original stone-photo files are kept until the database change succeeds. A local filename journal is prepared before committing removal; cleanup then checks committed stone references and keeps a file referenced by another stone. Failed save attempts retain selected image bytes on screen and attempt to clean newly written, uncommitted files. A normal launch with the saved archive available and Retry photo cleanup in the App retry journalled work. Temporary preview stores do not trigger production-photo cleanup. If the journal cannot be written, filenames can be held only in memory for retry while the App remains open; interruption can leave untracked draft files. Cleanup and record saving are separate, and residual files may remain. There is no Recently Deleted media recovery or full-collection restore through design import.
Original system media, exports, recipient copies and older backups remain separate. Device-backup recovery needs a usable completed copy. Earlier versions may remove files before saving.
These legal pages are hosted on Vercel. Opening a page sends ordinary request information, such as the IP address, browser information and requested URL, to the host for delivery and security; see Vercel’s Privacy Notice. This website request is separate from App record storage. If you email support, we receive the address and information you choose to send so we can respond. Send only the details needed for that request.
If the persistent database cannot be opened, the updated App shows recovery help without opening a substitute empty database for normal recording or editing. The App keeps the existing database and attachment files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.
Older installed versions may use different save or cleanup ordering and may not offer these retry controls.
The updated App reports a parsed design that cannot be saved as a save failure, keeps the original selected file outside the App unchanged and does not consume a free trial import for that failed write. Select or open the original file again to retry. The two-import allowance is a local successful-import counter, not a count of currently stored designs; successful repeated imports can create additional copies and deleting a design does not replenish it.
Saving an adaptation creates a separate checked design record; a failed write leaves the calculated result available in the open screen for retry and keeps the original design. Built-in library setup reads existing rows before changing them and marks setup complete only after a successful save. Previously user-modified and non-bundled material rows are retained; bundled facts are refreshed in place without replacing the identity used by an open screen. A setup failure offers Retry Library Setup and does not deliberately discard existing user records.
Starting a cutting session saves the new session together with the status change of earlier live sessions. If saving fails, the previous live session and its pending progress remain available. Index, lap and checkpoint edits retain their live-edit behaviour: if saving fails, the changed progress remains in memory with Retry Save, and external activity/widget updates wait for a successful save. These pending values are not restart-persistent backups. Completing or abandoning a session changes its saved status before ending its Live Activity; a failure keeps the session available for retry. Session completion and the optional later stone-log form remain separate operations; cancelling the log form does not undo an already saved completion.
Optional stone measurement fields accept complete finite numbers or a deliberate blank to clear the field. Invalid temporary text remains editable and must be corrected before Save; it is not silently treated as an instruction to erase a previously stored measurement.
Unreadable saved session-progress bytes are kept rather than being replaced with an empty progress record by a new toggle. The updated session screen identifies this condition and asks you to contact support. Recovery is not guaranteed. A widget count read failure retains the prior summary instead of publishing an empty count.
The cutting-card PDF keeps the chosen design's schematic and paginated tier labels, displayed angles and full index lists. It does not include the complete original ASC text, unparsed source lines, session progress or a restorable database archive. Each page carries a planning-aid and sharing-rights notice. Generation uses Apple rendering frameworks on the device; it is separate from sharing or filing the resulting file. Check the licence for any imported or adapted design before sharing. A stone share card remains a separate image without design geometry.
The system photo picker supplies selected stone-photo items without full-library read access. If you separately choose Save Image from the share sheet, iOS may request add-only Photos access to save that generated share card. That action creates a separate Photos copy, which can sync under your Photos settings and is not removed by deleting the stone record. No automatic request to read the full library or upload the records is added.