Legal / Privacy
Privacy policy
What personal data CyberOwl handles, why, and what you can ask us to do with it.
In force since
In short
CyberOwl holds three kinds of personal data. Account data of the people who sign in. Engagement data: what our testers find in the systems a customer asks us to test, which can include personal data that lives in those systems. And contact details you give us when you ask for a demo. We do not sell any of it, we run no advertising or tracking scripts, and the address at the bottom of this page reaches a person.
01
Who this covers
CyberOwl is a penetration testing platform operated by Nexa. This policy applies to the public site at nx-cyberowl.com, to the platform behind it, and to the reports and emails it produces.
It describes personal data belonging to three groups:
- People who use the platform: the members of a customer organization, and the testers and staff who deliver the work.
- People whose data lives in a tested system: a finding or a piece of evidence can show data about a customer's own users or employees. They are usually not our users.
- People who contact us through the demo request form on the public site.
02
Data we hold about platform users
| Category | What it contains |
|---|---|
| Account | Your full name, email address, the organization you belong to and your role in it. If you add them: a phone number, a profile picture and a time zone. |
| Authentication | Your password, stored only as a one-way hash. If two-factor authentication is on, the secret for your authenticator app, stored encrypted, and your recovery codes, stored as hashes. If you sign in with Google, the identifier Google issues for your account and the email address it confirmed. |
| Session and connection | A session cookie, the IP address and browser a session was opened from, the time and address of your last sign-in, and a counter of failed sign-in attempts. |
| Activity record | Actions taken in the platform, each with the person who did it, what it affected, the IP address, the browser and the time. This is a security record: the database rejects edits and deletions of its entries. |
| Developer access | API keys, stored as a hash with a short visible prefix, with their scopes, optional expiry and last use. Webhook signing secrets, stored encrypted. |
| Work you create | Campaigns and their scope, findings, evidence files, comments, remediation notes, reports and, for testers, time entries. |
| Tester profile and payments | For the testers who deliver the work: a professional profile (biography, experience, certifications, specializations, country, languages and links they choose to add), the counts and reputation score computed from their findings, review notes, and what is needed to invoice and pay them. |
How accounts are created. You can register on the public site; the account becomes active when you confirm your email address. A new customer organization is reviewed by Nexa before it gets access, and members join an existing organization by invitation. Tester and staff accounts are created by Nexa.
Server logs. Our web servers keep access logs that include the IP address of each request, whether or not you are signed in. They are written to rotating files and overwritten as those fill.
03
Data that comes from the systems we test
This is the part that makes a security testing platform different, so it deserves a plain explanation. When a customer asks us to test an application, a network or an organization, our testers look at it the way an attacker would. What they record can contain personal data that was already in that system: a screenshot of a page, a request and its response, a record that should not have been reachable.
- Whose decision it is. The customer chooses what is in scope and authorizes the test. We handle what we find on the customer's behalf, to show the weakness and help fix it.
- What we keep to learn from. Nexa keeps an internal reference library of findings from past engagements: what the weakness was, how severe, and in what kind of product. Our staff use it to write and calibrate later reports. It is not shown to other customers.
- Who can see it. Findings and evidence are visible to the members of the organization they belong to, to the testers assigned to that work, and to the Nexa staff who run it.
- How evidence is handled. Every uploaded file is scanned for malware before anyone can download it. A file that fails the scan is blocked, and a file still waiting for its scan is held back.
- Credentials for testing. Give our team dedicated test accounts where you can, share them through the channel agreed for your engagement, and rotate them when the work ends.
If you believe your data appears in a finding, write to the organization that operates the system first: it decides what happens to that data. You can also write to us, and we will pass the request on.
04
When you ask for a demo
The demo request form stores what you type: your name, work email, company, the service you are interested in if you choose one, your message, and the language of the page you sent it from. We use it to reply to you and to prepare that conversation.
We do not store your IP address with the request. To stop abuse, the form limits how many requests one address can send in an hour, and for that it keeps a hash of the IP address for one hour.
05
What we use it for
- Running the platform: signing you in, limiting what you see to your organization and your role, and showing your campaigns, findings and reports.
- Delivering the work: planning tests, recording findings and evidence, verifying fixes and producing reports.
- Telling you what changed: emails about your account, a campaign that started, a new finding or a comment.
- Protecting the service: rate limits, malware scanning, and the activity record used to investigate misuse.
- Answering you when you write to us or ask for a demo.
- Meeting legal obligations and responding to lawful requests.
We do not sell or rent personal data, and we do not use findings or evidence for marketing.
08
Automated analysis
Some of what the platform shows is computed: severity scores, posture indicators and, where the AI feature is on, a suggested triage for a finding. These are inputs for the people doing the work, and a person decides whether a finding is accepted. The platform also computes a reputation score for each tester from the outcome of their findings, and shows it on an internal leaderboard.
09
How it is protected
- Passwords are stored only as one-way hashes, and must be at least twelve characters long.
- Two-factor authentication is available on every account that signs in with a password, and is required by default for administrators and technical leads. Accounts that sign in with Google rely on Google's own sign-in protection instead.
- Sign-in, registration and password reset are rate limited, and repeated failures lock the account temporarily.
- What you can see is limited by your organization and by the role you hold in it.
- Integration credentials, authenticator secrets and webhook secrets are encrypted before they are stored.
- Uploaded files are scanned for malware before they can be downloaded.
- The database rejects edits and deletions of entries in the activity record.
- Traffic is HTTPS only, with strict transport security, a content security policy and clickjacking protection.
The security page keeps the full list, and explains how to report a weakness if you find one.
10
How long we keep it
Account data lives for as long as the account exists. Campaigns, findings, evidence and reports are kept so an organization can track a weakness from discovery to verified fix and compare one assessment with the next. The platform does not delete them on a timer today; where your organization needs a committed period, that belongs in its agreement with us.
Demo requests have no automatic expiry either; write to us to have yours deleted. Files that belonged to deleted findings, uploads or reports are removed from storage automatically.
11
Closing an account
Accounts are closed by a Nexa administrator, on your request or your organization's; there is no self-service deletion. Closing an account removes your name, email address, phone number, profile picture and sign-in details, ends your sessions and revokes your API keys.
Some things stay on purpose: the activity record of what the account did, and the testing work it took part in, including comments and notes you wrote, which remain without your name on the account. Your email address can also remain in records of emails already sent to you, in invitations and in the activity record. An audit trail that disappears when an account is deleted would not be an audit trail.
12
Your rights and how to use them
Depending on where you live, you can ask to access your personal data, to correct it, to have it erased, to restrict or object to how it is processed, and to receive it in a portable form.
If you use the platform, start with your organization's administrator for anything about your account, and write to us for the rest. If your data appears in a finding, see data that comes from the systems we test.
We ask for enough information to confirm you are who you say you are before acting on a request; for a request about an email address, that normally means writing from it. We answer every request, and where we cannot act we tell you why. If you are not satisfied, you can complain to your data protection authority: in Uruguay, the Unidad Reguladora y de Control de Datos Personales (URCDP), and elsewhere, the authority for your country.
13
International transfers
Nexa operates from Uruguay and serves customers in several countries, and several of the providers described above operate internationally. Personal data can therefore be processed outside the country where it was collected. If your organization needs the specific arrangements that apply to it, ask us and we will set them out for you in writing.
14
Changes to this policy
When this policy changes we publish the new version here and update the date at the top of the page. Material changes are announced to customer organizations.
15
Contact us
Questions about this policy, or about the data we hold: [email protected]. Related pages: the terms of use, which set the rules for using the platform, and the security page, which lists the controls the platform enforces.