Home/Docs/Platform & Safety/Pilotrav Security, Data and Deletion

Pilotrav Security, Data and Deletion

Pilotrav stores data needed to operate accounts, including encrypted game credentials, proxy details, settings, logs, and support data. Account deletion removes related bot data, but user deletion is requested through Support or e-mail and handled within 30 days, subject to legal retention.

Requirements

  • Ownership of user/account
  • Support or e-mail for full user deletion

Limits

  • Owner can view game password in Edit Account
  • Account deletion does not delete proxies
  • Registration records may remain until user deletion
  • No self-service user deletion

What it does

Stored data includes e-mail, hashed panel password, plan data, trial-abuse IP/device data, terms acceptance, encrypted game credentials, proxies, settings, tasks, logs, tickets, and payments. Owner Edit Account can pre-fill the owner game password. Account deletion cascades to its bot data but leaves purchased proxies. Registration jobs can retain encrypted lobby passwords until user deletion.

How it works

Stored data includes e-mail, hashed panel password, plan data, trial-abuse IP/device data, terms acceptance, encrypted game credentials, proxies, settings, tasks, logs, tickets, and payments. Owner Edit Account can pre-fill the owner game password. Account deletion cascades to its bot data but leaves purchased proxies. Registration jobs can retain encrypted lobby passwords until user deletion.

Pilotrav works only while an account runs. Each cycle reads game state, does eligible work, then waits a randomized delay. A proxy, credentials, plan, game queue, page, or Travian rule can prevent an action. Check Logs and the game page after important changes. Times for schedules and plans use UTC+3. Automation carries account risk; no setting removes that risk.

Settings

UI labelWhat it doesDefaultRange
PasswordGame loginRequiredMax 128 chars
Delete accountRemoves game dataManualPer account
Delete logsRemoves logsManualPer account

Setup in 4 steps

1. Open the relevant Pilotrav page.

2. Check the requirements below.

3. Save the listed settings.

4. Confirm the next result in Logs.

Requirements

▸Ownership of user/account
▸Support or e-mail for full user deletion

Limits and what it does not do

▸Owner can view game password in Edit Account
▸Account deletion does not delete proxies
▸Registration records may remain until user deletion
▸No self-service user deletion

Common problems

For full deletion, request it through Support or e-mail. Update game password in Edit Account and restart. Deleted logs are removed.

Related features

getting started · proxies · anti detection and human behavior

Frequently asked questions

When does this take effect?

It takes effect after its prerequisites are met and the running bot reaches the relevant account during normal processing. Network conditions, game pages, existing work, plan access, and configured delays can postpone it. Check the exact log and Travian page rather than assuming an immediate result.

Will this remove automation risk?

No. Pilotrav documents configured behavior and operational limits, not a safety or game-result guarantee. Travian rules, account status, server responses, proxy quality, and timing remain outside the feature. Use the service only where you accept the associated account risk.

What should I do after an error?

Read the exact customer-visible message first, then check the prerequisite it names: running bot, proxy, credentials, plan, verification, or game building. Correct one issue at a time and retry only where instructed. Include recent logs in a Support ticket if the cause remains unclear.

Related docs

Pilotrav Getting Started GuideTravian Bot ProxiesTravian Bot Human Behavior Settings

Last updated:

Ready to try Pilotrav?