Skip to main content
Private beta

Privacy Policy

Last updated October 19, 2026

We built Plannyfy so your budget stays yours. This is a plain-language account of what we collect, who sees it, and how you stay in control.

1. Who we are

Plannyfy runs plannyfy.com, a marketplace where travelers describe a trip and vendors compete to price it. This policy explains what we collect, why, who can see it, and what you can ask us to do. It applies to the private beta.

2. What we collect

  • Request for early access: your name, email, whether you are a traveler or a vendor, your business name if you are a vendor, an optional note, and the optional tag from the link you came through.
  • Your account: the name and verified email from the Google account you sign in with, and the role we gave you. We do not receive your Google password.
  • Your trips (travelers): destinations, dates, number of travelers, the items in your trip and what you want for each, your travel style and must-haves, and your private ideal and maximum budget and per-item targets.
  • Your bids (vendors): your business name, prices, inclusions, notes, your private floor price, your drafts and changes, availability rules, and any reason you give for withdrawing.
  • Payments and payouts: payment and payout credentials are handled by Stripe. Plannyfy stores tokenized payment method references (brand, last 4 digits, expiry), escrow payment intents, refund records, and Stripe Connect onboarding status—never full card numbers or raw bank credentials.
  • Anonymous usage: page views and product events (for example “trip published”). These contain no name, email, budget or free text. See “Analytics” below.
  • Technical data: our hosting provider keeps standard server logs, which include network addresses, for security and reliability.

3. How we use it

  • To let you in (we review every request and match invitations to your Google email) and to run your account.
  • To draft your trip and match it with vendors, work out the best price and best value offers, and tell you when time is running out.
  • To show vendors what they need to bid, and nothing more (see “Who sees what”).
  • To keep the service safe, prevent abuse, and fix problems.
  • To understand, in aggregate, whether Plannyfy is working, so we can improve it.
  • To contact you about the beta and your account. We do not send marketing you did not ask for, and we do not sell your data.

4. Who sees what

Your budget is private. Vendors never see your ideal or maximum budget, your per-item targets, or other vendors' prices.

Vendors do see your trip so they can price it: destination, dates, number of travelers, the items you want, your requirements, and a broad label for what matters most to you (price, value or balanced). While bidding is open, they do not see your name or email, and pre-lock Q&A messages automatically redact email addresses, phone numbers, links and social handles. Once you lock in and fund a winning package in escrow, direct contact details and voucher codes are shared between you and your winning vendors so they can fulfill your booking.

You never see a vendor's private floor price or how other vendors price their bids beyond the offers shown to you.

Plannyfy administrators can see accounts, trips and bids to run and protect the service. Access is limited to approved administrators.

5. AI

To draft a trip or assist with portfolio imports, we send the prompt or rate-sheet text you enter (destination, dates, party size, style, must-haves and your ideal budget) to Google's Vertex AI—or, if you configure your own Bring-Your-Own-Key (BYOK) AI provider in Settings, to your chosen provider using your encrypted key. We do not send your name or email. AI output can be wrong, so always check it. Prices in a draft are estimates, not quotes.

6. Service providers

We use Google Cloud and Firebase to host the service, store data in the United States, sign you in with Google, and run the default AI described above. We use Stripe to process customer escrow payments, split payments, refunds, and Stripe Connect vendor payouts. Destination photos are loaded from Unsplash, which means Unsplash's servers see the request your browser makes for each image. We do not give service providers permission to use your data for their own purposes beyond running the service for us.

We may disclose information if the law requires it, or to protect people and the service from fraud or harm.

7. Cookies and analytics

When you are signed in we set one cookie that keeps you signed in. It is needed for the service to work. The public demo sets a similar cookie for the demo session. We do not use advertising cookies.

We also use Google Analytics to understand how the site is used. It sets its own cookies (named _ga) in your browser. It is not loaded on admin pages, in the demo, or when your browser sends Do Not Track. Admins can mark their own browser as internal, which sets one small cookie (pfy_internal) so their visits are not counted.

Our own first-party analytics set no cookies. A visitor to a public page is counted using a code made from their network address and browser that changes every day, so we can count unique visitors per day but cannot follow anyone from one day to the next, and we do not store the address. Signed-in activity is recorded against a one-way code, not your identity. We respect Do Not Track and Global Privacy Control, and we ignore automated traffic. Analytics events are deleted after about 400 days.

8. How long we keep things

  • Account, trips and bids: while your account is active, and for a reasonable time afterwards for record keeping and disputes.
  • Access requests and invitations: as long as needed to run the beta.
  • Anonymous analytics events: about 400 days.
  • You can ask us to delete your account and data at any time (see “Your choices”). We may keep what we must by law or to resolve a dispute.

9. Your choices

You can ask us to show you the data we hold about you, correct it, or delete it, and you can ask us to stop using your details. Write to privacy@plannyfy.com from the email on your account and we will respond. Depending on where you live, you may have additional rights under local law, and you may be able to complain to your data protection authority.

10. Security

Data is encrypted in transit. The database accepts no direct connections from browsers, only from our servers. Budgets and private floor prices are kept out of everything shown to the other side. No system is perfectly secure, and we will tell affected people if something goes wrong that puts their data at risk.

11. Children

Plannyfy is for people aged 18 and over. We do not knowingly collect data from children.

12. Changes to this policy

We may update this policy as the beta grows, for example when we add payments. We will change the date at the top and, for material changes, tell you by email or in the product.

Questions? Write to privacy@plannyfy.com. See also our Terms of Use.

Privacy Policy · Plannyfy