Last updated: 23/10/2026
This policy explains how Pronto Host processes personal data under Regulation (EU) 2016/679 (GDPR). The Italian version prevails in case of discrepancy.
Check-in privacy noticeThe controller is MYLAE DIGITAL DI DAVIDE MERENDA, Piazzale Europa n. 2, int. 1 — 98057 Milazzo (ME), Italia, C.F. MRNDVD91D18F158T – P.IVA 03878780836. For any request about your data, contact hello@pronto-host.com.
MYLAE DIGITAL is an independent controller for account, billing and its own service-management data, and a processor for guest data collected by the host for check-in.
Account data: email address and, if you sign up with a password, the password (stored encrypted). If you sign in with Google, authentication is handled by Google and we do not process any password.
Property data you (the host) enter: property name, address, phone, optional WhatsApp and email, Wi-Fi name and password, check-in/out times, access codes and guide content.
Payment data: handled entirely by Stripe; we never store card numbers. We keep only technical identifiers (e.g. customer/subscription IDs) and subscription status.
Referral data: your invite code, the links between referrer and referred users, and technical records needed to apply, reverse, and reconcile Stripe balance credits.
Technical data: functional cookies (language, session, referral) and technical logs needed for operation and security.
Providing the service (creating, generating, editing and publishing guides): performance of the contract.
Managing subscriptions and payments: performance of the contract and legal obligations.
Security, abuse and fraud prevention: legitimate interest.
Service communications (e.g. password-reset emails): performance of the contract.
Data is used to identify guests and make the mandatory report to the public-security authority through Alloggiati Web (Article 109 of Italy's TULPS). The legal basis is the operator's legal obligation, Article 6(1)(c) GDPR. Consent is not requested for this report; acknowledging this notice is not consent. Without the required data, the operator cannot complete the legal requirements for accommodation. Contact them if you need another collection method. At properties with tourist tax configured, a separate operational register uses only accepted guests' first and last names, linked to technical stay and guest references, to correctly attribute individual stays, early departures and tax counts. The legal basis is the operator's legitimate interest in correctly managing the stay and tourist tax, Article 6(1)(f) GDPR. You may object on grounds relating to your particular situation by contacting the operator using your booking or invitation details. Acknowledging the notice is not consent to this processing.
We rely on providers that process data on our behalf: Convex (database and backend), Vercel (application hosting), Stripe (payments), Resend (transactional email and consented marketing communications).
If you choose to sign in with Google, Google processes authentication data (your email address and basic profile information) as an identity provider, to let you log in.
When you activate recommendation generation or automatic translations, some property and guide data (e.g. city, address and content to translate) is sent to generation providers: Perplexity, Google (Places/Maps) and Anthropic, to produce nearby places and services or translate content.
We do not sell your data. Any transfer to Meta for marketing measurement occurs only with consent and as described in the dedicated section.
The operator and authorized personnel can access the data, which is reported to the public-security authority. Technical providers involved are Google Cloud Storage for temporary uploads in a private bucket and Google Vertex AI for configured reading, Convex for the database, backend and receipt archive, and Vercel for the application. Subprocessors and their activities are described in the data processing agreement attached to the Terms.
The EU reading endpoint does not mean that every operation by all providers takes place in the EU. Any transfer outside the EEA must comply with Chapter V GDPR, using an adequacy decision or other applicable safeguards. Ask the operator for information and a copy of the safeguards, or contact hello@pronto-host.com for assistance.
Some providers (e.g. Stripe, Anthropic, Google, Perplexity, Vercel) may process data outside the EU, in particular in the United States, on the basis of appropriate safeguards (e.g. the European Commission's Standard Contractual Clauses).
We keep data for as long as needed to provide the service and while your account is active. You can request deletion from the Account section; if you have an active Stripe subscription, you must cancel it or let it end first. Deletion permanently removes the account and its guides. Some technical payment and referral records may be retained as required by law or for audit, fraud prevention, and accounting reconciliation.
Following Alloggiati Web's confirmation of acceptance, Pronto Host automatically starts deleting accepted guests' uploaded documents, OCR readings and transmitted personal-data payload. For partial submissions, deletion covers explicitly accepted guests; rejected data or data with an uncertain result remains temporarily available to resolve the result, for at most 7 days after the attempt. We do not retain an archive of transmitted named guest records. The official receipt and technical metadata needed to identify it are retained for 5 years after submission, without adding document copies or named guest lists.
To recognize guests already reported and prevent duplicate submissions, only accepted guests' first and last names remain in temporary Submission and receipt metadata for 48 hours after submission confirmation, including at properties with tourist tax configured and after early checkout. They are then automatically deleted and no longer accessible. This temporary list is separate from the official receipt: it changes neither the PDF nor the receipt's five-year retention.
Operational names remain available at most until the end of each guest's originally planned departure day in Europe/Rome. Recording actual departure and checkout immediately makes them inaccessible and starts deletion; deleting the stay, fiscal data, property or account, or disabling the purpose has the same effect. Corrections and recalculations neither recreate names nor extend expiry. The separate 48-hour temporary list in Submissions and receipts does not end at checkout or deletion of fiscal data alone. Fiscal history retains references and counts without copies of operational names; the official receipt remains unchanged.
Drafts and unsubmitted check-ins expire two days after the arrival date, counted from 00:00 UTC, or 7 days after creation when no arrival date is set. Automatic jobs perform deletion and retry technical failures. The operator can delete data earlier when it is no longer needed. Account deletion also removes the receipt archive: the operator must download and retain receipts beforehand. These rules apply to data managed by the service; the authorities apply their own retention periods. To help the host identify missed submissions, only the first and last names of unsent guests remain available for 72 hours after the reporting deadline, calculated in Europe/Rome. Names are then deleted too; dates, guest counts and the number of unsent records remain without identifying data.
The operational trial without an account lasts 7 days from the first guide publication or check-in link activation. Alloggiati Web submissions are real and require the host’s verified email and acceptance of the Terms, privacy notice and DPA. The service email is encrypted and used for verification and recovery, without implied marketing consent. Unactivated setup expires after 14 days; the guide, configuration and credentials remain recoverable for 30 days after the trial, then are deleted. Shorter deletion periods for guest documents and personal data remain unchanged. Receipts and minimal technical submission metadata remain stored for five years, with separate verified-email access without an account. Permanent voluntary archive deletion requires confirmation that receipts have been exported. Registration preserves trial deadlines and consumption and does not restore deleted data.
You have the right to access, rectify, erase, restrict or object to the processing of your data, and to data portability. Exercise these rights by writing to hello@pronto-host.com. You may also lodge a complaint with your data protection authority.
The content you publish (the guide) is visible to guests via a link. You are responsible for the data you put into guides and for its lawfulness. Pronto Host processes that data on your behalf solely to show it to guests.
The guest-data controller is the accommodation operator who invited you to check in. Contact them using the details in your booking or invitation. The operator must provide their full identity and contact details. Pronto Host processes this data on the operator's behalf as a processor under Article 28 GDPR. The service provider is MYLAE DIGITAL DI DAVIDE MERENDA, Piazzale Europa n. 2, int. 1 — 98057 Milazzo (ME), Italia; C.F. MRNDVD91D18F158T — P.IVA 03878780836; hello@pronto-host.com.
We process first and last name, sex, date and place of birth, citizenship, stay dates, family or group composition and, when required for the guest category, document type, number and place of issue. Booking references may also be included. When you upload a document, its image or PDF and extracted fields are processed temporarily. Uploading a document for every family or group member is not necessary where the law does not require their document details.
Automatic document reading suggests fields for you and the operator to review and correct before submission. It does not decide admission on its own. The reading flow may use Gemini through Google Vertex AI's EU regional endpoint; other reading services, such as Google Document AI, operate only if configured. Copies help prepare the report and are not used to build a document archive.
Host accounts are for adults. Check-in may include child guests whose data is supplied by a family member or accompanying adult for applicable registration obligations; it is not used for marketing.
We may update this policy; the version in force is the one published on this page, with its last-updated date.
When enabled, we use Sentry with the Germany data region for application errors, Better Stack with intended EU processing for availability and on-call, and Vercel Web Analytics and Speed Insights for aggregate technical measurements in production only. We minimize data before sending it and target a maximum 30 days for error and diagnostic-log retention. Actual configuration, DPAs, subprocessors, location and retention are checked before activation; these tools are not intended for advertising profiling.
We may send one promotional reminder about the referral programme on the basis of legitimate interest. You can object at any time using the unsubscribe link in the email.
If you have not activated a plan 24 hours after creating your account and chose to receive promotional emails, we may send you one email with a discount on the first 30 days. The offer expires after seven days. You can withdraw consent at any time in your account settings or via the unsubscribe link in the email.
With your verified marketing consent, Pronto Host may send you one email with an Early Bird offer to return to your draft. The offer gives you 50% off the first 30 days and is valid for 7 days from issue.
You can withdraw consent at any time using the unsubscribe link in the email. Links and encrypted content are removed when no longer needed. We retain minimal data to prevent duplicate emails and attribute conversions, and aggregate metrics for 90 days.
The virtual assistant starts when you choose. Recent messages pass through our servers to Anthropic to select answers about Pronto Host. Do not enter sensitive or guest data. Pronto Host does not archive conversations in its databases: up to 12 messages remain in the tab's sessionStorage, removable with Clear conversation or when the tab session ends. Anti-abuse limits use HMAC-derived IP identifiers. Chat statistics require marketing measurement consent and contain no message text, email or tokens.
Requesting Early Bird is optional and separate from subscribing to other promotional emails. Resend delivers one email to verify the address; after confirmation, Stripe creates the discount and makes it available directly on the website to eligible users. We record encrypted email, an HMAC digest, language, request date and version. The single-use verification link lasts 30 minutes; unverified requests are deleted in the next cleanup cycle after 24 hours. Verified contact data is minimized 30 days after offer closure or expiry. Technical digests and unsubscribe or delivery-failure evidence may remain for a further 90 days to prevent duplicate or unwanted sends. Unsubscribes and delivery reports are respected. To exercise your rights, use the contact address in this notice.
Only with your consent do we use Meta Pixel and Conversions API to measure campaign visits, registrations, checkout starts and first confirmed purchases, attribute results and optimize ads. Meta measurement is off by default and your choice does not affect use of the service.
After consent, the browser Pixel can observe the current page URL, including campaign parameters visible in the browser. For server-side Conversions API events, we accept only approved Pronto Host origins and remove the query and fragment before storage or delivery. For eligible events we may also send Meta event metadata, IP address, browser/user-agent information, identifiers such as _fbp and _fbc, and normalized, hashed email. We do not send Meta passwords, Wi-Fi passwords, access codes, property or guide content, or payment-card data.
Meta may process this data as a recipient and, where applicable, an independent controller, including through international transfers under its safeguards. Information: https://www.facebook.com/privacy/policy/ and https://www.facebook.com/business/help/AboutConversionsAPI.
Separately from Meta, Pronto Host may retain validated campaign parameters for up to 7 days as first-party attribution and connect the source to an account after verified registration. Vercel measures the banner experiment and funnel in aggregate, with URL query data removed; we do not use it to reconstruct individual visitors. Information: https://vercel.com/docs/analytics/privacy-policy.
You can withdraw consent at any time using the persistent Cookie control. Withdrawal blocks future Pixel and Conversions API events and removes marketing identifiers writable from our domain; it cannot recall events already delivered. We keep the functional consent receipt, including policy version and decision date, for 6 months. For access, correction, deletion, restriction, objection, portability or a complaint, use the contacts and procedures in the rights section.
Only with your consent, on public marketing pages and in the check-in demo and setup journey, we use Microsoft Clarity to produce session recordings and heatmaps and understand how navigation can be improved. Clarity may collect URLs, technical browser data and interactions such as clicks, scrolling, pointer movements and window resizing.
Assistant conversations and their forms are masked. In the check-in journey we mask all text, images and fields, including dialogs. We do not activate Clarity in the operational area with real guests, the dashboard, or sign-in and recovery pages. We do not send Clarity passwords, guide content or custom identifiers. We signal consent for analytics storage and denial for advertising storage.
Microsoft may process data outside the EEA under its safeguards. Playback recordings are retained by Clarity for 30 days; after that, it may retain for up to 9 months a sample equal to 1% or 10 recordings per day, whichever is higher. Click data, heatmaps and labeled or favorited sessions may be retained for 9 months. Information: https://learn.microsoft.com/en-us/clarity/ and https://privacy.microsoft.com/privacystatement.