Data and privacy
How wannasmth.com uses data for communication and the personal calendar.
Updated 7 October 2026
Who handles your data
Alexey Drozdov operates this website and personal calendar. For questions about data, corrections or deletion, contact [email protected].
[email protected]Requests and call conditions
The form stores your name, email, note and preferred time to process your request and reply. Sending a request does not confirm an appointment: Alexey approves it or suggests alternatives. Times use Europe/Madrid. Do not include passwords, payment details or other sensitive information in your note. The contact form also forwards your message and any file you choose to attach to the owner.
Personal calendar
The owner’s schedule, habits, addresses and journeys are available in the private account and to his personal assistant NEO for planning. Visitors see available time slots, not private events. A private request link displays its status and alternative times; do not share this link with others.
Google connection
Only the owner connects Google. The application obtains the verified account email, the list of calendars and permission to create and manage separate application calendars. Gmail is used to send replies to call requests; reading email is not requested. Our calendar remains the primary source, and events are copied into a separate Google calendar. Data received from Google is used for these features, is not sold and is not used by this application for advertising or training AI models. Use of Google data follows the Google API Services User Data Policy, including its Limited Use requirements.
Google API Services User Data PolicyProcessing services
The website is hosted on InterServer and served through Cloudflare. Notifications, requests and login codes are delivered to the owner through Telegram; visitor replies use the connected Gmail account. When the owner uses NEO, the assistant receives the necessary schedule and request data. If the owner enables Google route calculation, journey addresses are sent to Google for that calculation. Each service processes the data it receives under its own policies.
Storage and protection
Calendar and request data are stored on a server with restricted access, with backups for recovery. Google tokens are encrypted. Data is kept for schedule management, request handling and subsequent communication. You can ask the owner by email to correct or delete your data; deletion takes account of backups and records already sent to delivery services.
Your choices
Submitting a request and connecting Google are voluntary. Google access can be revoked in your Google Account settings. An essential session cookie is used for owner login; your selected theme is saved in your browser. Private sections do not require advertising cookies.