Privacybeleid

A) Who we are (data controller) + contact

Setri (“we,” “us,” or “our”) is responsible for processing the information described in this Privacy Policy.
Contact: info@elecho.io

B) Scope of this policy

This Privacy Policy covers information handled by the Setri mobile app, including local data stored on your device and information sent to third-party services for crash/error reporting, feedback submission, and analytics when enabled by app configuration.

It does not cover third-party websites you choose to open from within the app.

C) Data we collect

Local data on your device

Setri stores workout/exercise information and app preferences on your device using React Native AsyncStorage. This is local-only persistence and persists across app restarts.

Stored categories include workout history, a workout draft, templates, exercises, shortcuts, synonyms, supporter status, and preferences (including onboarding/retention-related timestamps).

Telemetry / analytics

Analytics/telemetry are controlled by app configuration environment variables. When enabled, the app may send anonymized/intended-to-be-anonymized usage signals to vendors.

expo-insights / EAS Insights: the app code comments indicate expo-insights collects anonymized usage data such as cold starts, app version, platform, and OS version, with “no user identifiers.” Because this is vendor-controlled, we describe this as intended to be anonymized / intended to have no user identifiers per the app code comments.

Vexo: when analytics are enabled and the vendor configuration is present, the app sends events such as onboarding_completed (with an at timestamp), retention_week_1 (with firstOpenedAt and reportedAt), and a test event vexo_test_event (with sentAt and source).

Analytics user binding: the code includes an identify function, but the provided facts indicate there are no other call sites invoking it. Based on this, the app currently does not bind analytics events via that identifier function. The vendor may still collect device/app data necessary for analytics, as configured.

Crash reports / error reporting (Sentry)

The app initializes Sentry and may report errors/crashes only when a Sentry DSN is configured and telemetry is enabled.

The Sentry configuration is privacy-first in the app code, including:

• sendDefaultPii: false (no default PII)
• replays disabled
• performance tracing disabled and profiling disabled
• the app removes event.user before sending
• the app removes event.extra.originalError before sending

Sentry events include app metadata and a country value derived from your device locale (along with items such as app version, environment, platform, and app build if present).

Feedback form

If you use the app’s feedback feature, you provide: message (required), and optionally name and email.

When you submit feedback, the app sends it to Sentry. The feedback submission may include your optional name/email and may also include additional context such as an optional associated event id and tags including a feedback type and supporter status derived from local supporter state.

External links

The app can open external websites using in-app linking, including a feedback board URL (default https://setri.userjot.com, unless overridden by configuration) and support/donation pages such as https://buymeacoffee.com/tarawillink and https://ko-fi.com/tarawillink.

These third-party sites have their own privacy policies and practices. We do not control their practices.

D) How we use your data

• To provide the app experience using locally stored workout/exercise data and preferences.
• To improve reliability by reporting crashes/errors to Sentry when enabled.
• To handle feedback you submit through the app when enabled.
• To understand usage patterns and improve the app via analytics/telemetry when enabled.

E) Legal bases

As applicable under your local laws, we process information for purposes such as providing the service, maintaining and improving the app, and other lawful grounds where required.

F) How we share data (processors/vendors)

When telemetry/analytics features are enabled by configuration, we may share information with the following vendors/processors:

• Sentry (crash/error reporting and feedback submission)
• Vexo (analytics events)
• expo-insights / EAS Insights (usage analytics; intended to be anonymized per app code comments)
• External websites you choose to open (such as a feedback board or support pages)

G) International transfers

Crash reports and analytics data may be processed in countries outside your own. Transfer details and protections are determined by the relevant vendors. As applicable, we take steps intended to meet applicable requirements. For specifics, contact us at info@elecho.io.

H) Data retention

Local data on your device

Your local workout/exercise data and preferences persist on-device and remain across app restarts. They remain on your device until you delete them (for example, by clearing the app’s data or uninstalling the app).

Telemetry / analytics / crash reports / feedback

The provided facts do not specify exact retention periods for Sentry events, Vexo events, or expo-insights / EAS Insights events. Retention varies; see vendor settings and the vendor’s privacy policy.

I) Your choices and rights

For local data

Uninstalling the app or clearing the app’s data removes the locally stored information from your device (subject to your device/OS behavior).

For telemetry / analytics / crash reporting

Telemetry/analytics enablement is controlled by app configuration (environment variables). The provided facts indicate there is no simple in-app user toggle for enabling/disabling telemetry in the settings UI.

If you want to exercise choices related to telemetry or crash reporting, contact us at info@elecho.io and/or the relevant vendors listed above.

J) Children’s privacy

The provided facts do not specify child-focused practices. If you are a parent or guardian and have questions about a child’s use of the app, contact us at info@elecho.io.

K) Security

We use security measures designed to protect information. No method of storage or transmission is completely secure. If we become aware of a security issue, we will take appropriate steps as required by applicable law.

L) Changes to this policy

We may update this Privacy Policy from time to time. The effective date at the top will reflect when the policy was last updated.

M) Effective date

March 20, 2026