Geofeed
Sign in
Policy

Privacy and Usage Policy

Version 1.3. This page combines our privacy policy and our usage terms. Creating an account requires agreeing to this policy, and we record the version each account accepted.

Versions: 1.3 · 1.2 · 1.1 · 1.0

Part 1 - Privacy Policy

1. Who is responsible for your data

The Geofeed service ("the service", "we", "us") is run by its operator, identified as geofeed.us. You can contact the operator about anything in this policy at [email protected].

2. What we collect, why, and the legal basis

WhatDetailsWhyLegal basis (UK/EU GDPR)
Account detailsEmail address, display name, password (stored only as a one-way bcrypt hash - we never store your actual password), interface language and registration date.Create and run your account.Contract
Policy acceptance recordsYour account, email address, the date and time you accepted, the IP address used, the exact policy version and a cryptographic hash of its wording.Show which terms each account accepted, and when.Legitimate interests (keeping evidence for legal claims)
Account activity logSign-ins, sign-outs, failed sign-ins, registrations, password and email changes, geofeed creation, edits, imports and checks, and actions we take to operate the service - each with its time, IP address and an approximate city/country location derived from that IP.Keep accounts secure and detect and stop abuse.Legitimate interests (security of the service)
Sign-in throttlingA one-way hash of your IP address, kept for up to 15 minutes. Expired records are physically removed by a cleanup that runs about once a day, so an expired entry can remain stored for up to about a day beyond its expiry.Rate-limit repeated sign-in attempts.Legitimate interests (security)
Location cacheAn IP address with its resolved approximate location, cached up to 30 days (failed lookups up to 1 hour). Expired records are physically removed by a cleanup that runs about once a day, so an expired entry can remain stored for up to about a day beyond its expiry.Avoid repeating the same lookup for the activity log.Legitimate interests (security)
Geofeed content you enterFeed names, descriptions, organization or ASN, comments, and the network prefixes with their country, region, city and postal code.Provide and publish your geofeeds.Contract
Feed download statisticsPer-feed aggregate download and check counts plus the time of the last request - nothing else.Show you whether a feed is being fetched.Legitimate interests (running the service)

We deliberately do not store IP addresses, user agents or per-request logs for feed downloads. We use no analytics, no advertising and no tracking, and we do not sell personal data.

You can see your own recent activity on the Security page of your account. The people operating the service can view activity across all accounts to keep the service secure.

3. Published feeds are public

Publishing a geofeed makes its CSV file available to anyone who has its URL, without sign-in. Include only information you intend to share publicly. Feed names, descriptions, organizations and comments you enter appear in the published file.

4. Who receives data

No other third parties receive your data.

5. Cookies and browser storage

The cookie is strictly necessary and the stored preferences only adapt how the service looks and functions for you, so the law does not require a consent banner and we do not show one. There are no analytics, advertising or tracking cookies.

6. How long we keep data

7. Your rights

You can see your account details and recent activity in the app, change your email address and password there, and export your geofeeds at any time through their public CSV URLs. You can also ask us to delete your account and personal data, restrict or object to processing, or provide a portable copy of your data - email [email protected] and we will respond within one month.

If you are unhappy with how we handle your data you can complain to the UK Information Commissioner's Office (ico.org.uk) or, if you are in the EU or EEA, to your local data protection authority.

8. International transfers

Public DNS and IP geolocation records place the server in the United States, but the operator's hosting arrangements, the server's actual location and the provider's identity have not been independently confirmed. When you use the service, the personal data described above is transferred to and processed wherever the server and the services listed above operate. The geo lookup and flag services listed above resolve to the same server address as this website.

UK and EU data protection law restricts transfers of personal data outside the UK/EEA unless an adequacy decision, an appropriate safeguard (such as the UK's International Data Transfer Agreement) or a narrow Article 49 exception applies. Which of these mechanisms, if any, covers this service has not been confirmed, so the legal basis for any transfer outside the UK/EEA is uncertain. If the server is in the United States as the public records indicate, note that United States law does not provide the same level of data protection as the United Kingdom or the European Economic Area.

9. How we protect data

The service uses HTTPS, bcrypt password hashing, CSRF tokens, rate limiting, session fixation protections and locked-down database file permissions. No method of storage or transmission is completely secure; if a breach is likely to risk your rights, we will inform you and the relevant authority as the law requires.

10. Children

The service is intended for people who operate networks and publish geofeeds. It is not intended for children.

11. Changes to this policy

This policy is versioned; the current version is shown at the top of this page and earlier versions stay available on it. We will announce material changes in the app before they take effect, and the app will ask you to read and accept the updated version before you keep using your account. Every account records the exact version it accepted, together with a cryptographic hash of that version's wording, and the wording of every released version is kept on the server itself.

Part 2 - Usage Policy (Terms of Use)

12. The service

Geofeed lets you create, maintain and publish geofeed CSV files (RFC 8805 format) that map IP prefixes to locations, and gives each feed a stable public URL you can reference from registry records.

13. Your account

You must provide accurate registration information, keep your password confidential, and you are responsible for activity on your account. You must agree to these usage terms to create an account; we record your acceptance as described in Part 1.

14. Acceptable use

15. No guarantee of adoption

Publishing a geofeed does not force any geolocation provider to use it, does not prove you own a prefix, and does not update registry records. Discovery, refresh timing and acceptance are up to each consumer of the feed.

16. Availability and warranty

The service is provided "as is". We do not promise uninterrupted availability, and we may change or withdraw features, giving notice in the app where practical.

17. Liability

Nothing in this policy excludes liability that cannot be excluded by law. Otherwise, to the extent the law allows, we are not liable for indirect or consequential losses, or for any loss caused by how geolocation providers or other third parties use or fail to use a published feed.

18. Changes to these terms

We may update these terms. Material changes are announced in the app before they take effect, and the app will ask you to read and accept the updated version before you keep using your account. We record each acceptance with its version, date and time, IP address and a cryptographic hash of the wording, as described in Part 1. New accounts always accept the version current at signup, which we record.

19. Ending the service

You can stop using the service at any time and ask us to delete your account. We may close accounts that break these rules. Public feeds go offline when their owner's account is closed.

20. Contact

Questions about this policy or the service: [email protected].