Privacy Policy
Last updated: 2026-09-22
If you accepted an earlier version, this version takes effect for you on 2026-10-22.
This Privacy Policy describes how Play or Party Private Limited ("itsmysite", "we", "us") collects, uses, shares, and protects information when you use our MCP connector to build and host personal websites, when visitors come to those sites, and when you discover or follow other users on the platform (collectively, the "Service").
This policy applies to:
- The MCP connector at
https://mcp.itsmysite.ai; - Our marketing site at
https://itsmysite.ai; - Personal sites hosted at
*.itsmysite.aiand any custom domains attached to those sites; - Our dashboard, admin tooling, and support channels.
1. Who we are
itsmysite is operated by Play or Party Private Limited, incorporated in India with its registered office at 6-181, SLNS Colony, Balapur X Road, Meerpet, Saroornagar, Hyderabad, Telangana 500097, India. We are the "Data Fiduciary" under India's Digital Personal Data Protection Act, 2023 ("DPDP Act"), the "Controller" under the EU and UK General Data Protection Regulation ("GDPR"), and the "Business" under U.S. state privacy laws for the personal information processed through the Service.
You can reach us at:
- General privacy enquiries: privacy@playorparty.com
- Grievance Officer (India, under the IT Rules, 2021 and DPDP Act): Raghunath Reddy Bokka, grievance@playorparty.com
2. What we collect
2.1 Information you provide
| Category | What it is |
|---|---|
| Account information | Your email address and (where the identity provider returns it) display name. We do not receive your password. |
| Acceptance records | The version of the Terms and this policy you accepted and when, your one-time confirmation that you are 18 or older, and the acknowledgements you tick before checkout (that the membership renews yearly and that you want it to start immediately). |
| Site content | Anything you ask your AI assistant to publish on your site: text, images, layout, code, fonts, uploaded assets. Public by definition because it is served on the public internet at your subdomain or custom domain, where anyone, including search engines and third-party crawlers, can read it. |
| Profile information | Structured data about you generated by your AI assistant from your conversation and site content: tagline, bio, location, services you offer, what you are looking for, interests, contact preferences. You can review and edit this any time. |
| Update notes | Short notes you post about what changed on your site. Public: served on your site's updates page and feeds. |
| Follows | The sites (or external feeds) you choose to follow, a label for each, and when you last read your updates. Private to you: never shown to the site you follow or to anyone else. |
| Booking link | If you connect a booking section, your Cal.com or Calendly handle and which provider it belongs to. |
| Custom domain information | If you add a custom domain on the Two-Buck-Fifty plan, the domain name and DNS records you configure. |
| Payment information | Collected and stored by Paddle, our merchant of record (see Section 4). We receive a subscription record (status, plan, period end), but not your card number or bank account details. |
| Cancellation feedback | If you cancel and choose to tell us why: the reason you pick and any free-text comment. Optional; you can skip it. |
| Support communications | If you email support@playorparty.com or reach us through another channel, the content of those communications. |
2.2 Information we collect automatically
| Category | What it is |
|---|---|
| Connector usage | Which tools you call (e.g., create_site, find_people), when, and whether they succeeded. We do not log the contents of your AI-assistant conversations — those stay between you and your AI assistant. |
| Site analytics (aggregate) | For each visit to your site: the site, the page path, the visitor's country (derived at the network edge), the referring page, and the device type (desktop, mobile or tablet, derived from the browser's user-agent string). We never store visitor IP addresses in analytics and we set no cookies on visitors. |
| Discovery interactions | When you use find_people, we keep a match record: your query text, which profiles were shown to you, the one-sentence rationale for each, and whether you asked to see a match's contact details. Used to run the feature, improve match quality, and detect abuse (scraping, harvesting). |
| Technical logs | Request IDs, timestamps, error codes, IP address, user agent. Retained for security and debugging on the schedule in Section 7. |
| Vector embeddings | A numerical representation of your profile, generated by an embedding model, used to power the discovery feature. Generated only if you opt in to discovery. |
| Content-safety records | When you publish, the categories our safety classifier assigns to your page text, and for each uploaded image a hash of the file with the classifier's verdict, so we don't rescan the same image twice. |
2.3 Information we do NOT collect
- We do not collect, see, or store your AI-assistant conversation history. We only see the specific tool calls your AI assistant makes to our connector and their arguments.
- We do not set tracking cookies on visitor browsers when they visit your
*.itsmysite.aisite, unless you have explicitly added a feature that requires them. - We do not sell your personal information. We have no sales or sharing of personal information in the legal sense used by U.S. state privacy laws.
- We do not use your personal information, your site content, or your profile data to train any AI model. The AI models we run ourselves (currently Cloudflare Workers AI) operate on your data only for the purpose of providing the Service; the AI assistant you connect through (such as Claude or ChatGPT) processes your conversation under its own provider's privacy policy.
3. Discovery: how matchmaking works
This is the part of the Service that processes the most user-identifying information beyond what you have made public, so it gets its own section.
If you opt in to discovery, we generate a vector embedding from your profile (tagline, bio, services, looking-for, interests). This embedding is stored alongside your site_id in our vector database. Until you opt in, no embedding is generated or stored.
When another user issues a discovery query like "find me a wedding photographer in Tampa," we:
- Embed their query;
- Search profile embeddings for similarity, filtered by location and other criteria;
- (Optionally) re-rank the top results with an LLM that returns a one-sentence rationale per match;
- Return matches to the searching user.
You control your discoverability
- By default, new profiles are not discoverable and contact info is hidden. Discovery is fully opt-in.
- You can opt in by asking your AI assistant to make your profile discoverable (the
set_profile_visibilitytool). You can opt back out at any time, and your vector is removed from the discovery index when you do. - You can separately opt in to make your contact email visible to people who match against you.
- Even when discoverable, we do not reveal contact information in bulk. Searching users must request specific match details one at a time, and must themselves have a deployed site (a reciprocity / anti-leech rule).
You can ask your AI assistant to show you exactly what your profile looks like to others.
4. Payment information and Paddle
Paid subscriptions are sold through our merchant of record, Paddle.com Market Limited ("Paddle"). Paddle is the controller of your payment information for the payment leg of your purchase. Paddle's collection and use of your information is governed by Paddle's Privacy Policy.
We receive from Paddle only the information needed to provision and manage your subscription: subscription identifier, plan, status, current-period end, billing email, country (for tax reasons), and the last four digits of your card if you ask us to identify the source of a charge. We also attach to each Paddle transaction a record of the acknowledgements you ticked before checkout and the Terms version in force at the time.
5. How we use your information
| Purpose | Categories used | Legal basis (GDPR / UK GDPR) | Lawful purpose (DPDP) |
|---|---|---|---|
| Operate the Service: deploy your site, store your profile, route traffic, serve visitors | Account info, site content, profile, booking link, custom domain, technical logs | Performance of contract | Specified lawful purpose (signup terms) |
| Publish your update notes and show them to people who follow your site | Update notes, follows | Performance of contract | Specified lawful purpose |
| Make you discoverable to other users (only if you opt in) | Profile, embeddings | Consent | Consent |
| Process payments and manage subscriptions | Account info, subscription record from Paddle | Performance of contract | Specified lawful purpose |
| Keep proof of your agreement to the Terms and of your pre-checkout acknowledgements | Acceptance records | Legal obligation / legitimate interest | Legal obligation |
| Detect abuse, fraud, illegal content; enforce Acceptable Use | All categories, content-safety records | Legitimate interest | Specified lawful purpose; legitimate use |
| Comply with legal obligations (e.g., DMCA, IT Act takedowns, court orders, tax records) | As required | Legal obligation | Legal obligation |
| Respond to your support requests | Account info, support communications | Performance of contract | Specified lawful purpose |
| Show you service notices (site suspended, terms changing, membership lapsed) in your dashboard; Paddle emails receipts and payment-failure notices on our behalf | Account info, subscription record | Legitimate interest / contract | Specified lawful purpose |
| Understand why members cancel | Cancellation feedback (optional) | Consent | Consent |
| Improve match quality using aggregated, anonymised usage patterns | Discovery interactions (anonymised) | Legitimate interest | Specified lawful purpose |
| Improve and secure the Service generally | Technical logs | Legitimate interest | Specified lawful purpose |
We do not use your data for advertising. We do not share it with advertisers. We do not engage in cross-context behavioural advertising.
Automated decision-making
The discovery feature uses automated processing (vector similarity + optional LLM re-ranking) to surface matches. These do not produce legal or similarly significant effects on you in the GDPR Article 22 sense. Our content-safety classifiers can block a publish or suspend a site automatically on a high-confidence match; a person reviews every such decision on request, and the Terms (Section 4) explain how to contest it. We do not use automated processing to make decisions about your eligibility for any tier or anything else with a legal or similarly significant effect.
6. Who we share with
We share your information only with:
- Cloudflare — our infrastructure provider, hosting the Service and your site (Workers, R2, D1, Vectorize, KV, Queues, Analytics Engine, Browser Rendering, Workers AI). Acts as our processor (GDPR / UK GDPR) / data processor (DPDP).
- Paddle — our merchant of record for paid subscriptions (see Section 4). Acts as an independent controller for the payment leg.
- Your identity provider — the provider you choose to sign in with (currently Google; Microsoft and Apple are supported by our infrastructure and may be enabled). You authenticate with it directly over OpenID Connect and it returns your email address, a stable account identifier, and your display name to us. It handles that sign-in under its own privacy policy and your relationship with it — not as our subprocessor. We never receive your password.
- Your AI assistant provider — the maker of the MCP-compatible AI assistant you connect through (for example, Anthropic if you use Claude, or OpenAI if you use ChatGPT). You interact with that assistant directly; the provider does not receive data from us beyond the natural flow of tool calls you initiate through the assistant. We list this for transparency. The provider's handling of your conversation is governed by its own privacy policy.
- AI inference providers (pass-through). When you use Service features that invoke an AI model on your data — for example, profile inference, content safety classification, vector embeddings, or LLM re-ranking of discovery results — your inputs are transmitted to the relevant AI provider (currently Cloudflare Workers AI) for the sole purpose of generating the response and are not retained by that provider for training, profiling, or other purposes beyond producing the response. Cloudflare's processing in this capacity is covered by its DPA.
- YouTube (walkthrough video embeds) — our marketing site and dashboard embed two short setup walkthroughs hosted on YouTube, using YouTube's privacy-enhanced
youtube-nocookie.complayer. No cookies are set and no viewing data is sent to Google unless you press play; loading the page does reveal your IP address to Google, as any embedded resource would. Playback is governed by Google's privacy policy. YouTube is not our subprocessor; we list it for transparency. - Cal.com or Calendly (third-party booking embed) — if you connect a booking link, your site embeds that provider's booking widget. Visitors who book interact with the provider directly: the details they enter (name, email, meeting information) go to the provider under your account and its privacy policy (Cal.com, Calendly) — we never receive or store them. Neither is our subprocessor; we list them for transparency because the embed appears on sites we host.
- Other users — but only the specific information you have made discoverable (only when they query for someone matching you, and only via the Service; we do not expose bulk lists), and your public update notes when they follow your site.
- Anyone on the internet — your published site and its update notes, which are public by design.
- Professional advisers (lawyers, accountants, auditors) — under confidentiality.
- Law enforcement — only if compelled by valid legal process, or if we believe in good faith disclosure is necessary to prevent imminent harm. We will notify you unless legally prohibited.
- A successor entity — if we are acquired, merge, sell substantially all of our assets, or undergo a similar corporate event. Your data would transfer with the same protections.
A current list of subprocessors, their location, and what they process is maintained at SUBPROCESSORS.md. We update this list when subprocessors change, and we notify you with an in-product notice of material changes.
7. How long we keep it
| Data | Retention |
|---|---|
| Account information and acceptance records | While your account exists. Deleted when we close your account, within 30 days of your request. A billing-record copy of your checkout acknowledgements is kept with the subscription records below. |
| Site content (HTML/CSS/JS/assets) | While the site exists. When you delete a site, its files are deleted immediately and the copies in our rolling backups age out within 30 days. A site suspended because your membership lapsed is kept for 90 days so you can resubscribe or export, then permanently deleted. |
| Profile and embeddings | While your account is active. The embedding is created only when you opt in to discovery and is removed from the index when you opt out. |
| Discovery match records (query text, matches shown, rationale, contact reveals) | 1 year from the search, then deleted automatically; earlier if you close your account. |
| Update notes | While the site exists; deleted with the site. |
| Follows | Until you unfollow or close your account. |
| Booking link, custom domain | Until you disconnect or remove it, or the site is deleted. |
| Cancellation feedback | While your account exists. |
| Subscription / billing records (your side of what Paddle sends) | While account is active, plus 7 years after closure for tax / statutory compliance. |
| Content-safety records | Text classifications: with the site version they relate to. Image hashes and verdicts: while the image exists; the hash alone (which does not identify you) may be kept to avoid rescanning. |
| Technical / security logs | Up to 30 days. |
| Audit logs (who did what, when — used for security, disputes and legal compliance) | For as long as needed for those purposes, and longer if subject to a litigation hold. Entries about a deleted account keep only the account identifier. |
| Backups | 30 days rolling. |
| Grievance / complaint records | 7 years (DPDP and IT Rules). |
When you close your account, we remove all of the above on the schedule shown within 30 days, except records we are legally required to retain (tax, audit, grievance).
8. Where your data lives, and cross-border transfers
We are based in India. Your data is processed and stored predominantly on the Cloudflare global network and in Cloudflare services located across multiple regions. The Cloudflare network is designed for global redundancy; specific data-centre locations vary.
Our subprocessors are based in India, the EU, the UK, and the United States (see SUBPROCESSORS.md).
If you are in the EU, UK, or Switzerland, your personal data may be transferred to countries outside the EEA / UK that have not been deemed to have an "adequate" level of data protection. Where this happens, the transfer is protected by:
- Standard Contractual Clauses approved by the European Commission (or, for UK transfers, the UK Addendum / IDTA);
- For transfers to Cloudflare specifically, Cloudflare's Data Processing Addendum incorporating the SCCs and additional technical and organisational measures.
A copy of the relevant clauses is available on request from privacy@playorparty.com.
If you are in India, the DPDP Act permits cross-border transfers except to countries notified by the Central Government as restricted (no such restrictions are in force at the date of this policy).
9. Your rights
Depending on where you live, you have some or all of these rights. To exercise any of them, email privacy@playorparty.com or use the in-product tools mentioned below. We respond within 30 days (sometimes 45, or 90 in complex cases, with notice).
9.1 Rights under the DPDP Act (India)
If you are in India, you have the right to:
- Access the personal data we process about you and a summary of how we process it.
- Correct inaccurate, incomplete, or out-of-date personal data.
- Erase personal data that is no longer needed for the purpose for which it was collected (subject to legal-retention obligations).
- Grievance redressal — raise a grievance with our Grievance Officer, and if you are not satisfied with the outcome, complain to the Data Protection Board of India.
- Nominate a person to exercise these rights on your behalf in the event of your death or incapacity.
You also have the right to withdraw consent at any time where processing is based on consent, as easily as you gave it (for discovery, by asking your assistant to make you not discoverable).
9.2 Rights under the GDPR / UK GDPR (EU, UK, Switzerland)
You have the right to:
- Access — get a copy of your data;
- Rectification — correct inaccurate data;
- Erasure ("right to be forgotten") — have your data deleted in defined circumstances;
- Restriction — limit how we process your data while a dispute is resolved;
- Portability — receive your data in a portable, machine-readable format and have it transmitted to another controller;
- Object — to processing based on legitimate interest, including profiling;
- Withdraw consent — at any time, for processing based on consent;
- Lodge a complaint with your local supervisory authority (EU: your national DPA; UK: the Information Commissioner's Office at https://ico.org.uk).
9.3 Rights under U.S. state privacy laws (California, Colorado, Virginia, and similar)
Depending on the state, you have the right to:
- Know what categories of personal information we have collected, the sources, the purposes, and the categories of recipients;
- Access a copy of your personal information;
- Correct inaccurate personal information;
- Delete your personal information (subject to exceptions);
- Opt-out of sale or sharing for cross-context behavioural advertising — we do not sell or share personal information in this sense, so there is nothing to opt out of. Because of that, a Global Privacy Control signal from your browser requires no action from us; we treat it as confirming a preference we already respect;
- Limit the use of sensitive personal information — we do not use sensitive personal information beyond what is necessary to provide the Service;
- Non-discrimination — we will not deny service, charge different prices, or provide a different quality of service because you exercised a right;
- Appeal — if we deny your request, you may appeal within 60 days of our denial by replying to our response email. We will respond to appeals within 45 days and explain the outcome and your further options (including, in some states, the right to contact your state attorney general).
9.4 How to exercise your rights through your AI assistant
Many actions are available directly through your AI assistant:
- Update your profile:
update_profile - View your profile as others see it:
view_my_profile - Make yourself discoverable or not:
set_profile_visibility - Export your site's files:
list_site_filesandget_site_file - Post or read update notes, follow or unfollow a site:
post_site_update,list_updates,follow_site,unfollow_site - Delete a site:
delete_site - See what sites you have:
list_my_sites
For account-wide deletion, a full export, or anything else, email privacy@playorparty.com.
10. Children
The Service is not directed to children under 18, and we do not knowingly collect personal data from anyone under 18. India's DPDP Act requires verifiable parental consent for processing children's (under-18) personal data, and we do not offer that flow. If you are under 18, do not use the Service. If you believe a child has signed up, contact privacy@playorparty.com and we will delete the account.
11. Security
We use:
- Encryption in transit (TLS) for all traffic to and from the Service;
- Encryption at rest for refresh tokens, secrets, and other sensitive fields in our database;
- Least-privilege API tokens, rotated on a regular schedule;
- Daily JWT signing-key rotation (background cron) with a 7-day overlap so old sessions don't break;
- Automated content scanning for malware, phishing, and known-bad signatures on every save, and AI safety classification on every publish;
- Cloudflare-native error and request logging for diagnosing crashes and bugs (no third-party error-monitoring vendor — logs stay within Cloudflare, our infrastructure subprocessor);
- Regular access review of administrative accounts;
- Standard secure-development practices (typed code, validated inputs, prepared statements / parameterised queries, dependency scanning).
No system is perfectly secure. If we detect a personal-data breach affecting your data, we will notify you and the relevant authority within the time required by applicable law: within 72 hours to the supervisory authority under the GDPR and UK GDPR, and, under the DPDP Act and its Rules, to you and to the Data Protection Board of India without delay, with a detailed report to the Board within 72 hours.
12. Cookies and similar technologies
- The MCP connector does not set cookies — it operates over the MCP protocol using bearer tokens.
- The marketing site at
itsmysite.aiuses no third-party analytics and sets no cookies by default. Strictly necessary cookies may be set if we add a feature that needs one; these don't require consent under EU/UK law. - The dashboard uses a session cookie for authentication. It is strictly necessary and does not require consent. It is scoped to
itsmysite.aiand its subdomains so that, while you are signed in, we can show you your own draft site at its private preview address. That means your browser also sends it when you visit other members'*.itsmysite.aisites; it is HttpOnly, so site owners' code cannot read it, and we use it there only to check whether you are the owner of a draft. - Sites you create at
*.itsmysite.aido not set cookies by default. If you enable a feature that embeds a third-party service — for example, a Cal.com or Calendly booking widget — that service may set its own cookies and collect information from your visitors (such as name, email, and meeting details for a booking) under its own privacy policy. We add embeds only at your direction, and you are responsible for any consent obligation those features create vis-à-vis your visitors.
We do not use cookies for advertising or for cross-context behavioural tracking.
13. Changes to this policy
We post material changes at itsmysite.ai/privacy with a new "Last updated" date and the date they take effect, at least 30 days ahead for anyone who accepted an earlier version (or sooner if required by law). During that time you'll see a notice in your dashboard; once the new version is in force we ask you to accept it the next time you sign in or publish. Prior versions are available on request.
14. Contact and complaints
- General privacy questions: privacy@playorparty.com
- Grievance Officer (India): grievance@playorparty.com
- Postal address: Play or Party Private Limited, 6-181, SLNS Colony, Balapur X Road, Meerpet, Saroornagar, Hyderabad, Telangana 500097, India
If you have unresolved concerns:
- EU residents: contact your national data protection authority.
- UK residents: contact the Information Commissioner's Office (https://ico.org.uk).
- India residents: after exhausting the grievance redressal mechanism above, contact the Data Protection Board of India.
- U.S. state residents: contact your state's attorney general.
We will always prefer to resolve issues directly, so please give us a chance to make it right first.