1. We respect your privacy
- stillorigin is operated by The App Development Co Pty Ltd (ABN 20 628 711 795), trading as stillorigin, in Queensland, Australia ("stillorigin", "we", "us"). We respect your right to privacy. This policy explains how we collect, use and look after personal information.
- We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth), whether or not the small business exemption would otherwise apply, and, where it applies, the EU General Data Protection Regulation (GDPR).
- "Personal information" means information that identifies you or could reasonably identify you, directly or indirectly. Examples are your name, email address or IP address.
- For anything about this policy, email info@stillorigin.net or write to us at PO Box 3301, Newstead QLD 4006, Australia.
2. What this policy covers
This policy covers:
- stillorigin.net: our public website, including the contact form for pre-sales and media enquiries.
- stillorigin.app: the portal, where hosts manage their account, sentries, origins, domains, limits, licences and helpdesk tickets. It also includes the public naughty list check page (
/check) and the delisting page (/delist). - kb.stillorigin.app: the public knowledge base.
- The hosted control plane: the stillorigin service that sentries connect to, to get their settings and updates and to send traffic counts and block information to the portal.
- Sentries: the firewall software a host installs and runs on its own servers, in front of the websites it hosts.
- owners.stillorigin.app: the domain owner area, where a host's customers can see and manage the protection of their own domain, when the host gives them access.
stillorigin runs the portal, the domain owner area, the knowledge base and the control plane. Hosts run their own sentries.
3. Hosts, their customers and their visitors
- The host is responsible for its own customers' and visitors' data. A host that uses stillorigin decides which websites go behind its sentries, and runs those sentries on its own servers. The host is responsible for its own customers' and website visitors' personal information on those servers, including telling them how it's handled.
- Web traffic stays on the host's network. Visitors' web traffic passes through the host's sentries to the host's own servers. It doesn't pass through stillorigin.
- What sentries send us. To provide filtering, the portal reports and the naughty list, sentries send us a limited amount of information, which we process on the host's behalf:
- counts of web requests allowed and blocked for each hostname, every minute. These contain no visitor data;
- counts of crawler visits;
- block events: the visitor's IP address, why it was blocked, and, where available, the page path and the browser's user agent. We record at most one event for each IP address and reason every 30 seconds;
- temporary bans: the IP address (for IPv6, the /64 range it belongs to), the reason and when the ban ends; and
- the health of each sentry: its software version, load, when it was last seen and the sentry server's IP address.
- The naughty list. The stillorigin naughty list is a list of addresses that have sent abusive traffic, such as vulnerability scans, password guessing and floods of requests. stillorigin's team adds addresses, and an address is also added automatically when sentries at three or more separate stillorigin customers block it for excessive traffic within 24 hours. For each listing we keep the address or range, a general category of the reason (for example password guessing), the listing level, the date it was listed, when it expires or whether it's permanent, a history of changes to it, and a count of how many customer accounts contributed. That count is public. Internally, we also record which customer accounts contributed. Only stillorigin administrators can see that, and it is never shown publicly or to the listed party. The raw signals that feed a listing are deleted after 2 days.
- If you visited a website protected by a stillorigin sentry and have a question about your data, contact the website's host first. You can also contact us at info@stillorigin.net, and we'll help where we can.
- Domain owners. A host can give the owner of one of its domains with Website protection, usually the host's own customer, access to the domain owner area. A domain owner sees data for their own domain only: allowed and blocked counts, the IP addresses of blocked visitors and their approximate location (city and country), the page paths requested, and why requests were blocked or would have been blocked. We show this on the host's behalf. The host decides who gets access, and is the party responsible to its own customers and their visitors for it, including telling them about it. stillorigin doesn't give support to domain owners. If you're a domain owner, contact your host.
The Terms of Service and this privacy policy cover how we handle personal information. If you need a separate data processing agreement, you can request one at info@stillorigin.net. We act as a processor for visitor data handled for a host's websites, including when we show it to a domain owner the host has given access to, and as a controller for our own websites, accounts, billing and the naughty list.
4. What personal information we collect
- Contact form (stillorigin.net). Your enquiry type (pre-sales or media), name, work email, company or hosting business, country and message, and, if you give them, your website and the approximate number of servers or sites. When you send the form, we also receive your IP address, your browser's user agent and the time. The enquiry is emailed to info@stillorigin.net. It isn't stored in a database.
- Portal account (stillorigin.app).
- For each person who signs in: their email address, name, password and the date the user was created. Passwords are stored only in hashed form, never as typed.
- For each customer account: the account name, the email address that alerts go to, and a key that the account's sentries use to connect to us.
- Sign-in codes and password reset links are stored only in hashed form. Codes expire after 10 minutes and reset links after 30 minutes.
- An audit log of changes made to the account, by the account's own users and by stillorigin staff viewing the account. Each entry records who made the change (by their email address), what changed, the IP address it came from and the time. Passwords, keys and other secrets are never recorded. The account's users can see the audit log in the portal, and entries are kept for 90 days. Changes made by stillorigin staff show to the account as "stillorigin support", without the staff member's email address or IP address. Domain owner entries are described below.
- We don't collect phone numbers. Card details never reach stillorigin; see billing below.
- Billing. Payments are handled by Stripe, a payment processor based in the United States. Card details go straight to Stripe and never reach stillorigin. We collect the business's legal or trading name, a billing contact, email address, postal address, country and tax ID, as well as the reference numbers Stripe gives us. To apply the one-trial-per-business rule, we also keep a fingerprint Stripe provides for the card, which isn't the card number, and a standardised copy of the tax ID.
- Helpdesk tickets. Support and all customer communication go through the helpdesk ticket system in the portal. We keep each ticket's subject and messages, and the account that sent them.
- Traffic and security data from sentries. See section 3.3.
- Naughty list check (
/check). The check page shows whether the IP address you're visiting from, or one you enter, is listed, and if it is, a general category of the reason. It never shows who reported an address. We don't store checks. To prevent abuse, we limit how often checks can be made, and the counts for that are kept only briefly in memory. - Delisting (
/delist). To ask us to delist an address, the request has to come from the listed address itself. You can open the delisting page from that address, or request a one-time code from it (valid 15 minutes, once) and enter the code and your email address on the delisting page from any device. We email you a confirmation link that lasts 30 minutes. We keep the listed address, your email address, the IP address you made the request from, the status of the request and our decision. Codes and confirmation links are stored only in hashed form. We don't accept disposable email addresses. - Public traffic totals. stillorigin.net shows the total web requests allowed and blocked across all customers. These are totals only and contain no personal information.
- Website and portal technical data. When you visit our websites, our servers receive your IP address and browser details. We keep access logs, including IP addresses, for 30 days.
- Website analytics (stillorigin.net and kb.stillorigin.app). We count visits to our website and knowledge base ourselves, on our own server, from our web server's page-request logs. We use no cookies, no tracking script and no third-party analytics service, and we leave out bots and crawlers.
- Separately from the access logs in section 4.9, for each page request our web server writes a line to an analytics log with your IP address, your browser's user agent, the page address, the referring page and the time. We delete this log after 1 day.
- From each line, the analytics keep only: the page path, the host name of the site that referred you (for example, google.com), the utm source, medium and campaign if the link had them, your country, and your device type (desktop, mobile or tablet) and browser type (for example, Chrome or Safari). The analytics don't keep your IP address, user agent, any cookie, or the rest of the page address (the query string).
- Your IP address is used only briefly, in memory, to look up your country in an IP-to-country database on our own server (no outside lookup service is used) and to make a daily visitor hash. It isn't stored with the analytics.
- To count each visitor once a day, we combine your IP address and user agent with a random value (a salt) that changes every day, and keep only the resulting hash. Salts and hashes are deleted after 2 days, so we can't follow a visitor from one day to the next.
- What we keep long term is daily totals only, such as page views and visitors by page, referring site, country, device and browser. They contain no IP addresses, user agents or visitor hashes, and we keep them for 25 months.
- Captcha Protection. Captcha Protection doesn't use a third-party captcha provider.
- Domain owner area (owners.stillorigin.app). Domain owners don't have stillorigin accounts, and we don't ask for their name or email address. We keep:
- for each one-time login link: which domain it's for, how the host made it (with its account API key, an origin agent, or a test from the portal, recorded by key, agent or user number, never a name), the IP address it was requested from, when it was made and expires, and when it was used and from which IP address. The link itself is stored only in hashed form;
- for each domain owner session: the domain, the IP address it signed in from, when it started, when it was last active, and when and why it ended. The session cookie is stored only in hashed form;
- an entry in the host's audit log for each sign-in and each change a domain owner makes (log mode or blocking, bot blocking and rate limits), with the IP address, what changed and when. The entry names the domain owner only by how they signed in, for example "domain owner via API key". The host can see these entries in the portal; and
- the settings a domain owner chooses for their domain.
5. How we collect your personal information
- We collect personal information when you fill in the contact form, sign in to or use the portal or the domain owner area, open a helpdesk ticket, check or delist an address, or visit our websites.
- We receive the information in section 3.3 from the sentries that hosts run in front of their websites.
- By giving us personal information, you agree to it being handled as set out in this policy.
6. How we use your personal information
We use personal information only for these purposes:
- to reply to contact form enquiries;
- to provide the stillorigin service: the portal, the control plane, sentry settings and updates, traffic filtering, reports and the naughty list;
- to run accounts, free trials and subscriptions;
- to send service emails, such as sign-in codes, password resets, delisting confirmation links, account alerts, trial reminders and billing notices. These come from noreply@stillorigin.app, through our own mail server. We don't send marketing email;
- to answer helpdesk tickets and investigate complaints;
- to keep the service secure, prevent abuse, and understand and improve the service;
- to count visits to stillorigin.net and kb.stillorigin.app, so we can see which pages people read and how they find us (see section 4.10); and
- to produce counts of web requests allowed and blocked, which we publish only as totals across all customers.
If you don't give us the information we ask for, we may not be able to reply to you or provide the service.
We may disclose personal information to comply with a legal requirement, such as a law, regulation, court order, subpoena, warrant or legal proceedings, or in response to a request from a law enforcement agency.
If there is a change of control of our business, or a sale or transfer of business assets, we may transfer our databases, including any personal information in them, to the extent the law allows.
7. Who we share personal information with
- Hosts see the allowed and blocked counts, blocked IP addresses and block reasons for their own sentries and domains in the portal. They also see the audit log entries for their domain owners' sign-ins and changes.
- Domain owners see the data in section 3.6 for their own domain only, when the host gives them access.
- The naughty list. Sentries across clusters apply the naughty list, and anyone can check whether an address is listed. The check never shows who reported an address. A count of how many customer accounts contributed to a listing is public. Which accounts contributed is never shown publicly or to the listed party.
- Our servers. Our websites, the portal, the knowledge base and the control plane run on servers in New York, United States. Our mail server and backups are in Sydney, Australia.
- MaxMind. We look up the country and city of IP addresses in block events, so hosts, and domain owners they give access to, can see where blocked traffic comes from. Those IP addresses are sent to MaxMind, which is based in the United States, and the results are cached for 24 hours.
- Stripe. See section 4.3.
- Monitoring. We use Nagios and Wazuh, which run on our own servers in Australia, to monitor server uptime, health and security. They process server logs, which can include IP addresses. We don't use third-party analytics or error-tracking services. Our own website analytics are described in section 4.10.
- The portal and the knowledge base at kb.stillorigin.app load no third-party scripts, styles or fonts. Captcha Protection doesn't use a third-party captcha provider.
- We may also share personal information with our employees, officers, insurers and professional advisers, as far as is reasonably needed for the purposes in this policy.
- We don't sell personal information.
8. GDPR (European Union)
- Where the GDPR applies, we follow its principles of fairness, transparency and lawful collection and use.
- For visitor data handled for a host's websites, we act as a processor for the host. For our own websites, accounts, billing and the naughty list, we act as a controller.
- We process personal information only with a lawful basis: to perform a contract with you, for our legitimate interests (such as keeping the service secure and filtering abusive traffic), to meet a legal obligation, or with your consent.
- We collect only what we need for each purpose.
- We don't collect sensitive personal information, such as information about your ethnic origin or sexual orientation.
- Our services are for businesses. We don't knowingly collect personal information from anyone under 16.
9. Your rights under the GDPR
If you live in the EU, you have these rights, except where the GDPR provides otherwise:
- to be told how your personal information is used;
- to get a free copy of your personal information;
- to correct personal information that is inaccurate or incomplete;
- to have your personal information deleted;
- to restrict how we process your personal information;
- to receive your personal information and reuse it for your own purposes;
- to object to your personal information being used; and
- to object to automated decision-making and profiling.
If an IP address on the naughty list is yours, you can check it and ask to delist it through the delisting page. Some addresses are added to the list automatically, and our team reviews any delisting request that can't be removed straight away.
To use any of these rights, email info@stillorigin.net. We may ask you to prove who you are before we act on a request.
10. Where your information is held
- We hold personal information on servers in New York, United States. Backups are held in Sydney, Australia, encrypted and kept off the server. Service emails are sent from our mail server in Sydney, Australia. Our monitoring tools also run on our own servers in Australia.
- stillorigin is an Australian company, and we follow the Australian Privacy Principles when personal information is stored or disclosed overseas. Personal information is held in the United States, and is also disclosed to:
- Stripe (United States), which processes payment details; and
- MaxMind (United States), which receives the IP addresses in block events.
- Because the servers are in the United States, that information may be subject to United States law.
- Sentries run wherever each host puts them. The host is responsible for its own servers.
11. Keeping personal information secure
- We take reasonable physical, electronic and managerial steps to protect personal information from misuse, interference, loss, and unauthorised access, change or disclosure.
- Passwords, sign-in codes, password reset links, delisting codes, and domain owner login links and session cookies are stored only in hashed form.
- Sentry software is signed and updates itself.
- Backups are encrypted and kept off the server, in Sydney, Australia.
- No method of sending information over the internet is completely secure. We can't guarantee the security of information sent to us or received from us.
12. How long we keep personal information
We keep personal information only for as long as we need it for the purposes in this policy, or as the law requires.
| Information | How long we keep it |
|---|---|
| Allowed and blocked counts for each hostname, every minute | 48 hours. After that, only hourly totals, which contain no visitor data. |
| Crawler counts | Hourly counts for 30 days, then daily totals for 2 years |
| Block events (IP address, reason, path, user agent) | 3 days. After that, a daily summary for each IP address (counts, reason, first and last seen, with no path or user agent) is kept for 90 days. |
| Temporary bans | Deleted when the ban ends (10 minutes by default) |
| Sentry health data | 48 hours |
| Naughty list listings | For as long as the listing lasts. Listings expire unless they're made permanent. |
| Naughty list change history | 1 year after a listing ends, or for as long as a permanent listing stands |
| Crowd-listing contribution records (which customer accounts contributed) | Kept with the listing and its change history. Never shown publicly or to the listed party. |
| Raw signals that feed a naughty list listing | Deleted after 2 days |
| Delisting codes | 15 minutes; deleted a day after they expire |
| Delisting requests | 6 months |
| Expired sign-in codes and password reset links | Deleted 1 day after they expire |
| Domain owner login links | 5 minutes, single use; deleted 1 day after they expire |
| Domain owner sessions (domain, IP address, times) | Deleted 7 days after the session ends. A session ends after 30 minutes without activity, or 8 hours after sign-in at most. |
| Audit log entries (changes by the account's users and stillorigin staff, and domain owner sign-ins and changes) | 90 days |
| Support tickets | Deleted within 30 days of account closure, unless the law requires us to keep them |
| Portal account data after an account closes | Deleted within 30 days, unless the law requires us to keep it |
| Mail to info@stillorigin.net and support addresses | 1 year. The noreply address keeps no copies. |
| Web server access logs | 30 days, including IP addresses |
| Website analytics log (IP address, user agent, page address, referring page and time for each page request) | 1 day |
| Daily visitor hashes and their salts | Deleted after 2 days |
| Website analytics daily totals (no IP addresses, user agents or visitor hashes) | 25 months |
| Backups | Encrypted and kept off the server, in Sydney, Australia |
| Naughty list checks | Not stored |
13. Accessing and correcting your personal information
- You can ask for the personal information we hold about you under the Privacy Act 1988 (Cth) and, where it applies, the GDPR. If you want a copy, or think something we hold is inaccurate, out of date, incomplete, irrelevant or misleading, email info@stillorigin.net.
- Hosts can also ask through the helpdesk in the portal to update their account details.
- In some cases set out in the Privacy Act or other laws, we may refuse a request. If we do, we'll tell you why.
14. Privacy complaints
- If you have a complaint about how we handle personal information, email the details to info@stillorigin.net. We take complaints seriously and aim to respond within 14 days.
- If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.
15. Cookies and browser storage
We use only our own cookies. We don't use tracking, advertising or analytics cookies. Our website analytics use no cookies or browser storage (see section 4.10).
stillorigin.net sets no cookies. The public traffic chart saves the latest public totals in your browser for up to five minutes, so the page doesn't have to fetch them again. These totals contain no personal information.
stillorigin.app uses these cookies:
| Cookie | What it's for | How long it lasts |
|---|---|---|
stillorigin | Keeps you signed in to the portal. It can't be read by page scripts and is sent only over HTTPS. | 14 days, renewed while you use the portal |
so_challenge | Remembers that you're partway through the sign-in code step | 10 minutes, deleted once you're signed in |
.AspNetCore.Antiforgery.… | Protects the sign-in pages and the delisting form against forged submissions | Short-lived, for form security |
so_tz | Remembers your time zone so times show correctly. It stores nothing else. It's set on all portal pages, including /check and /delist. | 1 year |
owners.stillorigin.app uses these cookies. They're sent only to owners.stillorigin.app, never to the portal or any other site:
| Cookie | What it's for | How long it lasts |
|---|---|---|
__Host-so_owner | Keeps a domain owner signed in. It can't be read by page scripts and is sent only over HTTPS. | Until you close your browser. The session itself ends after 30 minutes without activity, or 8 hours after sign-in at most. |
__Host-so_owner_af | Protects the domain owner area's forms against forged submissions | Short-lived, for form security |
Most browsers let you block or delete cookies. If you do, you may not be able to sign in to the portal or the domain owner area, or use the delisting form.
16. Links to other websites
Our websites may link to sites we don't own or control. A link isn't an endorsement, and we're not responsible for other sites' privacy practices. Please read the privacy policy of any site that collects your personal information.
17. Changes to this policy
We may change this policy from time to time, and we'll update it before we launch new features that collect personal information. Changes take effect when we publish them on stillorigin.net. Please check back now and then.