Privacy information

Updated September 11, 2026. This page describes data processing by Crypto Oracle Railway.

Google Sheets access

Only the bot owner connects Google. The connection requests read-only access to spreadsheets and is configured to read card titles and descriptions from the owner's Crypto Oracle catalog. It does not edit spreadsheets. Google credentials are stored as private service configuration on Railway.

Card titles and descriptions read from Google Sheets are sent through PuzzleBot to Telegram to answer card requests. Google credentials are not sent to OpenAI, PuzzleBot, or Telegram. Google user data is not sold, used for advertising, or used to train AI models. The service's use of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Card requests

The service receives a Telegram user identifier and the submitted card text or photo reference through PuzzleBot. OpenAI processes submitted card text or images to identify the card. Railway hosts the service and its persistent request queue. PuzzleBot and Telegram deliver the resulting card response.

Storage and control

Completed jobs clear their request and response content. Status and deduplication records are retained for seven days by default. Failed or uncertain jobs retain their content until resolved so delivery can be investigated. A local snapshot of the card catalog is also retained for migration verification and explicit fallback configuration.

The Google account owner can revoke access in their Google Account's third-party connections settings. For access or deletion requests, contact dev.romanv@gmail.com. OpenAI, Railway, PuzzleBot, and Telegram also process data under their own policies.