Privacy Policy
This page explains what TripSpark collects today on the public beta surface, how that data is used, what stays in your browser, what leaves the product when you click out, and how to exercise your privacy rights.
Who controls your data
The TripSpark beta is operated by TripSpark via snippetci.com.
Formal notices and support: hello@snippetci.com
Mailing instructions available on request for privacy, legal, or supplier matters.
United States
Privacy and support contact: hello@snippetci.com
TripSpark does not publish a standalone public mailing address on this beta surface yet. For privacy requests, legal notices, or supplier questions, email hello@snippetci.com and we will provide the correct handling path.
What this policy covers
This policy covers TripSpark’s public website, discovery flows, waitlist and account-status forms, saved-trip shortlist features, cookie settings, and outbound handoffs to third-party travel, stay, and event suppliers.
Data categories we collect
- Email address submitted through waitlist or account-status forms.
- Optional name.
- Optional planning or product-feedback notes.
- Optional beta-call interest and optional marketing/beta-updates consent.
- Trip-planning context such as origin, month, budget, interests, use case, community source, and visible result count.
- Browser-stored saved trips, shortlist notes, consent settings, UTM parameters, and referrer context when those categories are enabled.
- Technical and request metadata needed for security, rate limiting, and basic site operations.
How we use data
- Administer the waitlist and future-access queue.
- Handle account-status checks and support follow-up.
- Research which planning flows, trip formats, and acquisition channels matter during the beta.
- Provide shortlist functionality, saved-trip utilities, and consent preferences in your browser.
- Send optional TripSpark beta updates, product news, or access notices when you have opted in or when an email is operationally necessary.
- Protect the service against abuse, fraud, and reliability issues.
Service providers and recipients
| Service | Purpose | What may be processed | Basis |
|---|---|---|---|
| Vercel | Hosting, CDN, runtime infrastructure, and request delivery for the TripSpark site. | IP address, request headers, user-agent, and operational logs needed to serve the site securely. | Operational / essential |
| PostHog | Product analytics and attribution only when you enable Analytics / Attribution cookies. | Page views, route context, referral / UTM parameters, and on-site interaction events tied to the current browser. | Consent-based |
| Wikimedia Commons | Third-party destination or event imagery loaded only after you enable Third-party media. | Your browser requests the selected image asset directly from the media host. | Consent-based |
| Google Flights, Google Search, Booking.com, and other supplier or ticketing destinations | User-initiated click-outs for live pricing, booking, or event lookup. | The destination page receives the URL parameters and request metadata normally sent when you click a link out of TripSpark. | User-initiated |
| TripSpark waitlist and support email handling | Operational replies, waitlist coordination, and optional beta-update outreach when you explicitly opt in. | Email address, optional name, consent state, and the message or waitlist context you submitted. | Operational or consent-based |
When you click out to a third-party supplier, that supplier becomes independently responsible for its own pricing, inventory, booking terms, and privacy practices.
As of June 24, 2026, the public beta does not enable a separate bulk-email marketing vendor on this surface. Operational replies and waitlist support currently route through hello@snippetci.com, and this page will be updated before a dedicated email delivery vendor is enabled.
Automated suggestions and estimate transparency
Current recommendation, ranking, and narrative outputs on this beta are rules-based product outputs built from planning inputs and source data. They are not individualized human travel advice or live booking offers.
TripSpark also shows estimated trip suggestions and outbound supplier searches. Final prices, inventory, taxes, fees, booking terms, and event availability are determined by the supplier at click-out.
Retention schedule
| Data type | Retention approach |
|---|---|
| Waitlist records | Up to 18 months after the most recent signup, update, or confirmed inactivity, unless a longer retention period is required by law or to resolve abuse/security issues. |
| Product-feedback notes and beta-call interest | Up to 12 months after collection unless you ask us to delete them sooner or they must be retained longer for legal reasons. |
| Support or access-status correspondence | Up to 24 months after the last support interaction to document requests and resolve follow-up issues. |
| Browser-stored saved trips, notes, and consent settings | Until you delete them, revoke consent, clear your browser storage, or TripSpark removes them after a consent change. |
| Analytics / attribution data | Kept only while analytics consent remains valid and no longer than reasonably needed for beta measurement. |
Your rights and choices
| Right | What it means here |
|---|---|
| Access | Ask what personal data TripSpark holds about you and receive a copy where applicable. |
| Correction | Ask us to correct inaccurate or incomplete information. |
| Deletion | Ask us to delete information, subject to legal, security, or recordkeeping exceptions. |
| Portability | Request a portable copy of data you provided to us where the law gives that right. |
| Objection / withdrawal of consent | Withdraw marketing consent, object to certain processing, or reject optional browser storage. |
| Appeal / escalation | If you think a request was mishandled, reply to the response or email us again for escalation review. |
To make a request, email hello@snippetci.com from or about the address you used with TripSpark.
Depending on where you live, additional privacy or consumer-data rights may apply, including rights provided by certain U.S. state privacy laws or other local rules.
Cross-border transfers
TripSpark and its service providers may process information in the United States and in other countries where infrastructure or vendors operate. When cross-border transfers occur, TripSpark relies on contractual, organizational, and technical safeguards that are reasonable for the beta stage and applicable processing role.
Sensitive information warning
Please do not submit sensitive personal, financial, or health information through TripSpark’s open text fields. Those fields are intended for trip-planning context and product feedback only.
Cookies and browser storage
Essential storage supports core functionality and your consent settings. Optional categories cover saved trips, shortlist notes, attribution context, analytics, and third-party media. You can reject non-essential storage or reopen cookie settings at any time.
Children's privacy
TripSpark is not directed to children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child submitted personal data, contact us so we can review and delete it if appropriate.
Last updated
June 24, 2026