Privacy Policy

Who We Are

Fileika is provided by Vasily Pronin, an individual developer based in Israel.

Summary

Fileika is an iOS app for creating, editing, tracking, completing, and sharing filet crochet patterns.

Project data, photos, and certain account settings are stored locally on your device and may be synchronized through Supabase when cloud sync is available. Fileika uses third-party services for authentication, subscriptions, public shared links, crash reporting, and performance monitoring, as described below.

Fileika does not include advertising SDKs, Google Analytics, cross-app tracking for advertising, location tracking, contacts access, or microphone access.

Information We Collect

Account Information

The current version of Fileika requires Sign in with Apple. Fileika uses the Apple identity token to authenticate your account through Supabase. Depending on what Apple provides and what you allow, we may receive and store your user identifier, email address, full name, and account creation date. We do not receive your Apple ID password.

Account Settings

Fileika stores certain settings associated with your account, including your default crochet hand for new projects. This setting is stored locally in the storage namespace for your Fileika account and, when cloud sync is available, may be sent to Supabase and synchronized across devices signed in to the same account. The synchronized settings record may include your Fileika account identifier, selected crochet hand, and creation and update timestamps. First-project onboarding completion is currently stored locally and is not synchronized through Supabase.

Project and Pattern Information

Fileika stores project information locally on your device, including project name, identifiers, timestamps, pattern size, pattern grid data, template origin, crochet hand, starting corner, counter settings, current row and segment, completion state, and deletion metadata. When cloud sync is available, this project information is also sent to Supabase so it can be synchronized across your devices.

Progress and Timing Information

To support row tracking and time estimates, Fileika stores individual timing events and session identifiers locally on your device. Derived speed estimates, sample counts, confidence values, and current progress may be stored with the project and synchronized through Supabase when cloud sync is available.

Deleted-Project Information

When you delete a project, Fileika removes it from local project storage and queues permanent deletion from Supabase. If the project was synchronized, its cloud data and associated files may remain until the deletion request completes. After server deletion, Fileika retains a limited deletion record containing the project identifier, deletion timestamp, and storage-cleanup status to prevent an obsolete copy on another device from restoring the project and to complete file cleanup. This deletion record is removed when the Fileika account is deleted.

Support Communications

If you contact us, we receive your email address, message, and any other information you choose to include. When support is opened from the app, the message may be prefilled with diagnostic information such as the app version, build number, operating-system version, device model, locale, Fileika account identifier, screen or operation, and timestamp. You can review, edit, or remove this information before sending the message. We use it only to respond to your request and diagnose the reported issue.

Photos

If you attach a photo to a completed project, Fileika stores the photo locally on your device and may sync it to Supabase Storage when sync is available. Fileika may store the photo file, filename, image format, file size, and upload timestamp.

Fileika uses the camera only when you choose to take a photo. Fileika uses the system photo picker when you choose an image from your photo library.

Public Sharing

When you share a project, Fileika creates a public share record linked to the source project. The public page may display the project's current name, pattern, dimensions, generated pattern preview, optional elapsed time, and attached project photo. Changes to the source project may therefore change what the link displays.

A recipient can import the pattern into a new project. The imported project does not include your progress, attached photo, crochet hand, or starting corner.

Anyone with the link, including recipients, messaging services, search or preview bots, may be technically able to request, view, copy, or save the public content until the link expires, is revoked, or is removed. Fileika does not control copies made by third parties, and revoking a link cannot delete copies already made by others. Do not share a project if it contains information you do not want others to see.

Purchases and Subscriptions

Fileika uses RevenueCat and Apple to manage subscriptions and paid limits. RevenueCat may process a Fileika account identifier or an anonymous RevenueCat identifier, product identifiers, entitlement and trial eligibility, subscription period, expiration and renewal status, cancellation or billing-issue status, and purchase or restore results. RevenueCat also uses purchase history to provide subscription analytics, customer history, charts, and related subscription-management features.

Cloud synchronization of private project data, attached photos, and account settings requires an eligible subscription. Public shared links remain available without a subscription. Fileika may also contact Supabase without a subscription when needed to authenticate your account, maintain account metadata, or delete previously synchronized data.

We do not store your payment card number. App Store payment processing is handled by Apple.

Diagnostics, Performance, and Technical Information

Fileika stores app preferences and synchronization state locally on your device. As described above, your default crochet hand may also be synchronized as an account setting when cloud sync is available.

Release builds use Firebase Crashlytics to receive crash reports and selected important non-fatal errors. Reports may include a pseudonymous installation identifier, Fileika account identifier, crash stack trace, exception type and message, app version, device model, operating-system information, timestamps, app state, operation and error classification, and opaque project, draft, or purchase-package identifiers. Fileika does not intentionally send project names, pattern grids, or photos as diagnostic attributes, although operating-system or third-party error messages may contain incidental technical values.

Release builds use Firebase Performance Monitoring to measure app startup, network requests, and selected operations. Performance data may include installation and session identifiers, device and app information, duration, response code, response size, network URL without query parameters or request payloads, and country inferred from IP address. Fileika does not use Google Analytics.

When you use the app or open Fileika web links, Apple, Supabase, RevenueCat, Google Firebase, Cloudflare, or their infrastructure providers may also process IP address, user agent, device or browser information, request URL, request time, and security or operational logs.

How We Use Information

• Create and authenticate your account.
• Save, edit, restore, and sync your projects.
• Remember and synchronize eligible account settings across devices.
• Track crochet progress and estimate remaining time.
• Attach and display completed-project photos.
• Create project thumbnails, shared pattern links, and rich link previews.
• Enforce subscription and free-tier limits.
• Process purchases and restores.
• Diagnose crashes and important errors, measure performance, and maintain app security and reliability.

Legal Bases for Processing

Where applicable law requires a legal basis, Fileika processes personal information as necessary to provide the app and services you request and perform our agreement with you; for legitimate interests in diagnosing errors, measuring performance, maintaining security and reliability, and responding to support requests, where those interests are not overridden by your rights; and to comply with legal obligations.

How We Share Information

We do not sell personal information or share it for cross-context behavioral advertising. We disclose information to service providers only as needed to operate Fileika: Supabase, Google Firebase, RevenueCat, Apple, and Cloudflare.

We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer such as a merger or acquisition.

Data Storage and Retention

Account information, synchronized account settings, and synchronized project data are retained while your Fileika account remains active or until you delete the relevant content or account. Local projects, settings, and photos remain on your device until you delete them, account-deletion cleanup completes, or the app's data is removed. Support communications may be retained for as long as reasonably necessary to respond, maintain support history, resolve disputes, or comply with legal obligations.

Shared links may remain available until they expire, are revoked, or are deleted. Subscription records are retained by Apple and RevenueCat according to their own policies and operational requirements.

Crashlytics and Performance Monitoring data is retained according to Google's Firebase retention practices. Service-provider backups and security or operational logs may remain for a limited period after deletion where technically necessary or legally required.

Your Choices

• Choose whether to attach project photos or create public shared links.
• Delete projects or attached photos in the app.
• Manage or cancel subscriptions through the App Store subscription management screen.
• Sign out of your account.
• Delete your Fileika account from within the app.
• Change camera access in iOS Settings.

Signing out does not delete your Fileika account, local projects, cloud projects, shared links, or App Store subscription.

In-app account deletion requires you to authenticate again with Apple. It deletes your Fileika authentication account and associated cloud settings, projects, photos, shared links, and RevenueCat customer record, and revokes Fileika's Sign in with Apple authorization. Limited backup copies, Firebase diagnostic data, and security or operational logs may remain temporarily according to service-provider retention practices or where required by law. Account deletion does not cancel an App Store subscription, which must be managed separately through Apple.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal information, or to complain to a data-protection authority. Contact us to exercise a right. We may need to verify your identity.

Security

We use reasonable technical and organizational measures designed to protect information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

Children

Fileika is not directed to children. We do not knowingly collect personal information from children where parental or guardian consent is required by applicable law. If you believe a child has provided personal information without the required consent, contact us so we can review and delete it where appropriate.

Third-Party Privacy Policies

Fileika relies on third-party services that have their own privacy practices: Apple, Supabase, Google Firebase, RevenueCat, and Cloudflare.

International Processing

Fileika and its service providers may process information outside the country where you live. Privacy laws in those locations may differ from those in your country. International transfers are handled in accordance with applicable law and the safeguards offered by the relevant service provider.

Changes

We may update this Privacy Policy from time to time. The updated version will be indicated by the "Last updated" date at the top of this page.