Privacy Policy
Effective 9 July 2026 · Radiant Horizons Hospitality Private Limited
Radiant Horizons Hospitality Private Limited ("we", "us", "our") operates the Chat Translator API and developer portal (the "Service"). This policy explains what data we collect, why, and how it's handled.
1. Who we are
Radiant Horizons Hospitality Private Limited
Second Floor, E-142, Gali Number 4, Vinod Nagar West
New Delhi, East Delhi, Delhi 110092, India
2. Data we collect
Account & sign-in
API keys are issued via Google Sign-In. When you sign in, Google shares your name, email address, and Google account ID with us. We store this against your issued key so we can identify you, enforce plan limits, and let you view your own usage.
API usage metadata
Every translation request records: request count, character counts (input/output), cache hit/miss, timestamp, and target language — aggregated per key, per day. This powers the usage dashboard and rate limiting. We do not build advertising profiles from it.
A sampled per-request log (the "Recent requests" view on your dashboard) stores only the language pair, input/output character counts, HTTP status, latency, and cache flag for each logged request — never the text of your messages. Entries are capped per account and expire automatically within 30 days.
Translated content
Text you send to /api/translate is processed to produce a translation and, for repeated identical inputs, may be held briefly in a server-side cache (Redis) to serve faster on cache hits and to speed up quality-feedback review. It is not sold, and not used to train third-party models. If you submit thumbs up/down feedback via the try-it widget, the source text, translated output, and your verdict are stored to improve translation quality.
Server logs
Standard infrastructure logs (IP address, request path, status code, latency) are retained briefly for debugging and abuse prevention.
3. How we use data
- Authenticate API requests and enforce per-plan rate limits
- Show you your own usage on the portal's "Your usage" dashboard
- Operate translation caching for speed and cost efficiency
- Improve translation quality using submitted feedback
- Detect and mitigate abuse (e.g. per-IP request throttling)
- Respond to support requests you send us
4. Third parties & sub-processors
We rely on the following providers to run the Service. Each processes data only as needed to provide their function:
- Google Identity Services — sign-in and identity verification
- Modal — hosts the translation compute and API
- Upstash / Redis — stores API keys, plan tiers, and usage counters
- Vercel — hosts this developer portal website
- GitHub — hosts our source code and public issue tracker
We do not sell personal data to any third party.
5. Data retention
Usage counters are kept for 30 rolling days for the dashboard, and monthly totals are kept for billing/plan purposes. Account identity (name, email, Google ID) is kept for as long as your API key is active. Cached translation text expires automatically. You can request deletion at any time — see Section 7.
6. Your rights
You can request access to, correction of, or deletion of your personal data, or revoke your API key, by emailing us (Section 8). We'll respond within a reasonable time and no later than 30 days.
7. Security
API keys are treated as secrets — you're responsible for keeping yours confidential. We use standard measures (TLS in transit, access-controlled infrastructure) to protect stored data, but no system is 100% secure.
8. Contact
Questions about this policy or your data: prabhat@hobostays.in. See also our Contact page.
9. Changes to this policy
We may update this policy as the Service evolves. Material changes will be reflected by updating the effective date above.