Privacy, Operational Logs and Abuse Reports

[Eggy]

Privacy, Operational Logs and Abuse Reports

The service uses limited operational information to provide accounts, maintain security, diagnose faults and enforce service rules.

Information that may be recorded

Operational records may include:

• Account username and email address.
• Login times and login results.
• IP addresses.
• Browser or user-agent information.
• Dashboard actions.
• Network and vHost configuration.
• Support requests and staff responses.
• Payment or entitlement status.
• Security and abuse events.

These records may be used to operate the service, investigate faults and identify misuse.

IRC conversations

The service does not routinely monitor users' IRC conversations to track what they are doing on external networks.

Staff generally rely on:

• Reports received from IRC networks.
• Reports from affected users.
• WHOIS and connection information.
• Dashboard and configuration records.
• Relevant operational logs.

Where a supported feature such as IRC Inbox processes message data, that data may be handled as necessary to provide the feature.

WHOIS and configuration compliance

Account and network configuration may be checked to confirm that:

• The selected vHost is approved.
• Premium-only options are used only with entitlement.
• Account limits are being followed.
• The displayed WHOIS complies with service rules.
• Manual configuration has not bypassed restrictions.

Abuse reports

Reports should include enough information to identify the affected account, network and approximate time.

Reports may be shared internally with staff responsible for investigating the issue.

Serious or credible reports may result in temporary restrictions while evidence is reviewed.

Data protection

Do not post another person's private information publicly.

Support threads containing passwords, recovery links or other sensitive data may be edited or removed for safety.