Privacy Policy

Privacy at a glance

Your stitching projects are local by default. Source patterns, converted projects, progress, notes and project photos normally remain on your device or in the local folder where you saved them. Ruta does not currently provide general cloud synchronisation or server backup for the project library.

Some account and technical information is sent to Ruta services. Ruta uses account, trial, purchase, security and diagnostic information to provide access, restore purchases, investigate import compatibility, maintain the service and process account deletion.

Source PDFs have a separate diagnostic-sharing control. Ruta asks for explicit one-time consent before this sharing is authorised. The switch may initially be shown as on in the consent screen, but no PDF or technical report is authorised for upload unless you select Allow. Selecting Continue with the switch off keeps sharing disabled, and you can turn sharing off later.

Ruta does not sell personal data or use it for behavioural advertising. The app does not contain third-party advertising SDKs, and project content, account data and telemetry are not sold to advertisers.

1. Information Ruta processes

Authentication, profile and account data. Ruta may create a background anonymous technical session and identifier so that trial and access checks can work before you create a visible account. If you continue with email, we process your email address, Ruta account identifier, optional display name, verification and session information, login events and account status. Ruta does not receive your email password.

Trial, access and purchase data. We process trial start and expiry, trial-consumption status, entitlement state, promotional or tester grants, lifetime access, store and purchase identifiers, product information, transaction or purchase history needed for access, and purchase-restoration results. Payment-card details are handled by the relevant app store or payment provider and are not provided to Ruta.

Device, network and security data. Ruta and its hosting providers may process platform, operating-system and app/build version, IP address and request metadata, security events, and a pseudonymous device-derived proof used where supported to enforce trial eligibility and prevent repeated-trial abuse. The server is designed to receive a cryptographic or otherwise pseudonymous representation rather than the raw underlying device identifier where the platform supports that design.

Routine product and import telemetry. Ruta may send technical events such as app and build version, platform, timestamps, app lifecycle, import route and outcome, stable error or status codes, performance timings, feature usage, entitlement state, and stitch, page or object counts. Where an account or technical session is present, an event may be linked to that account or session. A source basename, cryptographic file hash and limited pattern or project metadata may be included when needed to correlate an import problem. Routine telemetry is designed not to include full PDF bytes, full project files, raw filesystem paths, passwords, one-time codes, access tokens, email addresses or unrestricted stack traces.

Extracted compatibility diagnostics. When an authenticated import produces an incomplete, rejected or otherwise non-passing technical assessment, Ruta may upload a private account-scoped diagnostic package containing extracted chart structures needed to understand the failure, such as bounded cell, cluster, thread, binding or special-geometry records and related counts or hashes. This package is not the original PDF and is not a cloud backup of the project, but it can contain pattern-derived technical content.

Problematic source PDFs. Ruta has a separate Share problematic PDF files setting under Privacy & diagnostics. Before this sharing is authorised for the first time, Ruta shows an in-app consent screen. The switch may initially be shown as on in that screen, but no PDF or technical report is authorised for upload unless you select Allow. Selecting Continue with the switch off keeps sharing disabled.

With your consent, a complete source PDF and a bounded technical report from an import that ends as partial, unverified, refused, failed or incomplete may be uploaded automatically to private storage for compatibility diagnosis. Complete and cancelled imports are not uploaded through this path. Turning sharing off stops future authorised transfers and requests cleanup of eligible queued or stored diagnostic files, although processing already completed cannot be undone.

If you later adopt a guest library into an account, a never-sent guest diagnostic file may be associated with that account only under the recorded sharing consent. A transfer already attempted under another technical identity is not reassigned.

Local projects, photos and other files. Converted Ruta projects, progress, notes and project photos are processed on the device for the features you choose. They are sent to us only through a clearly identified upload, diagnostic or support action described in this Policy. An account, subscription or purchase receipt does not make the local project library a server backup.

Support and correspondence. If you contact us, we receive your email address, optional name, Ruta account identifier where needed, message, diagnostic information you choose to provide and any attachments. In-app support messages may be linked to your Ruta account so that the conversation can be shown and answered securely.

Website and early-access data. Netlify and related hosting services may process website logs such as IP address, browser or device information, requested page and visit time. If you submit the early-access form, we process your email address and selected device. The website does not use third-party advertising analytics or advertising cookies.

2. Why the information is used

We use the information described above to operate Ruta; provide anonymous and signed-in sessions; start and enforce the seven-day trial; verify paid, tester, promotional and lifetime access; restore purchases; secure accounts and services; prevent fraud and trial circumvention; import patterns; diagnose compatibility, reliability or performance problems; improve product reliability; answer support requests; process account deletion; comply with store requirements and law; and communicate material service or policy changes.

Ruta does not use project content or telemetry to build advertising profiles. Where applicable law requires a legal basis, processing may be necessary to provide the service or perform a contract, based on your consent for an optional action, necessary for legitimate interests such as security and product reliability, or required by law. You may withdraw consent for an optional activity, but this does not affect processing already completed lawfully.

3. Service providers and sharing

Ruta does not sell personal information and does not share it with advertisers. Information is shared only as needed with authorised Ruta operators and service or distribution providers, including:

• Supabase, for authentication, anonymous technical sessions, server functions, entitlement records, private telemetry and diagnostic storage, support and account-deletion processing;
• RevenueCat, for purchase and entitlement management, restoration and deletion of the associated RevenueCat customer where applicable;
• Google Play, Apple App Store, Microsoft Store or another distribution or payment provider, for downloads, purchases, subscriptions, refunds, transaction history and store-account functions;
• Netlify, for website hosting, technical logs and early-access form submissions;
• email, hosting and security providers, where needed to deliver support, messages and maintain the service.

We may also disclose information when reasonably necessary to comply with law, protect users or the service, investigate fraud or security incidents, or complete a business transfer subject to applicable safeguards. Service providers may process information in countries different from yours. Where required, we use the contractual or other safeguards required by applicable law.

4. Patterns, diagnostic files and artificial intelligence

You keep any rights you already have in your patterns, designs, notes and photos. Processing or sending a file for a selected feature does not transfer ownership to Ruta.

Private telemetry, extracted compatibility diagnostics and an uploaded problematic PDF may be inspected by authorised Ruta operators only as needed to investigate compatibility, security or support. Their submission does not give Ruta permission to publish or sell the file, use it for advertising, add it to a permanent compatibility corpus, or use it to train an artificial-intelligence model. We will request separate, express permission before any such additional use.

Support attachments may be inspected to answer your request and diagnose the problem. Avoid sending material you are not legally allowed to share or information that is not needed for support. If Ruta later offers an optional cloud artificial-intelligence feature that sends project content to another provider, a separate in-app disclosure will be provided before that transfer.

5. Retention

Account, session and entitlement information is kept while needed to provide or restore access, secure the service and meet legal or store obligations. Purchase and entitlement records may be retained for accounting, fraud prevention, dispute handling and restoration of valid access.

Routine telemetry and extracted diagnostic packages are kept only as long as reasonably necessary for import investigation, reliability, security, support and legal obligations. Account-linked telemetry and private diagnostic objects are included in the account-deletion process unless limited retention is required for a legitimate reason described below.

When source-PDF diagnostic sharing is enabled, the local staged diagnostic copy is normally removed within seven days. A remotely uploaded problematic PDF is assigned an expiry, normally 30 days after staging and no later than 90 days under the current server policy. Retry does not extend that expiry. Secure deletion may finish shortly after the expiry while a worker completes cleanup. After file deletion, a limited operational record may remain for idempotency and security, with the stored file and identifying file metadata removed or scrubbed.

A pseudonymous trial-consumption or device-security record may remain after sign-out, reinstall or account deletion for as long as reasonably necessary to enforce one trial per eligible device, prevent abuse and protect the service. A limited account-deletion receipt or tombstone may also remain to prevent an old session or delayed request from recreating deleted data. These records are not used for advertising or to recreate the deleted account.

Support correspondence and attachments are kept while the request is active and afterwards only as needed for follow-up, security, dispute handling or law. Early-access contact information is kept while needed to respond to the request or send the requested availability notice, unless you ask us to remove it sooner.

Local project data is controlled through the app and device storage. Ending a trial, subscription or granted entitlement does not by itself create an automatic project-deletion schedule. Local data can still be lost if you delete projects, uninstall Ruta, clear app data, delete local files, lose the device or experience storage failure.

6. Account and data deletion

You can request deletion from inside Ruta or through the public Ruta account-deletion page. Ruta may require fresh email verification or other reasonable verification before accepting the request.

After a verified request is accepted, deletion may be queued briefly for secure processing. Access associated with the deleting account is blocked while cleanup proceeds. The deletion process removes the Ruta authentication user, profile and account data, account-linked entitlement records, support conversations, telemetry and diagnostic records, private account-owned storage objects and the corresponding RevenueCat customer where applicable.

Limited information may remain where necessary for security, fraud and repeated-trial prevention, proof that deletion was completed, valid purchase or entitlement restoration, accounting, dispute handling or legal compliance. App stores and payment providers may also retain transaction information under their own rules. Aggregated or irreversibly anonymised information may remain because it is no longer linked to the account. Temporary deactivation or freezing is not treated as account deletion.

Deleting a Ruta account does not automatically cancel an app-store subscription and does not automatically erase independent local project files on your device. The account-deletion page explains how to cancel a subscription and remove local files separately.

7. Security

Ruta uses technical and organisational safeguards appropriate to the information and service. These include encrypted network connections, account-scoped access controls, private storage, server-side credentials, signed or verified entitlement information, bounded diagnostic payloads, restricted administrative access and controls that block an account and older sessions after a verified deletion request is accepted. No storage or transmission method is completely secure, so absolute security cannot be guaranteed.

8. Your choices and rights

You can turn Share problematic PDF files off in Ruta’s Privacy & diagnostics settings. Turning it off prevents future authorised uploads and triggers cleanup of eligible queued or stored diagnostic PDFs, but it cannot reverse analysis or processing already completed lawfully. You can also choose whether to provide an optional profile name, support attachment or early-access email.

Depending on applicable law, you may request access, correction, deletion, restriction, objection or a portable copy of personal information, and may complain to a data-protection authority. You may also unsubscribe from optional product email. Contact support@rutastitch.com and include enough information for us to identify the relevant account or request.

Some information is necessary for Ruta to provide authentication, access verification, security or purchase restoration. If you ask us to delete information that is necessary for an account, the account or related service may no longer work.

9. Children

Ruta is not directed to children below the minimum age at which they may independently consent to the relevant data processing in their country. A parent or guardian should supervise use where required. Contact us if you believe a child provided personal information without the required permission.

10. Changes and contact

We may update this Privacy Policy when Ruta, its data practices, service providers or legal requirements change. The updated date above identifies the current version. Material changes will be communicated in the app, on the website, by email or through the relevant store when reasonably required.

Privacy questions, requests and complaints can be sent to support@rutastitch.com. Ruta Stitch is an independent software project operated by an individual developer. Verified developer or seller information may also be shown in the relevant app-store listing, distribution page or purchase receipt.