Security

It is not possible to hack questions with our encrypted question engine. Questions are pushed during the competition, not kept on the device.

Every action of each user is logged, every answer is recorded, the prize earned from each contest is confirmed by the AI within 24 hours and added to user’s balance after the confirmation. Every withdrawal request is reviewed by the AI for fraud controls. The money is transferred after the confirmation. All questions go to all users completely at the same time, so players see all questions simultaneously. All competitions can be set up and edited from the admin panel.

Fraud controls are checked in real-time at the moment of each competition, and there are also daily controls by each metric for all competitions of the day.

PAYLOAD VIOLATION: In any way, if the expected event is outside the desired format, the event will not be accepted.

IDEMPOTENCY: System and / or user-related actions that may occur repeatedly are processed idempotently. (e.g. the same event arrives repeatedly)

TIMING: An event is expected to arrive in the expected time window. Except that time window, the incoming events are considered invalid by the system.

ACTION DUPLICATION CONTROL: If an event is sent more than once, the first event is processed but the second one is not processed. (e.g. multiple answers to a question)

UNEXPECTED EVENT: When an answer comes from a user who has no right to answer the question (e.g. eliminated users) this answer is not processed and logged.

OVERUSE: Uses that exceed wildcard usage limits are logged without processing.

The following anomaly metrics are collected on the basis of user [global], user [contest], contest. The collected metrics are checked daily by the agent between a certain time window. If any fraud is detected, it will be intervened without delay and the notification will be sent through the admin channel.

Metrics:

• Time events other than time Windows

• Event losses (not answering the previous question correctly, trying to answer the next question, etc.)

• Duplicate actions, multiple incoming events (response, wildcard usage etc.)

• Potential event loss

• Payload violation

Non-random event loss:

If an event loss is not consecutive (if event loss was observed in at most 1 previous question), it is tolerated even if it appears as if there is no right to answer the next question.

The metrics related to the tolerations are examined daily and the action is taken by anomaly detection, if any.

If Fraud is detected, it continues to be passively monitored, not to allow withdrawals, and the actions it takes and associated accounts are tracked. Active withdrawal requests are suspended and accounts are deactivated.

Competition awards are scheduled to be transferred to the account (Trivians account) after certain time provided for fraud checks.

At this stage, daily checks of metrics and logs are performed. Every day, anomaly metrics are checked with the agent, open accounts with fraud cases as a result of checks are taken into the passive examination process, and cashout transactions are suspended, related accounts are determined and the same transactions are applied.

Anomaly alarms are defined through application-wide metrics and instant checks are made.

After each contest, automatic reports are produced including contest, answer and awards statistics. These reports are observed with the agent.