Privacy policy

Controller

Openfactory GmbH, Moosweg 85, 8500 Frauenfeld, Switzerland, operates this service and is responsible for the data processed in the FreeTransit portal.

What we process

We process account details, contact information, addresses, request details, ticket references, sponsored resource inventory, generated agreements, uploaded signed agreements, supporting documents, invoice references, outbound service-email records, and operational notes needed to provide and administer FreeTransit and RIPE sponsorship services.

Identity documents

For RIPE sponsorship we may need to validate identity documents or commercial-register extracts. Identity documents are used for verification and are purged from the web application as soon as they are no longer needed for the sponsorship process or compliance review. The portal keeps audit metadata showing that validation happened.

Retention

We keep customer, contract, resource, ticket, and billing records while you are a FreeTransit or sponsorship customer and for as long as required for accounting, legal, dispute-resolution, security, and RIPE-related compliance purposes. If service ends, operational records may be retained where necessary to document previous assignments, invoices, abuse handling, and contractual history.

Recipients and systems

Data may be processed in the FreeTransit portal, Openfactory ticketing systems, RIPE NCC systems, and billing systems such as Bexio where needed to operate the service. We do not use external captcha providers on the request form.

Service email

When FreeTransit sends application-generated service email, we retain the recipient, subject, plain-text message, related customer or case, delivery status, timestamps, and technical message identifier. This provides an operational record of notices and authorization reminders. Failed delivery information may also be retained for troubleshooting.

Your rights

You can request a copy of the data held about you, ask for corrections, and request deletion where retention is no longer required. Portal users can download a machine-readable JSON export from their profile. Staff can also export a client record for handling support or privacy requests.

PeeringDB authentication

When you authenticate through PeeringDB, PeeringDB may provide your user identity, name, e-mail verification status, and the networks and ASNs with which your account is affiliated. FreeTransit uses this information to authenticate portal users and to verify that a new transit applicant is authorised for the selected ASN. We retain the PeeringDB user ID, the relevant ASN verification result and its timestamp for account security and request auditing; OAuth access tokens are not retained.

Contact

For privacy requests, contact Openfactory through the FreeTransit support channel or by opening a ticket in the portal.