Embroidery Journal

1. Scope and who to contact

This policy describes information processed in connection with Embroidery Journal, an embroidery project journal provided under the Set In Stone brand. “We” and “our” refer to the app provider identified on the App Store listing. For privacy questions, requests, or complaints, contact [email protected] with “Embroidery Journal privacy” in the subject. The provider is responsible for personal information it receives through support communications and operation of its website.

This policy distinguishes information stored inside your device from information received when you email us, visit our website, or use Apple’s and RevenueCat’s purchase services. It does not claim that Apple, your email provider, or your device backup provider processes no information. Those providers operate their own services under their own privacy notices.

2. Local journal information

The app stores the information you enter: project titles, creation dates, start and finish dates, notes, favorite status, pattern and designer details, fabric, thread palettes, stitch types, strand counts, and references to imported photos. A project identifier associates each record with its local photos. These records are held in a SwiftData database in the app’s storage on your device.

The app has no app-provider account, authentication service, developer-operated journal server, or CloudKit synchronization. We do not receive your project database or photos through ordinary use of the journal. We cannot open, recover, remotely edit, or remotely erase the journal stored on your device. Information you choose to send in an email is different and is addressed below.

3. Photos, selection, and image metadata

You choose pictures through Apple’s system photo picker. The app imports the images you select into its own local storage to display project covers and photos. It does not upload your Photos library to us. Canceling an import discards the app’s draft files; removing a journal copy does not delete the original picture from your Photos library.

Imported image data is preserved rather than deliberately stripped of metadata. Depending on the source image and what Apple’s picker supplies, a local copy may contain information such as capture date, device details, or embedded location metadata. This metadata stays with the image locally; the app does not transmit it to us. Consider removing sensitive metadata before importing or voluntarily sending an image to support.

Photo access and any system permissions are managed through iOS. You can decline to select photos and maintain text project records. Changing a system permission does not automatically erase copies already imported into the journal.

4. Preferences and purchase information

The app stores local preferences needed for its interface, including your appearance choice and onboarding progress. It uses Apple StoreKit to retrieve the available weekly and lifetime products, display the storefront price, complete purchases, and check whether a verified lifetime transaction or active weekly subscription grants access. Relevant transaction information can include a product identifier, entitlement state, and revocation information.

Apple handles your Apple Account, payment details, receipts, tax information, and payment processing. We do not obtain your full payment-card details through StoreKit. The app’s purchase checks may communicate with Apple and RevenueCat even though your journal remains local. Apple may also provide the developer with sales or financial reports through its distribution services; that does not give us access to your journal.

The app uses RevenueCat to manage purchase reporting and subscription records. RevenueCat receives purchase and receipt information, product and transaction identifiers, subscription or lifetime-access status, a randomly generated app-user identifier, and technical information needed to handle these requests. This identifier is not an app-provider account, name, or email address. We use these records to support purchase access and investigate purchase issues. We do not send journal entries, project notes, or photos to RevenueCat. Apple continues to supply the displayed prices and process payments; RevenueCat does not receive your full payment-card details. RevenueCat’s privacy policy is available at https://www.revenuecat.com/privacy-policy.

5. Analytics, advertising, and automated decisions

The current app does not include third-party advertising, behavioral analytics, crash-reporting, or authentication SDKs. RevenueCat processes the purchase information described above for purchase and subscription management. It does not track you across other companies’ apps and websites, sell personal information, or share personal information for cross-context behavioral advertising. There is no in-app advertising or developer-operated profiling of your projects.

The app does not make decisions about you with legal or similarly significant effects through automated processing. Apple may separately collect diagnostic or usage information according to your device settings and its policies. Diagnostics you choose to share with Apple or voluntarily send us are not the same as an analytics SDK transmitting your journal.

6. Information you send to support

If you email us, we receive your email address, the content of your message, attachments you choose to include, and any details you provide about your device, app version, purchase issue, or project. Please send only information needed to explain the issue. Do not send passwords, full payment-card details, or unnecessary sensitive information.

We use this information to answer your request, investigate defects or purchase-access issues, maintain relevant support records, and deal with legal claims or obligations. It may be handled by the email and communications providers used to deliver and store the correspondence. Your journal is not attached to support messages automatically.

7. Purposes and applicable legal bases

On-device project and photo processing provides the journal functions you request. StoreKit information is used to provide and verify paid access. Where data protection law requires a legal basis for information we process, providing requested support and purchase assistance may be necessary to perform a contract or take steps at your request before a contract.

Our legitimate interests may support proportionate handling of support correspondence to troubleshoot defects, protect services, and establish or defend claims, balanced against your rights. A legal obligation may require specific records. Where an optional use legally requires consent, we will obtain that consent before the use and you can withdraw it without affecting earlier lawful processing. An iOS permission is a technical permission and does not by itself establish every legal basis.

You are not required to send us your journal or photos. Without sufficient details we may be unable to resolve a particular support issue, but declining to send an attachment does not authorize us to access your device.

8. Website access and external services

Opening a support, privacy, or terms link connects your browser to setinst.one, which is hosted through Cloudflare. Serving and securing a webpage involves technical request information such as IP address, requested URL, time, and browser or device request headers. This is separate from the local journal. This static site does not include a marketing analytics script or advertising tracker.

Apple’s App Store, purchase, operating-system, Photos, and backup services, RevenueCat’s purchase-management services, Cloudflare’s hosting services, and your email provider have their own terms and privacy notices. Following an external link or contacting us through email allows those services to process information needed to handle your request. The native journal does not use browser cookies; cookies or technical processing on external services depend on those services.

9. Sharing and international processing

We do not receive or disclose your locally stored journal through normal app operation. Information you voluntarily send us may be disclosed to service providers supporting the correspondence, to advisers where necessary for a claim, or where disclosure is required by law. Any disclosure must have an applicable legal basis; a request alone does not justify unlimited disclosure.

Local storage does not involve a journal transfer to our servers. Apple, RevenueCat, Cloudflare, email services, and any backup services you use may process information outside your country. Where we arrange a restricted international transfer of personal information, applicable law requires an appropriate transfer mechanism, such as an adequacy decision or contractual safeguards, unless a lawful exception applies. This statement does not promise a particular storage country for a service whose processing locations we do not control.

10. Retention, backups, and deletion

Journal records and imported photos remain locally until you edit or delete them or remove the app’s data. Use project editing and deletion to manage individual records. Settings → Delete All Data removes journal projects and attempts to remove their imported photo files. It preserves your Photos library and appearance preference. If the app reports that photo cleanup failed, retry deletion; deleting a record is not a guarantee that every filesystem cleanup succeeded.

Deleting the app normally removes its local app container. Offloading an app can retain its documents and data. Device or computer backups, including iCloud device backups if enabled, may retain copies according to your settings and the provider’s retention rules; the app does not offer its own cloud journal backup. Manage those backups separately. A restored device backup may restore previous app data.

Support correspondence is kept for the time reasonably needed to handle the request and necessary follow-up, resolve a dispute, or satisfy an applicable recordkeeping requirement. Relevance, the age of the issue, unresolved claims, and statutory requirements determine the period. We delete or minimize personal information when it is no longer needed. Purchase records processed through RevenueCat are retained as needed to provide purchase-access support, investigate issues, and meet applicable obligations. Deleting local journal data does not automatically delete these purchase records. Contact [email protected] about purchase-data access or deletion requests. Apple and other independent providers determine retention for their own records; deleting the journal does not erase an Apple purchase.

11. Security and your device

The app relies on Apple’s app sandbox and device security for local storage. Imported photos are written into app-owned files, and the journal is not offered as a developer-operated remote storage service. We do not promise custom end-to-end encryption or immunity from loss. Use a strong device passcode, keep the operating system updated, and take care when granting another person access to your device.

No storage method is completely secure. Device loss, damage, deletion, software errors, interrupted saves, or a failed backup can affect your journal. We cannot recover local-only content from a server. Email attachments and external websites have different security properties from local app storage.

12. Your rights and requests

Depending on applicable law, you may have rights to access, correct, delete, receive a portable copy of, restrict, or object to processing of personal information we hold. You may withdraw consent for consent-based processing. Rights have lawful conditions and exceptions and apply to information actually processed by the relevant controller. We do not deny service or otherwise unlawfully discriminate against you for exercising a privacy right.

You can inspect, edit, and delete the journal directly in the app. The current app does not provide a dedicated journal export feature. We cannot retrieve a local database remotely to fulfill a request. For information you have sent us, email [email protected]; describe the request and use the address used for your earlier correspondence where possible. We may request proportionate verification, but will not ask for your Apple Account password.

Where the GDPR or UK GDPR applies, we normally respond within one month; a legally permitted extension for a complex or numerous request will be explained within that initial period. Other applicable statutory deadlines remain in force. You may complain to the data protection authority in your country of residence, work, or the place of an alleged infringement. You do not have to contact us first. Ask Apple or your backup provider directly about records they control.

13. Children and policy updates

The app is a personal project journal and does not operate accounts or a social service for children. Its local storage design applies to all users. A child’s use and purchases should follow the App Store age rating and involve a parent or guardian where required. If you believe a child sent personal information directly to support, contact us so we can assess and appropriately delete it.

This policy is effective October 5, 2026. We will update this page when relevant practices change and provide additional notice or obtain consent where law requires it. A future networking, analytics, account, or synchronization feature would require a fresh assessment and notice; this policy does not authorize undisclosed future collection.