Legal
Search tracking without turning people into profiles.
LetsFG is designed so that ordinary travel searches are tied to anonymous sessions, not named accounts. This policy explains what personal data we process, the legal basis for each use, what happens to your details when we book a flight or a hotel for you, which AI models and companies are involved, who we share data with, and the rights you can exercise against us.
1. Who we are and who controls your data
LetsFG is the public brand operated by Mental Balance Sp. z o.o., VAT PL6751772427, with its registered address at Szafera 1/14, 31-543 Krakow, Lesser Poland Voivodeship, Poland. For the purposes of the EU General Data Protection Regulation (GDPR), the UK GDPR, and equivalent laws, Mental Balance Sp. z o.o. is the controller of the personal data processed through letsfg.co, the LetsFG API and MCP server, the LetsFG connectors for AI assistants, and related service channels (together, the "Service").
We have not appointed a Data Protection Officer, because we are not required to. Privacy questions, requests, and complaints go to contact@letsfg.co, or by post to the address above.
If you are in the European Economic Area, you also have the right to complain to a supervisory authority. Ours is the Polish President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland — uodo.gov.pl), and you may also complain to the authority where you live or work.
2. How LetsFG works: search, assistants, and booking on your behalf
LetsFG does not operate like a passive list of links. When you submit a search, we activate a software agent that acts on your behalf and according to your instructions. That agent uses your travel requirements to query airlines, online travel agencies, booking sites, and hotel suppliers, compare options, and surface the results that best match your criteria.
Because the Service is acting for you, we must process the search instructions you provide and the technical data needed to run that search across third-party supplier systems. The point of that processing is to help you choose the option that best fits your requirements, not to build an advertising profile around you.
When you ask us to, that agent also completes the booking for you, directly with the airline, booking site, or hotel supplier, instead of pointing you to their site. Flights and hotels both work this way today, on the website and through a connected AI assistant or the API. Section 6 explains in detail what an agent-completed booking means for your data, because it is the part of the Service that involves the most sensitive information, and section 7 lists who receives it.
3. Personal data we collect
3.1 Information you give us
- Search instructions. Origin, destination, dates, passenger counts, cabin and hotel preferences, filters, budget, and any free-text description of the trip you want — whether you type it on the website or say it to a connected AI assistant.
- Account data. Your email address, confirmed with a one-time code sent to that address — LetsFG accounts have no password, so we never hold one. An account created by connecting an AI assistant starts with no email at all; we learn your email when you add a card or make a booking, because a booking needs an inbox to confirm to.
- Traveller and identity-document data. For every traveller on a booking, and for saved traveller details: legal given and family names, date of birth, gender, nationality, phone number, email address, postal or billing address, and passport number, expiry date, issuing country, and issue date. A passport is required for every booking made through the API, and for a booking made through an assistant when the supplier asks for one at its checkout, because some suppliers will not issue a ticket without one. Known-traveller and airline loyalty numbers are collected where you give them. For a buyer in the United States, we also record their state, taken from the address on the booking.
- Travel companions. If you add other travellers to a trip, their name, contact details, and the traveller and passport details above. You may only give us another person's details if you are entitled to, and they need to know how we use them (this policy).
- Preferences. Travel preferences you save (for example seating, airlines, or hotel wishes), on the website or through an assistant.
- Payment-related data. The card brand, last four digits, expiry month and year, and issuing country of a card you add; the customer and payment-method identifiers our payment provider returns; and the status and amounts of holds, charges, refunds, and disputes. We do not receive or store your full card number, card security code, or authentication credentials — those are entered on the payment provider's own hosted fields.
- Booking approvals and answers. When you approve a booking by email, the approval and its time. When a booking pauses with a question (a price change, a seat or bag choice, a detail a supplier asks for), your answer.
- Booking consent records. Each time you agree to a purchase — pressing "Confirm & pay" on letsfg.co, pressing Approve in our booking email, booking through the API, or saving a card for later bookings — we keep a record of that consent: when it was given, the price and trip it was for, the travellers it named (passport numbers masked), the terms sentence you were shown and the version of these documents, and the IP address, approximate country, browser user-agent, and language setting of the device that gave it.
- Contact channels for alerts. An email address, a web-push subscription, or a Telegram identifier, where you ask us to send price alerts, flight-status alerts, or other service messages.
- Support and correspondence. Anything you send us by email or through an in-product survey or feedback prompt, including the content of your message.
- Developer and API data. If you use the LetsFG developer API or the MCP server directly: your account email, API keys and access tokens, plan and billing details, and per-request usage records.
3.2 Information collected automatically
- Session and device data. Cookies and local storage, session identifiers, user-agent string, language and currency preference, approximate location derived from your IP address, and request timestamps.
- Network and security data. IP address and IP-derived signals, rate-limit counters, and bot-detection signals, used for routing, security, and abuse prevention.
- Product telemetry. Which sources were queried for your search, how long each took, which results were shown and viewed, which filters and sorts you applied, which actions you took, and — for a booking — its progress and outcome.
- Analytics data. Page views, navigation paths, and aggregate funnel measurement through Google Analytics 4 and our own search-session analytics pipeline.
We intentionally structure ordinary searches so that we do not need your name, passenger identity, or a permanent account in order to show results. We still process the technical identifiers needed to operate and secure the site, but they exist to keep the Service working rather than to identify you by name.
3.3 Information we receive from others
- AI assistant platforms. When you use LetsFG through a connected assistant, its provider sends us the requests the assistant makes on your behalf, with the details you gave it.
- Travel suppliers. Airlines, hotel suppliers, online travel agencies and booking systems return booking references, confirmation numbers, ticket status, fare rules, price changes, and flight-status updates relating to a booking made for you.
- Payment providers. Our payment provider confirms the outcome of a hold, charge, or refund and returns the limited card and status data described above, including for accounting, tax, support, chargeback, and anti-fraud purposes.
- Security providers. Cloudflare returns a verdict on whether a request looks automated.
- Referral sources. Where you arrive through a partner, creator, affiliate, or campaign link, we receive the referrer and campaign identifiers attached to that link.
We do not buy personal data from data brokers, and we do not enrich your profile from social media or public-records sources.
3.4 One customer across your devices and assistants
From 2 November 2026, we keep one customer record for each person who uses LetsFG, so that your LetsFG accounts on different devices and assistants — a connector in Claude and the website, say, or two assistants — count as one customer rather than several. Two accounts become one customer when they use the same email address that has been verified (with a one-time code, or by pressing Approve in our booking email), or pay with the same card or Revolut Pay account. A card or phone never joins two people who each verified their own email. A website visitor who has not signed in is never given a customer record; their searches stay anonymous sessions.
Against that record we keep:
- When we first saw you, and how you came. The date of your first visit or connection, and whether you came through an AI assistant (and which one), a trip link someone shared with you, a creator or developer link, or the website.
- Your searches. When each search was made, whether it was for flights or a hotel, whether we answered it from results we already held, and whether it was started by a person or automatically — for example by a price watch you set up re-checking a price.
- Your assistant's requests. Which LetsFG tool your assistant used, how it ended, how long it took, and which assistant or app sent it.
- Price watches, shared trip links, and bookings. The watches you set, the trip links you share and open, and each booking with the amounts paid and refunded.
- Your country. For a search on the website, the country of your IP address (or, failing that, your browser's language setting). For a search through an assistant or the API we cannot tell where you are, and record it as unknown.
We use the record to count customers rather than accounts: how many people use LetsFG, how long it takes before a first booking, which assistants and links bring people, what serving one customer costs us in searches and AI processing, and to credit the person whose shared link brought someone to LetsFG within 30 days. The legal basis is our legitimate interest in understanding and running the Service (Art. 6(1)(f)). The record is not used to rank results or to set a price, it is not used for advertising, and it is not sold.
The links between accounts are kept as coded keys made with a secret only we hold — never the email address, card, or phone number themselves — and the record holds no name, date of birth, or passport detail. You can ask which of your accounts we have linked, ask us to undo a link, or object to the linking altogether (section 11); after an objection we stop linking your accounts.
4. Cookies and tracking technologies
We use cookies, local storage, and similar technologies to keep the Service working, remember your preferences, keep a checkout attached to the right search, recognise a connected assistant account when you reconnect, measure usage, and detect automated abuse. The main categories are:
| Key | Type | Purpose | Category |
|---|---|---|---|
LETSFG_LOCALE | Cookie | Remembers the language you chose, including for these legal pages. | Essential |
NEXT_LOCALE | Cookie | Routes you to the right language version of a page. | Essential |
LETSFG_CURRENCY | Cookie | Remembers the currency prices are displayed in. | Essential |
__lfg_ok | Cookie (signed) | Records that your browser passed the bot check, so a search can start. It also keys the per-browser search limits. | Security |
letsfg_customer_session | Cookie | Keeps you signed in to a LetsFG account after email verification. | Essential |
lfg_connector | Cookie (signed, HTTP-only, 1 year) | When you connect an AI assistant, remembers which LetsFG account that browser approved, so reconnecting lands on the same account rather than creating a new one. | Essential |
lfg_credit | Cookie (signed, HTTP-only) | Records a paid digital service (such as a search credit) you have already bought. | Essential |
letsfg_checkout_cs | Session storage | Ties a checkout session back to the search and offer it belongs to. | Essential |
lfg_result_* | Session and local storage | Holds the results of a search so a reload or a back-navigation does not lose them. | Essential |
letsfg_monitor_id | Session storage | Links a price-monitor or alert subscription to your browser. | Functional |
letsfg_push_pending_sub | Session storage | Holds a pending web-push subscription until you confirm the alert. | Functional |
lfg_ref | Cookie (up to 60 days) | Records the creator, referral, or campaign link you arrived through, so that a hotel booking you make on the website within that time can be attributed to them. | Analytics |
lfg_share | Cookie (signed, 30 days) | From 2 November 2026: remembers which shared trip link brought you to LetsFG, so the person who shared it can be credited (section 3.4). In the EEA, the UK and Switzerland, only after you accept in the cookie banner. | Analytics |
lfg_flight_bought | Cookie (2 years) | Records that this browser has bought a flight with us, so the lower first-flight fee for visitors in the United States (section 6.1) applies only to the first one. | Functional |
lfg_ab | Cookie | Assigns your session to a variant in a product experiment. | Analytics |
lfg_ab_uid | Local storage | A random identifier that keeps your experiment variant stable between visits. | Analytics |
_ga | Cookie | Google Analytics 4 — distinguishes browsers for aggregate usage measurement. In the EEA, the UK and Switzerland, only after you accept. | Analytics |
lfg_consent | Cookie (1 year) | Remembers whether you accepted or declined Google Analytics in the cookie banner. | Essential |
| Cloudflare cookies | Cookie | Set by Cloudflare to distinguish human visitors from automated traffic. | Security |
Names ending in * are families of keys, one per search or per resource. Session storage is cleared when you close the tab; local storage persists until you clear it. Cookies, session storage, and local storage are all storage on your own device, and the controls described below apply to each of them.
Your controls. Every browser lets you block or delete cookies and clear local storage; doing so for the essential keys above will break sign-in, checkout, and saved results. You can opt out of Google Analytics specifically using Google's browser opt-out add-on. We do not currently respond to "Do Not Track" browser signals, because there is no common standard for how to interpret them.
We do not use cookies for advertising, we do not run interest-based advertising or retargeting, and we do not share cookie data with advertising networks.
5. How we use your data, and our legal bases
We process personal data only where we have a valid legal basis under Article 6 GDPR. The table below maps each purpose to its basis.
| What we do | Legal basis |
|---|---|
| Run your search: query suppliers, rank results, and return them to you or to your assistant. | Performance of a contract, or steps taken at your request before entering into one (Art. 6(1)(b)). |
| Create and maintain a LetsFG account, including email verification by one-time code, and recognise a connected assistant account when it reconnects. | Performance of a contract (Art. 6(1)(b)). |
| Ask you to approve a booking by email before any money is held, and record that approval. | Performance of a contract (Art. 6(1)(b)), and our legitimate interest in making sure a booking is really wanted before your card is used (Art. 6(1)(f)). |
| Complete a booking on your behalf: hold the amount on your card, send the traveller, contact, and identity-document details to the seller, and take the money only once the booking is confirmed. | Performance of a contract (Art. 6(1)(b)), and your explicit consent where an element of that data is treated as a special category in your jurisdiction (Art. 9(2)(a)). |
| Use automated tools, including AI services, to run your search and complete your booking. | Performance of a contract (Art. 6(1)(b)). |
| Keep flights and hotels apart at the point of sale — refuse a booking that would combine them, or that follows the other kind within 24 hours — by matching the email, traveller name and date of birth, and card on the two purchases. | Compliance with a legal obligation (Art. 6(1)(c)): not to create a package or a linked travel arrangement under EU package-travel rules without the protections those require. |
| For a buyer in the United States, record their state, taken from the address on the booking, to know which local rules on selling travel apply to the sale. | Compliance with legal obligations (Art. 6(1)(c)), and our legitimate interest in meeting the rules of the places we sell to (Art. 6(1)(f)). |
| Take payment, verify it, issue invoices, and handle refunds, chargebacks, and disputes. | Performance of a contract (Art. 6(1)(b)) and compliance with accounting and tax obligations (Art. 6(1)(c)). |
| Keep a record of each booking consent (section 3.1) as evidence of what you agreed to, for a chargeback, payment dispute, or consumer complaint. | Our legitimate interest in establishing, exercising, or defending legal claims (Art. 6(1)(f)). |
| Send price alerts, flight-status alerts, and other messages you asked for. | Performance of a contract (Art. 6(1)(b)), or your consent where you subscribed without a purchase (Art. 6(1)(a)). |
| Send service and transactional messages about a booking, payment, or support request, including a booking status page. | Performance of a contract (Art. 6(1)(b)). |
| Attribute a hotel booking to the creator or partner whose link you arrived through, and pay them. | Our legitimate interest in running a creator programme (Art. 6(1)(f)). |
| From 2 November 2026, keep one customer record across your accounts, devices, and assistants (section 3.4): to count customers, measure how they find and use LetsFG and what serving them costs, and credit shared links. | Our legitimate interests in understanding and running the Service (Art. 6(1)(f)). |
| Secure the Service: rate limiting, bot detection, fraud investigation, abuse prevention, and operational logging. | Our legitimate interests in protecting the Service, our suppliers, and our users (Art. 6(1)(f)). |
| Measure usage and improve the product, including analytics and product experiments. | Our legitimate interests in understanding and improving the Service (Art. 6(1)(f)). |
| Establish, exercise, or defend legal claims, and respond to lawful requests from authorities. | Our legitimate interests, and compliance with legal obligations (Art. 6(1)(f) and (c)). |
Where we rely on legitimate interests, we have weighed those interests against your rights and freedoms. You can ask us for that assessment, or object to the processing — see section 11.
Where we rely on your consent, you can withdraw it at any time. Withdrawing consent does not affect the lawfulness of processing carried out before you withdrew it.
lfg_consent, for one year. Visitors elsewhere, and our own product-experiment and attribution cookies (lfg_ab, lfg_ab_uid, lfg_ref), run on the legitimate-interest basis described above, and you can block them as described in section 4. We do not use any of them for advertising, for profiling for advertising, or for sale of data.6. Automated processing and booking on your behalf
Three parts of the Service are automated in a way we think you should be told about plainly.
6.1 Ranking and prices
Results are ordered by an automated score built from price, total duration, number of stops, and layover quality. It is applied to the offers returned for your search, not to you — the score does not use your identity, your history, or any profile of you, and how often you have searched never changes a price.
Our service fee can differ slightly by region, because card payments from outside the EEA cost more to process. From time to time we also offer a lower fee on a first booking. The price we show always includes our fee.
6.2 Booking on your behalf
Nothing is booked without your say-so. On the website, you pay at checkout yourself. Through an assistant or the API, a booking starts only after we have emailed the cardholder an "Approve this booking" link and it has been clicked — that email names the flights or the hotel, the price, and the travellers (with the passport number masked). The link lasts 30 minutes. This approval cannot be switched off, and it cannot be given from inside a chat, so nothing an assistant reads or sends can approve a booking for you.
Once approved, we complete the booking with the seller in the traveller's name, using the details that booking requires — depending on the seller, each traveller's legal name, date of birth, gender, nationality, contact details, address, and passport details. We use automated tools, including AI services (section 7), to do this; they process your details only to complete the booking and may not use them to train models. Your card details never go to the seller, and money is only taken from your card once the seller has confirmed the booking.
You supply the traveller details, and you can review, correct, or delete saved details at any time, on the website or by asking your assistant. If the price changes, the seller needs something we do not have, or the booking cannot be completed, we ask you or tell you — we do not guess. If a booking stalls, a person at LetsFG steps in and emails you.
6.3 Keeping flights and hotels apart
We do not sell flights and hotels together. An automated check refuses a booking that would combine the two, or that would follow a completed booking of the other kind within 24 hours, by matching the email address, the traveller's name and date of birth, and the card on the two purchases. Nothing is charged for a refused booking, and you are told why. TheTerms of Service explain the rule.
8. International data transfers
We are established in Poland, and our primary infrastructure is in the European Union, with some services in the United States (AI service providers, Google Analytics, Cloudflare). Travel is global, so carrying out your instruction can require sending data to a supplier anywhere in the world — an airline, booking site, hotel, or hotel supplier in the country you are travelling to or established elsewhere.
Where we transfer personal data out of the EEA or the UK, we rely on one of the following: an adequacy decision covering the destination (including the EU-US Data Privacy Framework where the recipient is certified); the European Commission's Standard Contractual Clauses (with the UK Addendum where the UK GDPR applies), together with any supplementary measures the transfer requires; or, for a booking you asked us to make, Article 49(1)(b) GDPR, because the transfer is necessary to perform the contract you are entering into with that supplier.
You can ask us for details of the safeguards applying to a specific transfer at contact@letsfg.co.
9. How long we keep data
| Data | Retention |
|---|---|
| Live search results | A few hours, so a booking can be made from them; afterwards only the anonymous session and telemetry below. |
| Anonymous search sessions, results, and product telemetry | Up to 24 months, then deleted or aggregated into statistics that no longer identify anyone. |
| The customer record and what it holds (section 3.4) | The record itself, up to 24 months after the last activity on any of your linked accounts; each search, request, and booking entry in it, 24 months after it happened; the record of a shared trip link, 400 days. |
| Security, rate-limit, and abuse-prevention logs | Up to 12 months, or longer where needed for an open investigation or legal claim. |
| Account data (email address and account state) | For as long as the account exists, and up to 12 months after you close it. |
| Connected-assistant access tokens | Until you disconnect the assistant, or we revoke them. |
| Booking approval links | 30 minutes; the approval itself, 30 minutes (the consent record below is kept separately). |
| Booking consent records (time, price and terms accepted, IP address, country, user-agent, language) | 6 years after the booking (the general limitation period for claims under Polish law), longer if a claim or dispute is open. |
| Saved traveller details, companions, and identity-document data | Until you delete or replace them, or close your account. We delete them promptly on request. |
| Booking records (supplier, travellers, dates, price, status, references) | For the duration of the trip, and afterwards for as long as needed to handle refunds, complaints, and claims — normally up to 3 years after the trip, longer if a claim is open. |
| Flight-and-hotel separation records (the keys matched in section 6.3) | As part of the booking record; they only affect a purchase within 24 hours of the sale. |
| Data held by AI service providers during a booking | Used only to run the booking and never to train models. A provider may keep a request for a limited period under its own terms (typically up to 30 days) for abuse and safety monitoring, then deletes it. |
| Payment, invoicing, and accounting records | 5 years from the end of the accounting year, as Polish tax and accounting law requires. |
| Support correspondence and feedback | Up to 24 months from the last message. |
| Cookies and local storage | Until they expire, or you clear them from your browser. |
Where we must keep a record for a legal reason but no longer need it to run the Service, we restrict processing to that purpose rather than continuing to use it. Statistics derived from your data that can no longer identify you may be kept indefinitely.
10. Security
We use technical and organisational measures designed to protect personal data, including encryption in transit, access controls and least-privilege service credentials, secret management, isolated internal services, rate limiting, and bot detection.
Identity and travel-document fields stored under an account — legal name, date of birth, nationality, phone number, passport number, passport expiry and issuing country, known-traveller number, and the billing details attached to a traveller profile — are additionally encrypted at rest with AES-256-GCM at the field level, and decrypted only when a flow you started needs them. The one-time booking setup saved for a connected assistant is encrypted the same way, as one sealed record. If the encryption key is unavailable, those writes fail rather than falling back to storing the data unencrypted. Passport numbers are masked in every email we send and in every assistant reply.
Your card is held by our payment provider, not by us, and your card details never go to the seller. No system is perfectly secure, and security risk is inherent in all internet technologies. We cannot guarantee the security of personal data, and we do not control the security of the supplier systems a booking has to pass through. If a breach affects your personal data and the law requires us to notify you, we will.
11. Your rights and how to use them
Subject to applicable law, you can ask us to:
- Access the personal data we hold about you, and get a copy of it.
- Correct data that is inaccurate or incomplete.
- Delete your data, where we no longer have a valid reason to keep it.
- Restrict processing while a dispute about accuracy or legitimate interests is resolved.
- Port data you gave us to another provider, in a structured, machine-readable format.
- Object to processing based on our legitimate interests, including profiling for those purposes.
- Withdraw consent, where consent is the basis for a particular use.
Some of this you can do yourself: saved traveller details, companions, and preferences can be viewed, changed, and removed on the website, or by asking a connected assistant to edit or remove them; a card can be replaced or removed the same way; and disconnecting LetsFG from an assistant revokes its access.
For anything else, email contact@letsfg.co. We answer within one month, and may extend that by two further months for complex requests, telling you if we do. We may need enough information to verify the request and locate the relevant records — which, for anonymous searches, can mean we are unable to identify any data as yours, in which case we will say so rather than guess. Details already sent to a supplier for a booking you approved are held by that supplier under its own policy; we will tell you which supplier it is so you can exercise your rights there too.
Exercising these rights is free. We may charge a reasonable fee, or decline, only where a request is manifestly unfounded or excessive, and we will explain why.
You can also complain to a supervisory authority, as described in section 1.
12. Notice to United States residents
This section applies if you are a resident of a US state with a comprehensive consumer privacy law, including California, Colorado, Connecticut, Virginia, Texas, Oregon, Montana, and Utah. It supplements the rest of this policy.
In the twelve months before the date at the top of this page, we collected the categories of personal information described in section 3 — identifiers, customer records, commercial information, internet and network activity, approximate geolocation, and, where a booking requires it, government identification numbers. We collected them from the sources and for the business purposes described in sections 3 and 5, and disclosed them to the categories of recipients described in section 7.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under the California Consumer Privacy Act as amended by the CPRA and equivalent state laws. We do not knowingly sell or share the personal information of anyone under 16. We do not use or disclose sensitive personal information for purposes beyond those permitted without an opt-out right — a passport number is collected only to make the booking you asked for, and sent only to the seller of that booking and the service providers that help complete it.
Depending on your state, you may have the right to know, access, correct, delete, and obtain a portable copy of your personal information; to opt out of targeted advertising, sale, or profiling with significant effects (none of which we do); and to appeal a decision we make on your request. Use the same contact route as section 11. We will not discriminate against you for exercising a right. If we deny a request and you want to appeal, reply to our decision and we will reconsider it and give you a written answer.
Nevada residents may direct us not to sell covered information; as stated, we do not sell it. California residents may contact the Complaint Assistance Unit of the California Department of Consumer Affairs, 1625 N. Market Blvd., Suite N112, Sacramento, CA 95834, or by phone at (800) 952-5210.
13. Children
The Service is not directed at children and is not intended for use by anyone under 18. We do not knowingly collect personal data from a child for their own account. An adult booking travel may of course provide a child's traveller details as a passenger or guest on that booking; those details are processed only to make the booking, as described in section 6.
If you believe we have collected personal data from a child in a way the law does not permit, contact us and we will delete it as the law requires.
14. Other sites and services
The Service links out to airline, hotel, and booking sites operated by third parties, and a booking creates a relationship between you and one of them. Those links are not an endorsement, we do not control those sites, and we are not responsible for their practices. Once your details are with a supplier, that supplier's own privacy policy governs what it does with them. The same is true of the AI assistant you may use to reach us. We encourage you to read their policies.
15. Changes to this policy
We may update this policy. When we do, we change the "Last updated" date at the top of this page and post the revised version here. If a change materially affects how we use your personal data, we will give you additional notice — for example by email to an account address, or by a prominent notice in the product — before it takes effect, where the law requires it.
16. How to contact us
Privacy questions, requests, and complaints: contact@letsfg.co, or by post to Mental Balance Sp. z o.o., Szafera 1/14, 31-543 Krakow, Lesser Poland Voivodeship, Poland.
The rules for using the Service itself are in our Terms of Service.