Kraymus · Waitlist & private preview
Service providers and connected platforms
This directory supports the Privacy Policy. It identifies current service providers by service or organization, without naming AI models. It is not a finalized customer Data Processing Agreement or a claim of provider certification.
Current services
| Service | Role and relevant information | Location and limits |
|---|---|---|
| Hostinger | Website/app hosting; technical requests and authorized app requests passing through the server. | Processing and log locations depend on the hosting contract and configuration; they are not all confirmed here. |
| Supabase | Authentication, database, file storage and backend functions; waitlist, account and workspace records. Supabase Auth prepares account, invitation and password-recovery emails and passes them to Cloudflare Email Sending for delivery. | Current project region: ap-northeast-1, Japan. This does not describe all logs, backups or support processing. |
| Alibaba Cloud AI services | AI processor for invoked generation/research features; prompts and context selected for the request, including relevant brand information or images. | Contract entity, processing locations, retention and training terms need confirmation before broader customer launch. Waitlist records and private video-test files are not submitted to this processor. |
| Cloudflare | Email Routing for messages sent to the kraymus.ai contact addresses, including replies to app@kraymus.ai: receives each message you send to one of those addresses, including your email address, the subject, content and attachments, and forwards it to our Google Workspace mailbox. Email Sending for Supabase Auth account, invitation and password-recovery emails: receives each message from Supabase, including the recipient’s email address, the subject, content and any sign-in or recovery link, and delivers it from app@kraymus.ai to the recipient’s email provider. | Messages pass through Cloudflare while being forwarded or delivered, and routing and sending activity (such as sender, recipient, time and delivery status) is logged. Processing locations and log retention depend on Cloudflare’s terms and configuration; they are not all confirmed here. |
| Google Workspace | Kraymus’s own mailbox: stores the messages forwarded from the kraymus.ai contact addresses so we can read and handle your request. It is separate from any Google account you connect to Kraymus. | Storage locations and retention depend on the Google Workspace account and Google’s terms; they are not all confirmed here. |
Platforms selected by you
Instagram, Facebook, Messenger, Threads, WhatsApp Business and Meta advertising; TikTok; Google and YouTube including Shorts; and planned LinkedIn and X connections are governed by their own terms and granted permissions. Possible later services include Pinterest, Bluesky and Snapchat. They are not all currently connected or generally available. A connected platform is not automatically a processor acting solely on Kraymus FZE’ instructions.
Slack and Telegram are optional private team-control channels, separate from customer social inboxes. When their bot setup and applicable provider checks are complete, they deliver authorized messages to Kraymus and receive any enabled private reply. They hold their own message copies under Slack’s Privacy Policy and Telegram’s Privacy Policy. Availability depends on actual installation, configuration and provider rules.
See Privacy Policy for the categories, purposes, connection status and choices. External privacy information includes Meta, WhatsApp, TikTok, Google, LinkedIn and X.
Changes and business use
Before broader customer launch, we must confirm the contracting entities, processing locations, retention, appropriate contractual protections and any required international-transfer measures. Business customers may need a Data Processing Agreement, instructions on their own responsibilities and a process for provider changes. A separate draft is being prepared; it is not in effect by virtue of this directory. We will update this page and provide required notice before material changes. Contact privacy@kraymus.ai.
Provider names are transparency information, not passwords or access credentials. This directory does not disclose secret keys or private account access. The actual recipients and processors must be identified to the level required by applicable privacy law, customer agreements and platform rules; a generic reference to “partners” cannot replace required disclosure. No AI model name is needed to explain the processor’s role.