Privacy Policy

1. Introduction

GeoSwap ("the Service") is a free geo-targeting platform operated by GeoSwap, a company registered in Wyoming, USA ("we," "us," "our"). The Service enables website owners to create geo-targeted redirects, geo short links, and personalized content experiences for their visitors.

This Privacy Policy explains what information we collect, how we use it, who we share it with, and your rights regarding your personal data. It applies to all users of the GeoSwap dashboard, the geoswap.js script, Geo Links, and any related services.

Our role. For the data we process about visitors to our customers' websites and links (and the conversions customers report to us), the website owner is the controller and GeoSwap acts as its processor, on its instructions. For account, billing and GeoSwap website data, we are the controller. A Data Processing Agreement is available to customers on paid plans; contact support@geoswap.co.

We are committed to protecting your privacy and complying with applicable data protection regulations, including the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

By using the Service, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with our practices, please do not use the Service.

2. Information We Collect

2.1 Account Information

When you create an account through our authentication provider (Clerk), we collect:

• Your name and email address as provided during registration
• Profile information associated with your authentication method (e.g., Google or GitHub profile)
• Account preferences and team membership details

2.2 Configuration Data

We store the geo-targeting rules, redirect configurations, link settings, and content personalization rules you create within the Service.

2.3 Visitor Analytics Data

When visitors interact with websites using GeoSwap's geo-targeting features, we collect aggregated analytics data including:

• Geographic location (country, region, and city) derived from the visitor's IP address at the network edge
• Device type and browser information extracted from the user agent string
• Whether the request originated from a known search engine bot or crawler
• The page URL where the geo-targeting action was triggered
• Redirect, link click, and content display event counts
• Timestamps of events
• For conversion attribution: a click ID added to short links that lead to the website owner's own sites, a recipient ID when the website owner puts one in a link, ad-platform click IDs (such as gclid or fbclid), campaign tags and the referrer of the landing page
• Conversions the website owner reports (for example a sign-up or a purchase): the event name, the owner's order or lead ID, value and currency, and a one-way hash of an email address or phone number if the owner sends one, hashed at our edge on receipt; the address or number itself is never stored
• With a conversion, when the website owner sends them: the discount, promo or referral codes used, the customer's country and state or province, and, if the website owner sends them through our API or turns on storing postal code and city, the postal code and city (for example from a Shopify order's shipping address). A street address is never stored

2.4 Information We Do NOT Collect

We want to be explicit about what we do not collect:

• IP addresses are not stored. Visitor IP addresses are processed at the edge solely to determine geographic location. They are never written to our database, logs, or any persistent storage.
• We do not use fingerprinting techniques, and we do not build advertising profiles.
• We do not join visitor or conversion data across our customers. A visitor ID is pseudonymous, stored only as a one-way hash scoped to one customer's account, and never combined with another customer's data.
• We do not collect payment information (the Service is free).
• We do not collect sensitive personal data such as health information, religious beliefs, or political opinions.
• We do not sell, rent, or trade personal data to third parties for their own marketing purposes.

2.5 Conversion Attribution

GeoSwap helps website owners see which channels, campaigns and links lead to conversions on their own websites. To do this we recognize a returning browser across visits to that owner's websites (with the gs_vid ID described below, which we store only as a one-way hash), connect short-link clicks to the visits they lead to (with a click ID), and connect the conversions the owner reports to those visits. For browsers that block cookies and storage, our edge servers derive a daily pseudonymous identifier from a one-way hash of the IP address and browser user agent (with a key that rotates daily), so that visits and conversions on the same day can be linked. The identifier is a one-way hash that can't be turned back into the IP address or user agent, the IP address itself is not stored, and the identifier can't link visits across days. Promo codes and the region sent with a conversion are used to report results by region and, later, to credit the channel a code belongs to. This stays within one customer's account and its own websites: we do not track visitors across unrelated websites. Website owners are responsible for telling their visitors about attribution and for obtaining consent where the law requires it. To have a visitor's attribution data deleted, contact the website owner or email support@geoswap.co.

2.6 Data From Meta Ad Accounts You Connect

If you connect Meta (Facebook and Instagram ads) to a workspace, Meta gives us an access token for the ad accounts you choose in Meta's dialog, with read-only permission (ads_read). GeoSwap only reads: we never create, change or delete anything in your Meta ad accounts. We store your Meta user ID (and any earlier one that connected the same workspace) and Meta business ID with the connection (to find your data if Meta sends us a deletion request). To let you choose, we list the ad accounts the token can read; we don't store the ones you don't choose. We use the token only to read, once a day and when an admin of the workspace syncs now or chooses which ad accounts to sync: each chosen ad account's name, ID, currency and time zone, and per campaign per day its ID, name, amount spent, and the purchases and purchase value Meta reports (Meta reports other actions with them; we keep only purchases). We use this data only inside your own GeoSwap workspace: to show your ad spend, cost per conversion and return on ad spend, your campaigns' names, and the platform's own reported conversions next to GeoSwap's in your reports. We do not sell it, share it with other customers or third parties, use it for advertising or profiling, use it to train AI models, or combine it with data from other customers. The access token is stored encrypted and is never shown to anyone. We don't receive or store data about the people who saw or clicked your ads.

When an ad account stops syncing because an admin of the workspace disconnects Meta, stops syncing that ad account, or reconnects with a Meta login that can't read it, GeoSwap asks that admin to choose, for each ad account, whether we delete the spend data synced from it or keep it in their GeoSwap reports. We keep it only if they choose to, and an admin can delete kept data for any ad account later. Disconnecting also stops all further access to Meta and deletes the access token. GeoSwap stays listed as a connected app in your Meta Business settings until you remove it there (Business Settings → Integrations → Connected apps).

If Meta access ends without an admin action in GeoSwap (for example, you remove GeoSwap from your Meta Business settings), we stop all further access to Meta and delete the access token. The data already synced stays until an admin of the workspace chooses to delete or keep it.

We also delete the data we received from Meta when Meta sends us a data-deletion request (you can ask from your Facebook settings), when an admin chooses "Delete data" for an ad account or, once Meta is disconnected or its access has ended, "Delete all Meta data" in GeoSwap (Integrations → Meta Ads → Manage accounts), or when the workspace is deleted. After a disconnect, your Meta user ID and business ID stay with the disconnected connection until one of these happens. You can check a deletion request at geoswap.co/meta/data-deletion. We keep a record of each deletion request (the confirmation code, the Meta user ID it came for, the date and the outcome) so it can be checked there; nothing else.

2.7 Data From Google Ads Accounts You Connect

If you connect Google Ads to a workspace, you sign in with Google and allow GeoSwap to use the Google Ads API on your behalf. Google offers only one permission for the Google Ads API, and it also allows changes; GeoSwap only reads: we never create, change or delete anything in your Google Ads accounts. We store an encrypted refresh token and your Google account's ID and email address (to show who connected and to find your data if you ask us to delete it). To let you choose, we list the accounts your Google account can access; we don't store the ones you don't choose (the list is kept for a few minutes while you choose, then discarded). Once a day, and when an admin of the workspace syncs now or chooses which accounts to sync, we read, for the Google Ads accounts you choose: each account's name, ID, currency and time zone, the ID and name of the manager account you reach it through, whether it is a test account, and per campaign per day its ID, name and type, its cost, and the conversions and conversion value Google Ads reports. We use this data only inside your own GeoSwap workspace: to show your ad spend, cost per conversion and return on ad spend, your campaigns' names, and the platform's own reported conversions next to GeoSwap's in your reports. We do not sell it, share it with other customers or third parties, use it for advertising or profiling, use it to train AI models, or combine it with data from other customers, and no person at GeoSwap reads it unless you ask us to (for support), for security, or to comply with the law. We don't receive or store data about the people who saw or clicked your ads. GeoSwap's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

When a Google Ads account stops syncing because an admin of the workspace disconnects Google Ads, stops syncing that account, or reconnects with a Google account that can't read it, GeoSwap asks that admin to choose, for each Google Ads account, whether we delete the data synced from it or keep it in their GeoSwap reports. We keep it only if they choose to, and an admin can delete kept data for any Google Ads account later. Disconnecting also stops all further access to Google Ads, deletes the refresh token and revokes GeoSwap's access at Google (unless another GeoSwap workspace still uses the same Google sign-in).

If Google Ads access ends without an admin action in GeoSwap (for example, you remove GeoSwap at myaccount.google.com/permissions, change your Google password, or the connection goes unused for 6 months), we stop all further access to Google Ads and delete the refresh token. The data already synced stays until an admin of the workspace chooses to delete or keep it.

We also delete the data we received from Google Ads when an admin chooses "Delete data" for an account or, once Google Ads is disconnected or its access has ended, "Delete all Google Ads data" in GeoSwap (Integrations → Google Ads → Manage accounts), when you email support@geoswap.co from the address you connected with (we delete it within 30 days, usually the same day), or when the workspace is deleted. After a disconnect, your Google account ID and email address stay with the disconnected connection until one of these happens.

2.8 Data From Google Search Console and Google Analytics You Connect

If you connect Google Search Console or Google Analytics (GA4) to a workspace, you sign in with Google and allow GeoSwap read-only access: Search Console with the "View Search Console data for your verified sites" permission, Google Analytics with the "See and download your Google Analytics data" permission. GeoSwap never creates, changes or deletes anything in your Search Console or Google Analytics accounts. We store a refresh token and your Google account's email address (to show who connected and to find your data if you ask us to delete it), and the property you choose. To let you choose, we list the properties your Google account can access; we don't store the ones you don't choose.

For the property you choose we read, per day: from Search Console, clicks, impressions, click-through rate and average position by page, search query, country and device; from Google Analytics, report totals such as visits by channel and key events. We may store a copy so your reports load quickly and keep history longer than Google does. We use this data only to show SEO and analytics reports and to measure your own marketing launches inside your own GeoSwap workspace. We do not sell it, share it with other customers or third parties, use it for advertising or profiling, use it to train AI models, or combine it with data from other customers, and no person at GeoSwap reads it unless you ask us to (for support), for security, or to comply with the law. GeoSwap's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting stops all further access and deletes the refresh token. We delete the data we received from Search Console or Google Analytics when an admin of the workspace asks us to, when you email support@geoswap.co from the address you connected with (we delete it within 30 days, usually the same day), or when the workspace is deleted. You can also remove GeoSwap's access at any time at myaccount.google.com/permissions.

Signing in with Google and the Google Ads, Search Console and Google Analytics connections are one app at Google, named GeoSwap, so Google shows the same app name on each consent screen and lists them together in your Google Account. Each one asks only for its own data permission (Google Ads: the Google Ads permission; Search Console: "View Search Console data for your verified sites"; Google Analytics: "See and download your Google Analytics data") plus your Google account's email address, and has its own authorization, so disconnecting one in GeoSwap never affects the others. Removing GeoSwap in your Google Account ends all of them for that Google account: GeoSwap stops reading from Google, your GeoSwap account stays, and signing in with Google again asks for your consent again. The Limited Use commitment above applies to information received from every one of them.

3. How We Use Information

We use the information we collect for the following purposes:

3.1 Providing and Operating the Service

• Processing geo-targeting decisions at the edge based on visitor location
• Executing redirects, link routing, and content personalization
• Displaying analytics dashboards to account holders about their geo-targeting rules
• Managing accounts, teams, and access permissions

3.2 Communication

• Sending service-related communications such as team invitations, account notifications, and security alerts
• Responding to support requests or inquiries you send to us

3.3 Service Improvement

• Analyzing aggregated usage patterns to improve the Service
• Identifying and fixing bugs, errors, and security issues
• Developing new features based on how the Service is used

3.4 Legal Compliance

• Complying with applicable laws, regulations, and legal processes
• Enforcing our Terms of Service and protecting against misuse

4. Legal Basis for Processing (GDPR)

Where the General Data Protection Regulation applies, we process your personal data on the following legal bases:

• Performance of a contract (Article 6(1)(b)): Processing your account data and configurations is necessary to provide the Service you registered for.
• Legitimate interests (Article 6(1)(f)): We process aggregated analytics data and usage patterns to improve the Service, maintain security, and prevent abuse. We have assessed that these interests do not override your fundamental rights and freedoms.
• Legal obligation (Article 6(1)(c)): Where we are required to retain or disclose data to comply with applicable laws.
• Consent (Article 6(1)(a)): Where explicitly given for optional features or communications. You may withdraw consent at any time.

5. Cookies and Tracking Technologies

We use a limited number of cookies that are strictly necessary for the Service to function. We do not use advertising cookies or third-party analytics cookies. On websites that use geoswap.js, a first-party visitor cookie (gs_vid, below) recognizes a returning browser for the website owner's analytics and conversion attribution.

5.1 Dashboard Cookies

• Authentication cookies (set by Clerk): Essential for maintaining your signed-in session. These are strictly necessary and do not require consent.
• geoswap_active_workspace: Stores your currently selected account for multi-account switching. This is a functional cookie necessary for the Service.

5.2 Visitor-Facing Cookies (geoswap.js)

When a website uses GeoSwap's geo-targeting script, the following cookies may be set on the visitor's browser:

• geoswap_visited_{ruleId}: A small cookie used to identify whether a visitor has previously triggered a specific redirect rule, enabling "first visit only" behavior. Contains no personally identifiable information.
• geoswap_popup_dismissed_{ruleId}: Records that a visitor has dismissed a specific popup (or bar) so it is not shown again. Contains no personally identifiable information.
• gs_sid: Counts sessions on the website. It holds a random ID and a timestamp, never leaves the visitor's browser, and expires after 30 minutes of inactivity.
• gs_vid: Recognizes a returning browser so the website owner can count unique visitors and attribute conversions on their own websites. It holds a random ID and the date it was first set, and lasts up to 400 days (7 in Safari). The ID is sent to GeoSwap, which stores only a one-way hash of it, scoped to that website owner's account, never the ID itself.
• geoswap_consent_{id}: Stores a visitor's cookie-banner choice, only on websites that use GeoSwap's consent banner.
• geoswap_override_{id}: Set only when someone opens a website owner's preview (override) link; it ends with the browser session.
• Local and session storage (gs_s_…, gs_p_…): gs_s_ lives in local storage and holds the page count and landing campaign (UTM values and the landing referrer) of the current visit, and which A/B variant you were shown (a rule id and a letter). gs_p_ lives in session storage and clears when the browser tab closes; it holds the previous page's URL and the time spent on it. Used for engagement and time-on-page reports. Each page view sends the current page URL, the previous page's URL and time spent on it, the page count and landing campaign of the visit, and the visitor ID (gs_vid, above). When a GeoSwap redirect or link sends you to a page, the address may briefly carry a gs_arm parameter naming which A/B variant you were shown; if that page also runs the GeoSwap script, the script removes the parameter from the address bar on load. gs_s_ also keeps the visit's latest GeoSwap click ID and recipient ID. When a GeoSwap short link or redirect sends you to the website owner's own site, the address may briefly carry gs_c (a click ID), gs_r (a recipient ID) or gs_q (a QR-code marker); the script removes them on load. The website may also copy these IDs into hidden form fields so a form submission can be attributed.

These visitor-facing cookies are minimal, first-party, and contain no names or email addresses; the visitor ID, click ID and recipient ID they may hold are pseudonymous identifiers. They make the website owner's rules behave as configured (for example, not repeating a redirect or popup), count sessions and unique visitors, and attribute conversions on the website owner's own websites.

5.3 No Third-Party Tracking

We do not embed third-party trackers, pixels, or analytics scripts in the geoswap.js script or on our customers' websites. Our own website and dashboard use the measurement and product analytics tools listed in section 6 (Google Tag Manager, Google Analytics and Ads, and PostHog). We do not participate in retargeting, and we do not track visitors across unrelated websites: attribution stays within one website owner's own websites.

6. Data Sharing and Third Parties

We do not sell your data. We share data only with the following categories of service providers that are necessary to operate the Service:

All service providers process data solely on our behalf and in accordance with our instructions. They are bound by data processing agreements and are prohibited from using the data for their own purposes.

We may also disclose information if required by law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of GeoSwap, our users, or others.

7. International Data Transfers

Our infrastructure providers operate globally. Your data may be processed in countries other than your own, including the United States. Where personal data is transferred outside the European Economic Area, we rely on appropriate safeguards such as the Standard Contractual Clauses approved by the European Commission (Decision 2021/914) or on adequacy decisions. Where personal data is transferred from the United Kingdom, we rely on the UK GDPR transfer safeguards, such as the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, and for Switzerland on the Standard Contractual Clauses as adapted for the Swiss Federal Act on Data Protection.

For customers, these safeguards are set out in our Data Processing Agreement, which is available to customers on paid plans; contact support@geoswap.co.

Cloudflare Workers process visitor requests at edge locations worldwide. IP addresses are used transiently at the nearest edge node for geographic determination and are not transferred to or stored at any central location.

8. Data Retention

We retain data according to the following schedule:

• Account data: Retained for as long as your account remains active. Upon account deletion, we remove your personal data within 30 days, except where retention is required by law.
• Configuration data: Deleted when you delete the associated rules or your account.
• Visitor event data: Individual visitor events (country, region and city, device and browser type, referrer, page URL parameters, a daily-rotating one-way visitor hash and, for attribution, click IDs and a pseudonymous per-customer visitor key — no IP addresses, names or account identifiers) are retained for 90 days, then deleted by a weekly cleanup (so no more than 97 days in total). Attribution touches (one record per visit landing, holding the same kinds of fields as the visitor events above — including browser and OS with version, device type, the daily-rotating visitor hash and approximate location — plus the landing page path, click IDs, UTM campaign tags, the referring page and, from per-recipient links, a recipient ID) and link clicks used for attribution (link rows carrying a click ID) are kept for 400 days, then deleted by the same weekly cleanup (so no more than 407 days in total).
• Conversions: Kept until the website owner asks us to delete them (support@geoswap.co) or deletes their account, with the codes and region sent with them, and the site (domain only) each credited visit was referred from. Emails and phone numbers in conversions are stored only as one-way hashes.
• Aggregated analytics: Daily totals and breakdowns (counts per country, device and so on) contain no visitor-level data. Per-rule and per-link daily totals are retained for as long as your account is active, to provide your plan's analytics history. Campaign, page, consent-choice and unique-visitor rollups are retained for about 400 days (13 months), then deleted.
• Data from Meta: Deleted when a workspace admin chooses to delete it (when disconnecting Meta or stopping an ad account's sync, with "Delete data" for one ad account, or with "Delete all Meta data"), when Meta sends us a data-deletion request, or when the workspace is deleted. Data an admin chooses to keep stays in their reports until then. If access ends without an admin action, we stop syncing, delete the access token and keep the data until an admin decides. Daily campaign figures are kept 400 days, then deleted; the weekly spend totals and campaign names built from them stay in your reports until deleted as above.
• Data from Google Ads: Deleted when a workspace admin chooses to delete it (when disconnecting Google Ads or stopping an account's sync, with "Delete data" for one account, or with "Delete all Google Ads data"), when you ask us by email to delete it, or when the workspace is deleted. Data an admin chooses to keep stays in their reports until then. If access ends without an admin action, we stop syncing, delete the refresh token and keep the data until an admin decides. Daily campaign figures are kept 400 days, then deleted; the weekly spend totals and campaign names built from them stay in your reports until deleted as above.
• Visitor IP addresses: Not retained. Processed transiently at the edge and discarded immediately after geographic determination.
• Visitor-facing cookies: Expire automatically: gs_sid after 30 minutes of inactivity, gs_vid after 400 days (7 in Safari), the override cookie when the browser session ends, a banner choice after a year, and rule cookies after the period the rule uses (up to 90 days, or the browser session).

9. Your Rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

• Right of access: You may request a copy of the personal data we hold about you.
• Right to rectification: You may request correction of inaccurate or incomplete personal data.
• Right to erasure: You may request deletion of your personal data, subject to legal retention requirements.
• Right to restrict processing: You may request that we limit the processing of your data in certain circumstances.
• Right to data portability: You may request your data in a structured, commonly used, machine-readable format.
• Right to object: You may object to processing based on legitimate interests.
• Right to withdraw consent: Where processing is based on consent, you may withdraw it at any time without affecting the lawfulness of prior processing.
• Right to lodge a complaint: You have the right to lodge a complaint with your local data protection authority if you believe your rights have been violated.

To exercise any of these rights, contact us at support@geoswap.co. We will respond to your request within 30 days.

10. California Privacy Rights (CCPA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act:

• Right to know: You may request the categories and specific pieces of personal information we have collected about you.
• Right to delete: You may request deletion of your personal information, subject to certain exceptions.
• Right to non-discrimination: We will not discriminate against you for exercising your CCPA rights.
• Right to opt out of sale: We do not sell personal information. No opt-out is necessary.

In the preceding 12 months, we have not sold any personal information and do not intend to do so. To submit a CCPA request, contact us at support@geoswap.co.

11. Security

We implement appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. These measures include:

• Encryption in transit using TLS for all data transmitted between your browser, our servers, and third-party services
• Encryption at rest for database storage
• Role-based access controls within the dashboard and internal systems
• Edge processing of sensitive data (IP addresses) that never reaches our central servers
• Regular security reviews and dependency auditing

While we strive to protect your data, no method of transmission over the internet or method of electronic storage is completely secure. We cannot guarantee absolute security.

12. Children's Privacy

The Service is not directed to individuals under the age of 16. We do not knowingly collect personal data from children under 16. If we become aware that we have inadvertently collected personal data from a child under 16, we will take steps to delete such data promptly. If you believe a child under 16 has provided us with personal data, please contact us at support@geoswap.co.

13. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will:

• Update the "Last updated" date at the top of this page
• Provide notice through the Service dashboard for significant changes
• Where required by law, obtain your consent before applying changes to previously collected data

We encourage you to review this Privacy Policy periodically. Continued use of the Service after changes have been posted constitutes your acceptance of the revised policy.

14. Contact Information

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:

We will acknowledge receipt of your inquiry within 5 business days and aim to resolve all privacy-related requests within 30 days.