of the GriffonHub service
This English version is provided for convenience. In case of any discrepancy the Russian version prevails.
In short. We store account data in Russia and use it to run the Service: generations, payments, receipts, support. Requests to neural networks go to foreign model providers — without your contacts. Website visit statistics are collected by Yandex Metrica — only if you agree in the cookie banner. No ad trackers, we do not sell data. Work files are deleted after 30–60 days. The consent you give when signing up is a separate document: Consent to personal data processing.
Operator
Operator: Aleksandr Sergeevich Samosadov, professional income tax payer (self-employed), Russia
Tax ID (INN): 781431043508
Email for data requests: support@griffonhub.ru
Website: griffonhub.ru
Telegram bot: @griffonAibot
Support: “My requests” on the website and the “Help” button in the bot
1. General provisions
1.1.This Policy follows Russian Federal Law No. 152-FZ of 27.07.2006 “On Personal Data” and describes which personal data the Operator processes, why, where it is stored, who receives it and for how long, as well as users’ rights.
1.2.The Policy covers all parts of the GriffonHub service (the “Service”): the Telegram bot @griffonAibot, the Telegram mini app and the website griffonhub.ru. The account is shared across all of them.
1.3.The Policy is public and applies together with the Public Offer and the Terms of Service.
1.4.The Service is not intended for persons under 16. If you learn that a child has given us their data, write to us and we will delete it.
2. Whose data and what data
2.1.Data subjects are users of the Service and people who contact support or leave an email for a receipt.
2.2.We process only what the Service needs:
Telegram accountTelegram ID, username, name, interface language. The profile photo is shown in the mini app from Telegram and is not stored by us
Website accountname, email, password hash (we do not store the password), VK ID and Yandex ID if you sign in with them
Usagesign-up and last activity dates, Griffs balance and operations, plan and subscription, generation history (model, parameters, status, cost)
Contentrequest texts, uploaded images, audio and video, generation results; voice samples if you create your own voice for voiceover
Eva assistantmessages in the chat with Eva, attached images, Eva’s replies
Chat with modelsmessages, attached images (from your library) and documents (their text), model replies, the chosen model and mode, Griffs spent; files the model built at your request (PDF, Word, Excel) and their versions; for attached Word and Excel — also the files themselves, so that the model can edit them at your request
Presentationstopic and wishes, the text of an attached document, slides and finished files
Your charactersthe name and appearance description you set, up to three chosen photos from your library and a mark that the person in the photos agrees to their use. Visible only to you: a board opened via a link and its copies do not show them
Paymentsamounts, dates and statuses, email for the receipt, tax receipt number. For auto-renewal — the YooKassa payment token and card mask (e.g. “VISA •••• 4242”). We never receive or store the full card number, expiry date or CVC
Affiliate and giftswho invited whom, credited bonuses, bought and redeemed vouchers, gift message; visits via an affiliate link — an anonymous counter (whose link, day, website or bot), with no IP, cookies or data on who visited. On the affiliate page the inviter sees friends only under a masked name (“Al***”)
Supportrequests, support conversation and attached photos, contact email if provided
Public profile on the siteusername, profile name, profile photo, cover, published works (images, videos, music, voiceovers and sounds; a work with sound may carry your voice if you used your own recording) with the prompt and references you chose to show (attached photos and videos are shown; audio attached to a generation is not) and the categories the Service assigns; follows, followers, likes, bookmarks (visible only to you), collections (name, contents, visibility), blocks (visible only to you), views (without data on who viewed) and weekly profile statistics (visible only to you), decorations from cases (name tag, theme, charm, mascot guise, work frames, showcase; visible to everyone), reports on publications; records of consent to disseminate profile data and of consent of people in photos and videos
Consentswhich consents were given or withdrawn, document version, date, IP address and browser (User-Agent) at the moment of consent
Technical dataIP address and browser data in server logs, notification settings, whether the bot is blocked
Website visit statisticsonly with your consent in the cookie banner: Yandex Metrica cookie ID, IP address, browser, device, pages viewed, traffic source, clicks and scrolling, a recording of actions on the page (Webvisor). Passwords, email, sign-in and gift codes, support and Eva conversations are not recorded
2.3.We do not collect special categories of data (health, beliefs etc.) and do not use biometric data to identify anyone. Do not put other people’s personal data or images of people without their consent in requests.
3. Purposes and legal grounds
Account and sign-inperformance of the contract (Art. 6(1)(5) of 152-FZ)
Generations, Eva, chat with models, presentations, storing and showing worksperformance of the contract
Public profile and feed on the siteperformance of the contract; disseminating profile data — by separate consent (Art. 10.1 of 152-FZ) given when you make the profile public: consent text
Payment, subscription and auto-renewalperformance of the contract; auto-renewal is a term of the subscription, disclosed before payment
Receipts and tax accountinglegal obligation (Law 422-FZ, Russian Tax Code)
Support, refunds, claimsperformance of the contract and the Consumer Protection Law
Affiliate program and giftsperformance of the contract
Abuse prevention and securitylegitimate interest of the Operator and performance of the contract
Marketing emailsonly by separate consent, which can be withdrawn in account settings
Keeping consent recordsduty to prove consent was obtained (Art. 9(3) of 152-FZ)
Visit statistics and website improvement (Yandex Metrica)consent (Art. 6(1)(1) of 152-FZ) given with the “Accept” button in the cookie banner
3.1.We do not use data for targeted advertising (including Metrica data), do not sell it and do not share it for third-party marketing.
4. How data is processed
4.1.Operations: collection, recording, systematisation, accumulation, storage, clarification, retrieval, use, transfer (provision, access), depersonalisation, blocking, deletion, destruction.
4.2.Processing is mixed and mostly automated. We make no decisions with legal effects for you based solely on automated processing. Automatic screening of requests for prohibited content may reject a single generation — its cost is refunded, and screening of publications for 18+ content may unpublish a work or its shown references; you can appeal such a decision to support.
5. Where data is stored
5.1.The database with accounts, payments, history and consents is located in the Russian Federation (Selectel data centre). Personal data of Russian citizens is recorded, systematised, accumulated and stored in this database (Art. 18(5) of 152-FZ).
5.2.The application server, which receives bot and website requests and passes them to model providers, is in Sweden; it works with the database over an encrypted channel and keeps no copy of it.
5.3.Work files, uploads and attachments are kept in two object storages: in Russia (Selectel) and in the Netherlands (Scaleway). The website serves files from the Russian storage, the bot and mini app — from the Dutch one.
6. Who receives data
6.1.We share data only with those without whom the Service cannot be provided, and only as much as needed:
fal.ai (USA)request text and uploaded files — for photo, video, music and 3D generation, upscaling and speech recognition; images of publications and shown references (a frame for videos), profile photos and covers — for automatic 18+ screening; the text of published prompts — for automatic feed categories; messages to Eva and the chat with models with attached images and documents, the topic and document for a presentation — for a language model reply via OpenRouter. No contacts or names
ElevenLabs (USA)text for voiceover and voice samples — for speech, music and custom voices
OpenRouter (USA)language model router: receives requests of Eva, the chat with models, presentations and feed categories from fal.ai and passes them to the provider of the chosen model. We allow only US providers that do not train models on requests: OpenAI, Anthropic, Google, xAI and, for open models (DeepSeek), US hosts (DeepInfra, Together and others)
Perplexity (USA)the search query — if you turned on web search in the chat with models; under Perplexity’s API terms requests are not used to train models
YooKassa (Russia)amount, payment description, receipt email; you enter the card on YooKassa’s side
Telegram (international platform)bot and mini app messages, payments in Telegram Stars
Russian Tax Service, “Moy Nalog”amount and service name for the receipt; buyer’s email to send it
Unisender email service (Russia)email address and message text — for sign-in codes, receipts, support replies and marketing by consent
Yandex (Russia)SmartCaptcha — browser data for bot protection; Yandex ID — sign-in at your choice; Yandex Metrica — website visit statistics, only with your consent
VK (Russia)VK ID — sign-in at your choice: name, email and ID from VK
Cloudflare (USA)network intermediary in front of the website: IP address and request data — for attack protection and page delivery
HostingSelectel (Russia), AEZA (server in Sweden), Scaleway (Netherlands) — servers and files
6.2.Data may be provided to state authorities only upon a request based on law.
6.3.Model providers process requests under their own rules; under their API terms request data is not used to train models or is kept for a limited time. We send requests to language models with a no-training flag: OpenRouter passes them only to providers that do not use the data for training. We choose providers with such terms but do not control their systems.
7. Cross-border transfer
7.1.For generations, replies of Eva and the chat with models, presentations and website delivery, data is transferred outside Russia: to the USA, Sweden and the Netherlands. The Netherlands and Sweden provide adequate protection of data subjects’ rights; the USA is not on that list.
7.2.What goes abroad is the request content (text, files, messages to Eva and the chat with models) and technical data — without your name, email or payment data. The transfer is needed to perform the contract, and consent to it is part of the Consent to personal data processing.
7.3.The Operator notifies Roskomnadzor of cross-border transfer as required by Art. 12 of 152-FZ.
8. Retention periods
Generation result filesat least 30 days; deleted by a monthly cleanup, so in practice they live 30–60 days. The history record (request, model, status) remains
Videos and audio attached to a generationtogether with its result: deleted when you delete the work or by the monthly cleanup (30–60 days). Visible only to you unless you show the references in a publication; attached audio never goes into a publication
Account data, history, uploads, Eva and support conversationswhile the account exists
Your charactersuntil you delete the character or the account; while the character exists, its photos are not pushed out of a full library
Chat with modelsuntil you delete the conversation or the account. Texts of a deleted conversation, its documents and the files built in it are erased by the monthly cleanup — 30–60 days after deletion; only the spending records remain. Documents uploaded but never sent — also 30–60 days
Public profileshown to others while the profile is public; a private profile is visible only to you
Published worksa separate copy of the file and shown references — while the work is published and 30 days after unpublishing
Payments and receiptsas required by tax and accounting law (usually 5 years)
Consentswhile in force and 3 years after withdrawal — to prove consent was given
Server logsa limited time needed for diagnostics and security
Yandex Metrica dataWebvisor recordings — 15 days; visit statistics — in Metrica reports under Yandex’s rules. Metrica cookies live in the browser for up to a year unless removed earlier
8.1.After the account is deleted or consent is withdrawn, data is deleted or depersonalised within 30 days. Only data the law requires us to keep (payments, receipts, consents) is retained until those periods end.
9. Cookies and browser storage
9.1.On your first visit to griffonhub.ru (the website, home page and documents) a cookie banner is shown. If you click “Accept”, the Yandex Metrica counter loads: it sets its own cookies (_ym_uid, _ym_d and others prefixed _ym) and collects visit statistics, including a recording of actions on the page (Webvisor). If you click “Decline” or leave without choosing, the counter does not load.
9.2.You can change your mind at any time: the “Cookies” link in the page footer opens the banner again. On refusal, Metrica cookies are deleted. You can also opt out of Metrica on all websites with Yandex’s counter-blocking browser extension.
9.3.There are no ad pixels or other analytics counters. Cloudflare and SmartCaptcha may set cookies solely for attack and bot protection.
9.4.The website keeps in browser storage (localStorage):
gh.sessionsign-in token; valid for 30 days after your last visit
gh.themelight or dark theme
gh.draft.*draft of a generation request, removed after 30 minutes
gh.refreferrer code from an affiliate link, 30 days
gh.onboardonboarding tips already shown
gh.oauth.nextwhere to return after VK or Yandex sign-in
gh.pay.trackingan unfinished payment — to show its status
gh.cookiesyour choice in the cookie banner: consent to Yandex Metrica or refusal
gh.socialwhether the public part of the site is on — so the feed doesn't flicker on load
gh.configthe service's models, prices and form settings (the same for everyone) — so pages open without waiting
gh.tariffsGriffs pack prices (the same for everyone) — so the pricing page opens instantly
gh.featureswhich site sections are open to you — so the menu doesn't rearrange on load; no name, email or balance
gh.viewera random browser number — so a work view is counted at most once a day; not linked to the account
gh.feedViewprompt feed view: cards or images only
gh.soundOffcase sounds are muted on this device
gh.caseCdpause between case openings (5 seconds)
gh.caseFastfast spin of the case reel
gh.banners.hiddenhome page banners you closed — so they are not shown again
gh.boards.*where you left off on a board (canvas position and zoom) and board tips you closed
gh_langlanguage of the griffonhub.ru home page
9.5.This data stays on your device; you can remove it by signing out or clearing site data in your browser.
9.6.The Telegram mini app keeps on your device (localStorage):
gh.meyour profile from the previous launch: Telegram name and username, balance, plan, chosen look and the sections open to you — so the app opens instantly, without a splash screen. Refreshed on every launch, never used for another Telegram account and kept for no more than 7 days
gh.seasonthe state of the seasonal event from the previous launch (quest progress) — for the same purpose and on the same terms
gh.configthe service's models, prices and form settings (the same for everyone) — so screens open without waiting
gh.banners, gh.banners.ratiohome screen banners (the same for everyone) and their image proportions — so the screen doesn't rearrange on load
gh.banners.hiddenbanners you closed — so they are not shown again
griffon_lang_chosenthe language has been chosen — the language picker no longer appears
griffon_sound_offapp sounds are muted on this device
griffon_season_offseasonal decorations are turned off on this device
griffon_voice_prefsthe last voiceover model and its settings
case_cd_untilpause between case openings (5 seconds)
case_fast_spinfast spin of the case reel
griffon_season_previewseasonal event preview — administrator only
9.7.This data stays in Telegram on your device. In addition, while the app is open (sessionStorage), it remembers which screen you were going to if it had to reload after an app update.
10. Your rights
10.1.You may (Art. 14, 20, 21 of 152-FZ):
- learn what data of yours we process, why, who receives it and how long we keep it;
- require inaccurate, outdated or unnecessary data to be corrected, blocked or deleted;
- withdraw consent to data processing and, separately, to marketing emails and auto-renewal;
- require your account to be deleted;
- appeal the Operator’s actions to Roskomnadzor (rkn.gov.ru) or in court.
10.2.Send a request to support@griffonhub.ru or via “My requests” on the website. So that we can identify you, write from your account email or from your account in the Service, or give your Telegram ID. We reply within 10 working days; this may be extended by 5 more working days with a reason.
11. Withdrawing consent and deleting the account
11.1.To stop marketing emails, use the toggle in account settings or the link in an email. Auto-renewal and the saved card are switched off in “My subscription” on the website, in the mini app or in the bot.
11.2.Withdrawal of consent to data processing and account deletion — by request to support@griffonhub.ru or via “My requests”. The Service cannot work without processing data, so withdrawal means deleting the account and ending the contract.
11.3.Unused purchased Griffs and the unused part of a subscription are then refunded under section 9 of the Public Offer. Download the works you need beforehand — they cannot be restored after deletion.
11.4.You can also delete the account yourself in profile settings on the site. The profile is hidden immediately, auto-renewal is turned off and the account is deleted after 30 days; until then the deletion can be cancelled. Remaining Griffs are cancelled with such deletion — unused purchased Griffs can be refunded by request before deletion.
11.5.Consent to disseminate profile data is withdrawn with the “Public profile” switch in settings: the profile and works stop being shown to others immediately.
12. How we protect data
- data travels only over secure channels (HTTPS/TLS); the database is reachable by the application only via an encrypted WireGuard tunnel and is closed to the internet;
- passwords are stored only as a strong salted hash (scrypt);
- files in storage are private and served via temporary signed links;
- server access is key-based and limited to few people; administrator actions are logged;
- backups, regular software updates, rate limiting and bot protection;
- payment and generation records are kept in our own database in Russia; the only third-party analytics is Yandex Metrica, and only with your consent.
12.1.In case of a data breach the Operator notifies Roskomnadzor within the time limits of Art. 21 of 152-FZ and informs the affected users.
13. Changes to the Policy
13.1.The Policy may be updated when the Service or the law changes. A new edition is published on this page with its date. If the purposes or the set of shared data change, we tell you in the Service and, where needed, ask for new consent.
13.2.The previous document “Consent to personal data processing” (May 2026) is replaced by this Policy and the Consent.