Moredays Privacy Policy

Revision date: 23 September 2026.

Who is responsible

Moredays is operated by Veronika Martynova, an individual based in the United Arab Emirates. For privacy enquiries and rights requests, contact tyanochkamal@gmail.com.

This policy covers Moredays, the rules website moredays-rules.pages.dev, and analytics on the operator-managed landing page relofast-consult.pages.dev. Relofast consultations and Telegram are third-party services with their own terms and privacy practices.

Information on your device

Travel history, countries and dates, manual corrections, visa and residence-permit parameters, limits and preferences are stored locally. Moredays does not require an account or a passport scan.

Location: With your permission, coordinates are used to determine the country using a bundled boundary database. The travel history stores country codes, dates and confirmation information, not coordinates or routes. “Always” permission permits background location events. You can change permission in iOS Settings and use manual entry instead.

Photos: With permission, Moredays reads dates and location metadata from accessible photos to suggest past trips. It does not analyse image content or upload photos to our server. You can review and correct suggested trips before saving. Revoking photo access does not erase trips already saved.

Documents: Visa and residence-permit parameters are used for calculations. They are not sent by Moredays to the rules service or the partner landing page.

Notifications: Reminders are scheduled on the device. This version does not use our own remote push server. You can disable reminders in the app or iOS Settings. Notification text may appear on a locked screen according to your preferences.

Widget: A local shared container supplies the widget with the current country, counters, update time and a forecast. Other people who can see your device screen may see this information.

We do not receive local travel history through a Moredays server. This does not mean that the app and associated websites never access the internet.

Rules updates and hosting

The app downloads rules from moredays-rules.pages.dev. Cloudflare hosts the rules website and the landing page. Requests necessarily expose technical information to the hosting infrastructure, such as IP address, request time and path, and available HTTP headers including client software information, for content delivery and security.

Moredays does not add your current country, coordinates, travel history, visa parameters or advertising identifier to rules requests. Cloudflare processing and logs are governed by its applicable service terms and privacy policy. We do not promise that the host keeps no technical logs.

We do not place Google Analytics or Yandex Metrica tags on the rules website or this privacy page.

Relofast landing page and analytics

When you select visa or residence assistance, the app opens relofast-consult.pages.dev in a Safari browser view. Opening it is optional and is not required to record trips.

The page uses Yandex Metrica counter 112816896 and Google Analytics 4 stream G-S008KNV50E, owned by Veronika Martynova, to measure visits and clicks on the Telegram button. We use these statistics for analytics only, not advertising or retargeting, and do not sell them.

The services may process page and referral URLs, visit times, page-view and click events, browser and device information, browser/cookie identifiers, and approximate location derived from IP addresses. Pseudonymous identifiers distinguish visitors; absence of a person's name does not make data fully anonymous. Google states that GA4 uses IP addresses during processing and approximate-location derivation but does not log or store the IP addresses in GA4.

The landing-page code disables Yandex session replay, click maps and automatic link tracking, and disables Google Signals and ad-personalisation signals. The explicit telegram_click event means a button was clicked; it does not confirm that the bot was started or a consultation obtained. These settings do not prevent standard technical information being sent to analytics providers.

Current implementation: Analytics tags load when the landing page opens. This version has no separate analytics-consent control. You can restrict cookies and website data through browser controls or choose not to open the page. Blocking analytics should not prevent the ordinary Telegram link from working. These controls do not replace prior consent where legally required.

Telegram and consultations

The button links to the Relofast bot with the shared referral parameter rp_martynova. This is not a unique Moredays user identifier. Moredays does not add travel history, coordinates or document parameters to this link.

Starting the bot or sending messages may disclose Telegram profile information and your submissions to Telegram and the bot operator. Review the recipient's terms before sharing documents. Moredays cannot control deletion of information held by those recipients.

Support

Emailing tyanochkamal@gmail.com provides us with your sender address, message and any attachments you voluntarily include. We use these to respond, resolve the issue and meet applicable obligations. Please avoid sending passport numbers, scans or complete travel histories unless necessary for your enquiry.

Processing grounds and international processing

iOS permissions control access to information on your device. Technical network requests support rules updates and page delivery. Support data is used to respond to your request. Depending on applicable law, processing grounds may include fulfilling your request, legitimate interests in service operation and security, a legal obligation, or consent where required. Location permission is not consent to website analytics.

Cloudflare, Google, Yandex, email services and Telegram may process data outside the UAE or your country. Protections may differ. Applicable provider contracts and international-transfer mechanisms must be considered; this policy alone neither authorises transfers nor guarantees compliance in every country.

Retention and deletion

Local history remains while you keep it on your device. Available records can be edited or deleted in the app. Fully deleting the app in iOS removes its principal local container; offloading the app is not the same as deleting its data. Device backups and their deletion are managed separately through Apple. We cannot remotely delete history from your backup.

Widget snapshots are overwritten when updated. System containers and preferences are subject to iOS behaviour. Hiding a card or revoking permission does not mean that all previously stored records are deleted.

Technical logs and analytics data follow the relevant service settings and terms. Cookie lifetime and report-data retention differ. Current retention settings can be requested by email; this revision does not state an unverified single retention period for all providers. Support correspondence is retained as necessary to resolve the request, meet obligations and address related disputes, and should then be deleted or de-identified.

Your rights and security

Depending on applicable law, you may request access, correction, erasure, restriction or portability, object to processing, or withdraw consent. Contact tyanochkamal@gmail.com. We may request minimal information to verify a request. Local records we never receive must be managed on your device. Withdrawal does not affect prior lawful processing. You may also contact a competent data-protection authority.

Rules and web pages are delivered over HTTPS. Local-data security also depends on device protection. No storage or transmission method is absolutely secure.

Children and policy changes

The app is not specifically directed at children. We do not request age or intentionally organise collection of children's data for analytics. Contact us if you believe a child's information was provided through support or an associated site contrary to applicable requirements.

We will update this policy and its revision date when practices change. Publishing a new policy alone does not replace any required additional notice or consent.

Provider policies