Privacy Policy

Course 1 of 8

Your rights and self-management

You control the records Loomia keeps. You may inspect project files, row tallies, snag marks, archive cards, and function preference tags. You may correct project names, stitch counts, node schedules, or preference tags. You may delete a project, an archive card, or all local records after a second confirmation.

One-click export packages project progress, preference tags, and archive cards into a file you save through the system Files interface. You may withdraw optional permissions, including photo-library access used only to pick a cover image. You may object to matching that relies on function preference tags.

We honor a complete request without undue delay and do not show internal identifiers or sandbox paths. Incomplete requests receive an explanation; blocked actions are not ignored in silence.

LoomNext course

Course 2 of 8

What the tool writes

Loomia works without an account. Records are created by your use of the tool:

• Craft records you enter: stitch counts, total rows, shaping or color nodes, tap-per-row progress, rip-backs, and pin marks, so the dial can warn you before a decrease.
• Cover images you optionally choose from the device photo library. The app requests only photo-library read access and copies the image into the application sandbox. Loomia does not write to the system album, open the camera, or record audio.
• Function preference tags created in tool-use scenes, such as favored project types, last-used roller values, marker-chip sets, and Fray Guard sensitivities. These tags exist solely for personalized service matching inside Loomia.
• On-device stability signals that never include the pixels of your photos.

We use this material for counting, reverse-planning, archive filing, and preference matching, not for public-model training, ads, or a social graph. Refusing photo-library access disables cover import only.

PreviousNext course

Course 3 of 8

Sharing, store, and risk review

Project files, preference tags, and sandbox images are not uploaded by default. If a future optional collaboration you enable would share a subset of records with a processing partner, two gates must complete first: you give express, separate authorization naming the partner role and record types — silence or a pre-ticked box is not authorization — and we complete a compliance risk assessment of purpose limitation, partner retention, onward transfer, and deletion ability. A failed assessment blocks the share.

We do not sell tool records or share them with advertising networks. No payment processor is used because there are no purchases, virtual currency, or paywalls. Loomia does not sell access, run a coin store or wallet, or charge for any function.

PreviousNext course

Course 4 of 8

Technical protection

Records stay in the application sandbox. Cover images are sandbox copies, so uninstalling Loomia removes them. Operating-system isolation gates access. Preference tags and project files use named keys. Export archives are written only after you trigger one-click export. Integrity checks reject empty temporary files. Preview failures do not undo a successful sandbox copy. The core counting loop does not need a network.

PreviousNext course

Course 5 of 8

Permission and operational review

Each function is mapped to a data type, a lawful reason to hold it, and an export or delete path before it ships. New surfaces are reviewed for permission impact. The only authorized permission is photo-library read access for cover import. Camera, microphone, and album-write capabilities are out of scope. A support export you send is used only to answer you and then discarded. Handling errors are assessed, stopped, and notified when applicable data-protection laws require notice.

PreviousNext course

Course 6 of 8

Scene overlays

A home hobby, a class sample, and a commission may share the same row dial but not the same duties. Loomia keeps a conservative default: records stay on-device, functions stay free, and photo import stays limited to library picks you control. Scene-specific rules are overlays you switch, not hidden profiles.

You must select the overlay that matches your scene. Do not import another person’s work as a cover, or export progress cards, where that scene forbids it. Loomia cannot know classroom or client rules; it honors the overlay you select. Labeling a commission as a private hobby to bypass a rule you accepted elsewhere is your responsibility.

PreviousNext course

Course 7 of 8

How long a record lives

Each record class follows a use-linked life rather than one calendar cutoff. Active projects remain until you finish, archive, or delete them. Archive cards remain until you delete them. Function preference tags remain until you clear them in settings. A sandbox cover is removed with its project. A one-click export file is yours; Loomia keeps no hidden second copy. Uninstalling removes the sandbox. There is no remote locker unless you kept an export.

PreviousNext course

Course 8 of 8

Updates and mailbox

Material changes update the Last Updated line and appear in-app. Continued use after a reasonable chance to review means you accept the revision. Expansions of collection require a fresh acknowledgment.

Questions: Loomia@gmail.com. On data-handling facts, this policy controls; on the device identifier idle clock and session authentication, the Terms of Service control.

PreviousBack to loom