SOC2C

Eyeball security & compliance

An overview of Eyeball's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).

SOC 2 statusSOC 2 · Listed
FrameworksNot listed
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerView

Security questions about Eyeball

Is Eyeball secure?
Security isn't a single yes/no, but Eyeball is SOC 2 compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
Does Eyeball have a bug bounty or vulnerability disclosure program?
Eyeball hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@eyeball.at or via a /security page.
Who are Eyeball's subprocessors?
Eyeball's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
Where does Eyeball host or store data?
Eyeball's hosting and data-residency details aren't listed on SOC2C yet. The company can add where it hosts (AWS, GCP, Azure) and which data it handles.
Where is Eyeball's trust center or security page?
Eyeball's trust center is at https://eyeball.at. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.

See Eyeball's full SOC 2 profile →