Privacy Policy — Elite Manila Escorts

Elite Manila Escorts www.elitemanilaescorts.com

Last Updated: September 11, 2026

1. Introduction

This Privacy Policy explains how personal information is collected and handled on this adult directory Site and in related private coordination.

1.1 Who does what

Platform / Site Publisher: Public website, hosting, security of site infrastructure, analytics configuration, and publishing of profile content. Limited technical access to systems. Does not act as the day-to-day human booker of meetings.
Private Concierge: Client inquiries, booking coordination, availability and logistics, adult verification workflows, safety follow-up, and access to booking-evidence and private operational records needed for those tasks.
Companions: Their own decisions after receiving only the booking information needed to accept or decline.
Infrastructure providers: Hosting, email, forms, analytics, and similar processors under their own terms and security controls.

"We," "us," and "Elite Manila Escorts" in this policy mean the brand operating the Site, acting through the Platform and/or the Private Concierge as described above. Where this policy says Private Concierge, that function (not the Platform's limited technical role) is the primary human controller of booking and verification data.

2. Information Collected

Companion profile information and adult identity-verification records. Public profiles use stage names. Legal names, document details, and private contact information are not published.
Client booking information, collected when someone requests an introduction. This may include full name, Telegram or another agreed contact method, accommodation and confirmed meeting location, private room or unit information, and a required image of the hotel or accommodation booking for the meeting location. We do not ask clients for selfies or identity documents. This Site is for adults 18+. Using it confirms that requirement.
Telegram / messaging content used for coordination: the connected Telegram Business account records supported incoming, outgoing, edited, and deleted conversation material in an encrypted operational Conversation Spine. This includes exact conversation identity and permitted attachment representations. It is not public, analytics data, a generic transcript search service, or a default model input.
Recruitment and applications: information voluntarily submitted through contact or recruitment forms, including name, email address, message, and private application details. The public first-contact form does not collect a photo. Invited private applications collect written details only. Identity is checked in person, and the agency arranges a covered professional photoshoot after 18+ verification.
Technical data: IP address, browser type, and requested pages as needed for security and operations.
Analytics data: a pseudonymous Analytics client and session identifier, pages and product interactions, stable client-booking CTA context and site-relative page path, campaign tags, external referrer hostname, coarse service area, and later booking or application funnel outcomes and booking value. We do not send Telegram destination identifiers, draft messages, booking references, full referrer URLs, or client personal details to Google Analytics.

The public Site does not maintain public client profiles. Authenticated operational accounts restrict private records.

3. How Information Is Used

To publish accurate companion listings and maintain adult-verification records (Private Concierge-led verification; Platform publishes approved profile content).
To process companion applications and recruitment messages submitted voluntarily (Private Concierge).
To respond to inquiries and coordinate requested introductions (Private Concierge).
To coordinate bookings, safety, schedule, and service operations; resolve disputes; and maintain an encrypted operational record available only to authorized Private Concierge staff. Controlled historical Telegram-import work, if separately approved, remains distinct from live capture.
To give a selected companion only the information needed to decide whether to accept a request and to support safety follow-up (Private Concierge).
To secure and improve the Site, measure pseudonymous booking attribution, and comply with legal obligations (Platform for site/security/analytics; Private Concierge for operational booking data).

4. Sharing of Information

We do not sell personal information.

A selected companion receives only the booking information needed to evaluate and carry out the request.
Private room or unit information and stored booking-evidence images remain restricted to authenticated operational access used for concierge work. They are not open to the general public or to companions as downloadable client files.
Pseudonymous usage and funnel data is processed by Google Analytics with advertising storage and personalisation disabled.
Information may also be processed by infrastructure providers under confidentiality and security controls, or disclosed when required by law.

The Platform does not use booking-evidence images or client identity data for marketing and does not publish them on the public Site.

5. Data Security

We use reasonable technical and organisational safeguards.

5.1 Booking evidence

Booking-evidence images received by the Private Concierge are stored outside the public website without added watermarks and can be opened only by authenticated operational access used for concierge work. Companions may see that booking evidence was received but cannot open the stored image.

5.2 Telegram Business Conversation Spine

The connected Business account preserves its supported conversation material in an encrypted-at-rest Conversation Spine for operational coordination, booking and schedule evidence, safety, dispute handling, continuity after restart, and legal obligations. Exact content and conversation identity are available only to authenticated authorized staff and approved internal operations; every allow or deny outcome is audited. We do not expose a public transcript, raw analytics report, or generic raw-content API, and we do not use the Spine as a default input to automated reply models. We record a fixed capture gap when a message or attachment cannot be preserved. Content is retained until an explicit governed deletion; encrypted backups can retain a prior encrypted copy for their stated recovery horizon. A historical Telegram export, if separately authorized, has distinct provenance and is never automatically imported or used for live replies.

5.3 After a meeting is marked safely done

When the provider marks a meeting safely done, the system checks for an active safety/abuse incident, banned-client review, payment dispute, or specifically documented legal-retention requirement. If none applies, booking-evidence images are deleted and the operational record irreversibly removes the client's name, age, contact/account linkage, exact meeting time and location, room or unit, and prior booking reference. We retain only a non-identifying day-bucketed record of the companion, duration, confirmed price, payment/commission status, and coarse attribution totals for reconciliation and aggregate reporting. A later reconciliation correction can change only a status boolean with a day-bucketed audit. It cannot restore a client link or exact timestamp.

5.4 Retention holds and backups

An active retention hold prevents that deletion until every hold is explicitly released. Holds record only a coded reason, responsible role, and audit times. They do not add conversation text or other sensitive content. Encrypted disaster-recovery backups expire within 30 days. A restore from a backup made before deletion must reapply the deletion process before the service is brought online. Companion identity-verification records are retained only as long as necessary for verification, safety, and compliance.

5.5 Bans

If a safety review results in a confirmed ban, we do not keep a client profile or narrative booking history for matching. While the review hold is active, the system may convert an exact Telegram numeric account ID or a legitimately collected normalized phone number into a protected non-reversible matching token, then erase the raw identifier and unrelated booking/location details. Only that token, ban status, a broad reason category, and review/expiry audit metadata remain. Future contacts are checked by exact token equality. We do not use names, display names, username similarity, device fingerprinting, or account binding. A changed or new account therefore may not be recognized.

5.6 Provider recruitment photos

Provider recruitment does not collect a face selfie or identification image. Identity is checked in person, and public photos come from a covered professional photoshoot after 18+ verification. Any leftover applicant-media files on the private volume are deleted by maintenance and are not published or reused.

6. Your Rights

Under the Data Privacy Act of 2012, you may request information about processing, access to your personal data, correction of inaccurate data, object to processing, or request deletion or blocking where applicable. Send the request from an email address or account we can reasonably verify to contact@elitemanilaescorts.com. Operational booking and verification requests may be handled by the Private Concierge. You may also consult the National Privacy Commission's data-subject rights guidance.

7. Cookies

We use essential cookies for Site functionality and authenticated operations, together with analytics technologies that measure Site usage and booking attribution. Booking attribution uses an anonymous handoff reference and does not store the content of a private Telegram conversation. An official client-booking click may be measured once with stable CTA and site-page context before the private Telegram handoff. The Site can privately associate a pseudonymous Analytics identifier with that reference so verified funnel outcomes can be measured. The reference, booking record identifier, Telegram destination identifier, message text, full referrer URL, and personal booking information are not sent to Google Analytics.

8. Changes

We may update this policy. The latest version will be posted here with an updated "Last Updated" date.

Contact: contact@elitemanilaescorts.com