P01Operator and scope
Zeymivo is a travel planning service operated by Azizkhon Uygunkhujaev, an individual based in Uzbekistan. This policy covers the Zeymivo website, applications and guest use. Contact support@zeymivo.com about privacy or exercising your rights.
P02Information we receive
We process email addresses, sign-in identifiers, display names, authentication provider details and sessions. Guest use creates technical identifiers. You may supply a traveler profile, age group, country, interests, destinations, dates, budget, travel party, children's ages, preferences and requests. We store information you enter, generated itineraries, edits, invitations and publication settings.
The website and applications process technical information about requests, devices, app versions, errors and feature interactions. Support receives your message and reply contact. Do not submit passwords, tokens, passport or payment details, diagnoses or other people's private information.
P03Sign in with Google
When you choose native Google sign-in in the mobile app, the Google SDK sends an identity token to the Zeymivo server. The server verifies it and creates its own session. Zeymivo receives your account identifier, email and available name information. We use these details to create your account, sign you in, communicate with you and associate trips with your account. Account linkage identifiers, profile data and session records are stored in the Zeymivo database; session credentials are kept in secure storage on your device. This sign-in flow does not send Google credentials to Supabase. Existing Google identities and sessions through Supabase remain supported during the transition; their records may remain in Supabase until deletion. Email/password continues to use Supabase. Retention and deletion are described in P07–P08.
The current sign-in integration does not request access to Gmail, Google Drive, Calendar or contacts. We do not receive your Google password. Google sign-in data is not sold, used for advertising or transferred to AI providers for model training. Access and use are limited to the described user-facing features, security and applicable legal obligations. The use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including applicable Limited Use requirements.
You can disconnect Zeymivo through Google Account connections settings. This stops further authorization through that connection but does not by itself erase trips or an existing Zeymivo account. Use the process in P08 to request deletion.
P04Purposes and legal bases
We use information to provide sign-in, create and store itineraries, personalize requested plans, enable sharing, provide support and protect the service. Where GDPR or UK GDPR applies, data necessary for the requested service is processed to perform a contract; limited security and diagnostic operations rely on legitimate interests where permitted, and required records on legal obligations. Where consent is required, it is a separate basis; accepting the Terms does not replace it.
Dietary, mobility and free-text fields may reveal sensitive information. They are not needed for ordinary planning. Provide only necessary information about yourself; do not enter medical, religious or other sensitive information about companions or children. Contact support@zeymivo.com to ask about restricting or deleting information you supplied.
P05AI, providers and transfers
Necessary trip parameters and requests are sent to OpenAI to generate plans. Search stages use public destination context; private wishes, dietary and mobility information are applied in later stages without web search. Account emails, passwords and authentication tokens are not included in generation requests. Do not enter information you do not want processed by AI into trip requests.
Supabase handles email/password sign-in and supported legacy sessions; native Google and Apple credentials are verified by the Zeymivo server. Hosting and database infrastructure support operation and storage. Google Maps and Google Weather provide maps and weather. When error reporting is enabled, Sentry receives sanitized technical error information rather than trip text or passwords. Authorized people access data only for operation, support, security and legal obligations. Partner websites you visit process information under their own policies.
Providers may process data outside your country. Transfers subject to GDPR or UK GDPR use the applicable lawful transfer mechanisms. Contact support@zeymivo.com for questions about recipients, processing locations and applicable safeguards. We do not claim all AI requests are anonymous, that providers have zero retention, or that their own mandatory security logs never exist.
P06Publication, sharing and security
Invited participants access a trip within their role. Publishing makes the selected public version accessible to link recipients; it may be indexed or copied. Review the preview before publishing. Removing publication closes the original link but does not erase independent copies, screenshots or external caches.
We use protected connections, authentication checks, access restrictions and technical data filtering. No system guarantees absolute security. Keep sign-in credentials private and report suspected unauthorized access to support@zeymivo.com.
P07Retention, storage and diagnostics
Account and trip data is retained to provide the service and preserve your plans. Guest session expiry, signing out and uninstalling the app do not themselves erase server records. Following a deletion request we remove associated active data; limited technical records may remain to prevent reuse of old credentials, protect security, meet legal obligations and resolve disputes. Backups and provider records follow their retention cycles and applicable requirements rather than necessarily being erased simultaneously with active records.
The landing page stores your theme under zeymivo-theme in localStorage until browser storage is cleared. Applications and authentication providers use local storage and sessions for sign-in, preferences and requested features. Applications may process pseudonymous usage events and technical errors; no optional analytics trackers are connected on the landing page. These identifiers are not automatically anonymous. Send retention questions and objections to support@zeymivo.com.
P08Your rights and account deletion
Depending on applicable law, you may request access, correction, deletion, restriction, objection or a portable copy, withdraw consent where processing is based on it, and complain to a competent data protection authority. Email support@zeymivo.com. We verify account ownership proportionately; do not send a password, token or identity document with your initial message. We respond within applicable legal deadlines and explain any relevant exceptions.
Use the available Delete account action in the app or email a request with the subject “Zeymivo — account deletion”. Sending an email does not require a web form or installing our app. The request covers your profile, owned trips, generated plans and related identifiable records, subject to lawful exceptions. Other users' independent copies may remain. Uninstalling the app or revoking Google access does not replace a request to delete Zeymivo data. For guest data, describe the available session information without disclosing its secret token.
P09Age and policy changes
Zeymivo is intended for users aged 18 and over. An adult may provide the number and ages of children for a family itinerary, without their names, documents or sensitive details. Contact support@zeymivo.com if you believe prohibited child information has been supplied.
The current policy is published on this page with its update date. We notify you of material changes where required. New purposes or permissions requiring separate consent are not authorized merely by continuing to use the service.