Skip to content
DAILY ICT Solutions

Security at DAILY ICT

Protecting access, credentials, and messaging data.

Our security approach combines application safeguards with careful operational practices. Security is an ongoing responsibility shared by our team, our providers, and every authorised user.

Access

Authenticated workspace

Operational pages require an authenticated account. Sessions and password controls help restrict workspace access to authorised users.

Credentials

Server-side secrets

Sensitive platform credentials belong in protected server configuration, not message content, templates, browser storage, screenshots, or client-visible pages.

Requests

Validation and integrity

Forms use request validation and anti-forgery protection. Incoming platform callbacks are rejected unless their signature is verified before their contents can affect local status.

Visibility

Minimal display

The interface shows operational identifiers and results only where needed. It does not display access tokens or app secrets.

Operations

Controlled logs

Diagnostic records should capture enough context to investigate failures while excluding credentials and reducing unnecessary personal content.

Response

Incident handling

We assess reported security events, contain exposure, preserve relevant evidence, remediate causes, and provide notices where applicable.

Your role

Keep your workspace secure

Technical controls work best when users follow sound access practices.

  • Use a unique password and keep account access limited to people who need it.

  • Never paste credentials into messages, templates, screenshots, or support emails.

  • Sign out from shared devices and report unfamiliar activity immediately.

  • Review recipients and content before sending, especially when using real customer data.

Report a security concern

Include a clear description, approximate time, and safe reproduction steps. Do not include live credentials or exploit personal data.

Email security team