Privacy

Who is responsible

Juan Salvador Romero Borunda operates Zekt and is responsible for personal information received to provide its services. Address for this purpose: General Retana 304, Colonia San Felipe, C.P. 31203, Chihuahua, Chihuahua, México. Privacy and support contact: zekt.app@gmail.com.

This notice describes Zekt for iPhone, zekt.app, and our support channel. It distinguishes information stored on your device from information you choose to send us or that providers process when you visit the website.

Your training record

Zekt stores routines, exercises, sets, weights, repetitions, duration, distance, effort, notes, history, and preferences locally. You can also record body weight and measurements. Some of this information may reveal health information; avoid entering information you do not need to use the app.

Zekt does not require a Zekt account and does not operate a Zekt cloud or server for your training records. Records are used on your device to display sessions, history, summaries, and progress features. Simply using the app does not give the operator remote access to your training record.

Automatic iCloud backup. If iCloud Drive is on for Zekt, the app saves a copy of your records (history, routines, measurements, notes, and preferences) after each finished workout and once a day. Backups are stored in your private iCloud Drive container, under your Apple Account and Apple's terms. Zekt has no server access to them: we cannot read, recover, or delete them. You can turn the backup off in Zekt → Settings → iCloud backup and delete stored copies from your iPhone's iCloud storage settings. On a new install, Zekt offers to restore a backup it finds in your iCloud. RevenueCat, used only for Premium purchases, is the only network service the app itself uses.

You can edit or delete information using available app actions. Retention also depends on your device and operating system. Deleting the app or losing your device may cause data loss. Any system backups you have with Apple or another provider follow that service's operation and terms; they are not a Zekt recovery service.

Importing, exporting, and sharing

When you import a supported file from another workout app or a Zekt file, the app reads and processes your selected file to create or restore local records. It may contain exercise names, dates, sets, loads, effort, and notes. You do not need to give Zekt your password for any other service. Review the summary, units, and exercise matches before confirming an import.

When you export data or share a routine, Zekt creates a local file and you choose its destination using system options. A backup may contain training history and body measurements. Routine sharing may include weights or progression rules when you enable those options. Check what a file contains before sending it.

If normal opening or export fails, Zekt may offer a SQLite recovery file: a copy of the local database that may include history, measurements, notes, and settings. It differs from the JSON backup and is not restored through the normal Restore data action. Choose a trusted destination and send it to support only when its necessity and handling have been agreed. Recovery is not guaranteed.

Creating files may leave temporary copies in app storage. Sharing does not establish that those copies are automatically deleted. Deleting a record does not update or remove earlier copies; their retention lifecycle is separate.

A confirmed restore replaces the local data covered by the supported format; it does not merge backups or clone every device setting. Deleting records in Zekt does not delete files you saved or sent elsewhere. Recipients and providers you choose apply their own privacy and retention practices.

Device features and external services

Rest alerts use local notifications when you grant permission. Supported Live Activities and widgets may show session information on system surfaces, including the Lock Screen. Review Zekt and iOS display settings if you share or lend your phone.

Apple controls permissions, delivery, and limitations of these features. It may also process App Store, TestFlight, and diagnostic information under its services and your settings. When you provide a TestFlight or support report, we receive information that channel allows you to share. This does not automatically provide us with your full training history.

If you open an external reference or link, the destination website processes the visit under its own terms.

Zekt Premium and purchases

Zekt Premium is an optional auto-renewable subscription sold through the App Store. Apple processes the payment with your Apple Account; we do not receive your card details, Apple Account password, or billing address. Apple handles purchase information under its own terms and privacy policy.

To know whether Premium is active on your device and to restore it, the app uses RevenueCat, Inc., a subscription service provider based in the United States. The app creates a random identifier that is not linked to your name or email. RevenueCat receives that identifier with purchase information from Apple — plan, purchase and expiration dates, trial and renewal status, storefront country, price and currency, and transaction identifiers — and the technical details needed to answer each request, such as app and iOS version, language, and IP address. Your training record, body measurements, and notes are not sent to RevenueCat. RevenueCat Privacy Policy.

We use this information only to provide, restore, and support Premium, to prevent abuse, and to review aggregate subscription figures. We do not use it for advertising or to track you across other companies' apps or websites. To request access to or deletion of purchase records, include the order ID shown in your Apple purchase history so we can locate them.

Website, security, and cookies

Cloudflare provides website hosting and protection. When you access the site, it may process your IP address, requested URL, browser or device information, and technical metadata to deliver content and prevent abuse. The site has no forms and does not require you to sign in; to contact us, write to zekt.app@gmail.com.

Zekt does not use these channels to sell data or serve targeted advertising. We have not added our own advertising tracking tools. A site visit is not necessarily anonymous. zekt.app does not set cookies of its own and uses no analytics, tracking, or advertising cookies. Cloudflare may set a strictly necessary security cookie (such as __cf_bm or cf_clearance) only when it needs to tell people apart from automated traffic or shows a security check; it is not used to identify you across sites or for advertising. Cloudflare Privacy Policy.

Support

Support and security: we use your messages and their context to reply, investigate the reported issue, handle rights requests, and prevent abuse. Reusing an identifiable support request for general product research is a separate purpose that requires your permission; you do not need to accept it to log workouts or receive support. Email addresses are not added to advertising lists or used for unsolicited research invitations.

Why we process each flow: support and security requests are handled to answer what you ask and to protect the service. Sensitive files, such as a backup, are processed only with your prior, express authorization for the agreed purpose. Premium purchase records are processed to provide the subscription you requested and to meet accounting, tax, and legal obligations.

Email support uses Gmail, a Google service. If you contact us, we receive your address, message, email metadata, and attachments you choose to send. App version, iPhone model, iOS version, and steps to reproduce are usually enough to begin an investigation. Do not send passwords or a full backup to begin a request. Before requesting JSON or SQLite, support must explain why it is needed, what it may reveal — including potentially sensitive health data — who will access it, the channel and deletion period, and obtain any required authorization. An unsolicited file does not authorize new uses. If we receive unnecessary sensitive information, we will restrict access and arrange deletion as appropriate. Google Privacy Policy.

Providers and international processing

The providers listed above may process information outside your country. We use their services for hosting, security, email, and subscription management. We do not publish your messages or email addresses. We may prepare summaries that do not identify you; an identifiable quote, screenshot, or testimonial requires separate permission.

We may also retain or disclose information when a valid legal obligation requires it, limited to what is necessary. Destinations you choose when sharing files are separate from the providers we use to operate Zekt.

Retention and deletion

Local records remain under your device's control until you change or delete them, replace them through a restore, or the system stops retaining them. We cannot remotely delete them or recover history that was never sent to us.

Support correspondence is kept while necessary to handle the case and for the defined follow-up, security, and legal retention period. Support messages are kept for up to twelve months after the case is closed, and sensitive attachments are deleted within thirty days after closing or earlier when no longer needed. Exceptional retention required by law is limited to that purpose.

Purchase records held by RevenueCat are kept while needed to provide and restore Premium and for the periods required by accounting, tax, or legal obligations. Apple keeps its own purchase records under its policies.

You may request earlier deletion of information we hold. If we cannot reliably identify a message, we will explain the minimum information that could help locate it. Copies you sent to other recipients are outside our control. Provider recovery copies follow a separate lifecycle: they are kept only for the limited period set by each provider's backup system and then expire. They are not used for research or routine support.

Your rights and requests

You may request access, correction, cancellation or deletion, and objection, as well as restriction of use or withdrawal of consent where applicable. Contact zekt.app@gmail.com with your request, name, a reply channel, and information that helps locate the record, such as the date of your message. For corrections, describe and substantiate the requested change.

We verify your identity or authority to act before releasing or changing information. We will explain what documentation is needed and an appropriate way to provide it; do not attach government identification to your first message. We will not request information unrelated to verification.

Where Mexican law applies, we will communicate our determination within twenty business days of receiving the request and, if granted, implement it within fifteen business days after the response. Each period may be extended once for an equal period where legally justified. Access responses will be delivered in a readable format to the verified channel or through an agreed secure method. If a restriction or retention duty applies, we will explain its basis and limit use to that purpose. Other applicable laws may give you different rights or time limits, which we will respect. Withdrawal of consent does not affect prior lawful processing or applicable retention obligations.

The contact above also receives privacy complaints. You may contact the competent data protection authority. Records that exist only on your device are managed through local app functions; use this contact for rights relating to emails that we do receive.

Minors

Zekt is intended for people aged 18 or older. The initial release is not available to people under 18. If you believe we have received personal information from someone under 18, contact zekt.app@gmail.com so we can review the case and arrange deletion as appropriate.

Changes

We will publish changes on this page with a new effective date. Where required, we will notify you through the appropriate channel and obtain necessary consent before new processing. Changing this notice does not by itself authorize new uses of information.