How mkrecho.ai handles data

Last updated: July 13, 2026. This policy describes the current validation app and avoids promising automated fulfillment or retention periods that are not implemented.

What mkrecho.ai is

mkrecho.ai is a web app that helps AI SaaS builders turn build updates into X drafts, draft libraries, analytics, and growth recommendations. The public landing page can live on SherKhanCodes while the product home uses mkrecho.ai.

Information we collect

When you join the waitlist, we collect the email address, X handle, niche, and product note you choose to provide. When you sign in, we receive the account details returned through X and Supabase Auth, such as your user ID, handle, display name, and avatar when available.

Workspace and draft data

Supabase stores workspace profiles, brand-voice preferences, generated candidates, saved drafts, feedback events, connected-account records, tracked posts, and metric snapshots. Older browser-local drafts may remain in localStorage until you migrate or remove them. Clearing browser storage can delete drafts that have not been migrated.

OpenAI processing

mkrecho.ai uses the OpenAI API to generate and refine content. A generation request may include your prompt, niche, audience, voice preferences, edited examples, and relevant authorized evidence. Generated outputs and operational metadata may be stored in your workspace so the product can present drafts and evaluate quality. mkrecho.ai does not opt API data into cross-user training through the application.

X sign-in and analytics monitoring

Signing in with X creates your mkrecho.ai session; it does not connect analytics or grant posting permission. If you separately connect read-only monitoring, mkrecho.ai stores encrypted OAuth credentials server-side and uses the authorized X API scopes to read your account details, posts, recent evidence, and available performance metrics. The current monitoring connection does not request permission to post, reply, like, follow, or send direct messages.

Third-party services

mkrecho.ai currently uses Vercel for hosting, Supabase for authentication and workspace storage, OpenAI for content generation, X for user-authorized account data, and Resend for internal waitlist notifications. Each provider processes data under its own terms and privacy practices.

Retention and controls

A workspace owner can record export and deletion requests in Privacy & Data after privacy-control storage is configured. Recording a request does not immediately generate a file or delete data; fulfillment is manually reviewed. This policy does not promise a fixed retention or fulfillment period. Aggregate learning is off by default, requires separate reversible opt-in, and no aggregate-learning pipeline is currently active. Disconnecting X removes the app's stored monitoring connection through the available disconnect workflow; workspace records remain separate.

Contact

For privacy questions, contact @SherKhanCodes on X while the product is in early validation.