Legal
Privacy policy
What personal data Railflag handles, why, who helps us process it, how long we keep it, and your rights.
Who we are
Railflag is operated by Forcehook IKE, Stigos 12, Kalavrita, Greece ("Railflag", "we"). For anything about this policy or your data, email hello@railflag.com. Our full company details are in the imprint.
We are the controller for the data of people who visit railflag.com, ask us for a migration, or have a Railflag account. For data our customers send to Railflag about their own users through the SDKs, the customer is the controller and we act as their processor; see Data our customers send us.
Visiting railflag.com
The website sets no cookies, runs no analytics or advertising, and loads nothing from third parties: fonts, scripts and images are served from our own server.
- Server logs. Our hosting provider records each request's IP address, time, requested address, response and browser user agent, to run the service and investigate abuse. Logs are kept for no longer than 30 days. Legal basis: our legitimate interest in operating a secure website (Art. 6(1)(f) GDPR).
- Theme preference. If you choose light or dark mode, your browser stores that choice in its local storage. It never leaves your device.
Migration requests and email
When you send the migration form or email us, we receive your name, work email, company, the details you give about your current tool, and your message. We use them to answer you and plan the work, on the basis of steps taken at your request before a contract (Art. 6(1)(b) GDPR). We keep them for up to 24 months after our last contact unless you become a customer, in which case they become part of your account records.
Your Railflag account
To provide the Railflag app at app.railflag.com we process:
- Account data: name, email address, a salted hash of your password (never the password itself), your organization, projects and role.
- Activity data: an audit log of the changes you make to flags, environments, members and tokens, with time and author, and approvals you request or give. The audit log is part of the service our customers rely on and is kept for as long as the organization exists.
- Security data: a session cookie, and IP addresses used briefly to rate-limit sign-in and password reset attempts.
- Access tokens you create for SDKs, scripts or AI agents. We store them in a form that lets us check them, not read them back.
- Credentials for other tools you connect for a migration, such as AB Tasty or Unleash API keys. They are encrypted with AES-256-GCM, used only to read from that tool, and deleted after 7 days without use or when you disconnect.
- Billing data for paid plans: billing contact, company name, address and VAT number. Card details go directly to our payment provider; we never see or store them.
We use this data to provide the service you signed up for (Art. 6(1)(b) GDPR), to keep it secure (Art. 6(1)(f)), and to meet tax and accounting obligations (Art. 6(1)(c)). When someone signs up, our team receives a short email with their name and organization so we can welcome them and spot abuse (Art. 6(1)(f)). We send service emails such as invitations, password resets and approval requests. We do not send marketing email without your consent.
We keep account data while your account exists. After an organization is deleted or its contract ends, we delete its data within 30 days, except invoices and records we must keep by law, which Greek tax law requires us to keep for the statutory period.
Cookies and local storage
| Name | Where | Purpose | Lifetime |
|---|---|---|---|
rf_session (cookie) | app.railflag.com | Keeps you signed in. Strictly necessary; HttpOnly and Secure. | 14 days, or until you sign out |
| Selected environment (local storage) | app.railflag.com | Remembers which environment you were looking at. | Until you clear it |
theme (local storage) | railflag.com | Remembers light or dark mode, if you chose one. | Until you clear it |
All of these are strictly necessary for something you asked for, so they need no consent. We use no tracking or advertising cookies.
Data our customers send us
Customers use Railflag to decide which of their users see which feature. What reaches us depends on the SDK:
- Server SDKs (Node, Python) download the flag rules and evaluate them inside the customer's own servers. The customer's user data is not sent to Railflag.
- The browser SDK sends the evaluation context the customer chooses (typically a user id and attributes such as plan or country) to our servers, which return the flag values. The context is used for that evaluation and not stored. To count monthly browser users for billing, we add the context key to a probabilistic counter (HyperLogLog) from which individual keys cannot be read back; the counters expire after 70 days.
- Migrations may compare decisions for sample contexts the customer provides. Those contexts are used for the comparison only.
We process this data only on the customer's instructions, under our data processing agreement (DPA), which is available on request at hello@railflag.com. If you are a user of one of our customers, please contact that company to exercise your rights; we will help them answer you.
Service providers
We use these providers to run Railflag. Each is bound by a data processing agreement and processes data only for us.
| Provider | Purpose | Data location |
|---|---|---|
| Railway Corporation (USA) | Hosting of the website, app, API, databases and logs | EU (Amsterdam, the Netherlands) |
| Cloudflare, Inc. (USA) | DNS, and the redirect from www.railflag.com | Global network |
| Resend (Plus Five Five, Inc., USA) | Sending service emails | USA |
| Stripe Payments Europe, Ltd. (Ireland) | Payments, invoices and tax for paid plans | EU and USA |
Where a provider may access data from outside the European Economic Area, the transfer is covered by the EU–US Data Privacy Framework where the provider is certified under it, and otherwise by the European Commission's Standard Contractual Clauses. We will update this list before adding a provider that processes customer data.
Security
Data is encrypted in transit with TLS. Passwords are hashed, connected tool credentials are encrypted with AES-256-GCM, and access to production systems is limited to the people who operate the service. Production changes in customers' accounts are recorded in an audit log.
Your rights
Under the GDPR you can ask us for access to your data, correction, deletion, restriction of processing, a copy in a portable format, and you can object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time. Email hello@railflag.com; we answer within one month.
You also have the right to complain to a supervisory authority. In Greece this is the Hellenic Data Protection Authority, Kifisias 1-3, 115 23 Athens. You can also contact the authority where you live or work.
We do not sell personal data, and we do not make decisions about you based solely on automated processing.
Changes to this policy
We will post any change on this page with a new effective date, and tell account holders by email before a material change takes effect.