Contact
Pick the channel that matches the request.
Sales, partnerships, privacy, security, and hiring stay separate so the right person reads it. No sales overhead.
Channels
Sales
Evaluating a plan, team rollout, or pricing questions before committing.
What to include
Current workflow, team size, publishing setup, and estimated story volume.
Address
hey@ermisai.comPartnerships
Content licensing, distribution agreements, or syndication conversations.
What to include
What content is in scope, who may use it, territory, and under what rights.
Address
hey@ermisai.comPrivacy & GDPR
Data subject requests, consent questions, or data processing enquiries.
What to include
The request type and the account or organisation involved.
Address
privacy@ermisai.comSecurity
Vulnerability reports or questions about the security posture.
What to include
The issue, affected path, reproduction steps, and estimated impact.
Address
security@ermisai.comGeneral
Anything that does not fit another channel.
What to include
Context and what kind of response you need.
Address
hey@ermisai.comCareers
Role enquiries when we are actively hiring.
What to include
The role area, location constraints, and relevant portfolio or newsroom work.
Address
hey@ermisai.comRouting notes
Commercial topics
Sales and partnership messages work best when they describe the team, workflow, and commercial scope clearly.
Privacy and security
Privacy requests and security reports work best when they identify the account, organisation, affected path, and the specific issue.
General and hiring
General and careers messages should include enough context to route them to the right person or team.