Someone asks to delete their data
Who is this for
Section titled “Who is this for”The operator or lead admin who receives a deletion request by message, e-mail or at the stand.
- Lead (form on the landing page):
/stickers_forget <number>in the sales group. Contact fields are erased at once. - Guest (station): admin panel → find the guest → Reset guest. Database rows go at once; photos go with the automatic clean-up within 72 hours of the photo.
- Backups age out within 14 days. The guest’s sticker pack lives in their own Telegram and only they can delete it.
- Reply to the person with the script at the bottom of this page.
Symptom
Section titled “Symptom”A person asks to delete “my data”, “my photo” or “my request”.
Likely cases
Section titled “Likely cases”| The person is… | Their data is in | Identify them by |
|---|---|---|
| An organiser who filled the landing form | leads (and possibly lead_repeats) |
Name, Telegram username or phone → the card #stickers_<n> in the group |
| A guest who took a photo at the station | users, sessions, jobs, files of the session |
Telegram username or name in the admin panel |
| Both | Both | Do both procedures |
A fallback message in the group (starting with ⚠️ Запасной канал) is not in the database. Delete that Telegram
message by hand, if Telegram still allows it, or edit it out.
Diagnose
Section titled “Diagnose”- Lead: search the group for the person’s username or the hashtag; or send
/stickers_leadwith no number and pick from the last five. - Guest: open
https://stickers.eventtalks.uz/admin, search by name,@usernameor Telegram id.
- In the sales group, as a lead admin:
/stickers_forget <number>. - The bot answers that the data is deleted and will leave backups within 14 days; the card turns into “data deleted”.
- Erased: name, Telegram username, phone, comment, the IP hash, and the same fields of any repeat requests. Kept: status history, language, advertising source, dates, and the free-text event date and guest count fields. If those contain personal details, tell the engineer — there is no command for them.
- A test lead (with «ТЕСТ» in the name or comment) can be removed entirely with
/stickers_forget <number> тест.
Details: Data erasure flow.
- Admin panel → the guest’s row → Reset guest → confirm. Alternative on the server:
python tools/reset_users.py <telegram_user_id>(dry run), then the same with--yes. - Deleted at once: the guest’s rows in
users,sessions,jobs. - Not deleted by this action:
- photo, face crop, sheets and debug images — removed by the clean-up loop within 72 hours of the photo, as long
as the
sticker-botservice runs; - the automatic database copy made just before the reset (
app.db.bak-<time>-resetin the data folder) — delete it by hand on the server once the reset is confirmed; - the audit-log entry of the reset (Telegram id and old pack links) and cost-accounting rows;
- log lines, rotated within 14 days; nightly backups, rotated within 14 copies.
- photo, face crop, sheets and debug images — removed by the clean-up loop within 72 hours of the photo, as long
as the
- The Telegram sticker pack is not ours to delete; tell the guest how to remove it in Telegram.
Verify
Section titled “Verify”- Lead:
/stickers_lead <number>shows “data deleted”; the export no longer contains the person’s contacts. - Guest: the admin panel search no longer finds the person. On the server, after 72 hours:
find /opt/ai-sticker-pack/bot/data/sessions /opt/ai-sticker-pack/bot/data/debug_sheets -type f -mmin +4320 | wc -lprints0.
What to tell the person
Section titled “What to tell the person”Send this only after step 3 of the guest procedure (the safety copy deleted by hand); otherwise the 14-day promise is not true for that copy.
Your data has been deleted from our system. Contact details [or: your photo records] were removed today; nightly backup copies disappear within 14 days. Your photo itself is deleted automatically no later than 72 hours after it was taken. The sticker pack is in your own Telegram account, where you can remove it at any time.
Prevent
Section titled “Prevent”- Keep the
sticker-botservice running after an event until 72 hours have passed. - Periodically remove old
app.db.bak-*copies from the data folder — see Known gaps, L10.
Where to go next
Section titled “Where to go next”Last verified: 2026-11-13 against ai-sticker-pack@b715418 and ai-stickers-landing@e350ff5.