Updated September 20, 2026
Privacy at Frank
Frank is Leo Kraz’s private workspace for managing his music, connected social accounts, personal plans and finances. Its management tools require owner authentication. Artist pages and listening links are public where the owner shares them.
Information the app handles
With the account owner’s authorization, Frank reads connected account profiles, posts, engagement statistics, comments and replies. This can include platform identifiers, usernames, comment text, timestamps and the post a comment belongs to. The owner can also import content records. The private workspace holds music files, plans and financial records from its connected services.
How information is used
Social data helps the owner review conversations, prepare replies, understand content performance and plan future posts. Replies are sent when the owner chooses to send them. When the owner requests an AI draft or analysis, relevant text and evidence are sent to OpenAI to produce that result. API requests ask OpenAI not to store the response. When the owner asks to sort comments, the comment text can be sent to TypeSafe AI for a category and confidence score. Frank does not include the commenter’s username or the post title in that Jev request. Processing is also subject to each provider’s API data policies.
Service providers and security
Frank uses Vercel for hosting, Neon for database storage, Cloudflare R2 for media, Inngest for background processing, OpenAI for requested AI assistance and TypeSafe AI for requested comment classification. Connected services process requests according to their own policies. Stored platform access tokens and sensitive record payloads are encrypted, and management routes require authentication. Social comments are not published as a public directory by Frank.
Public pages and email
Listening and artist pages can collect engagement events and email addresses submitted by listeners. Optional measurement follows the choices shown on those pages. Release notifications use the consent given for the release and include an unsubscribe link. If email delivery is enabled, the email provider processes the recipient address and message.
Retention and control
Records are kept to provide the workspace’s history and ongoing services until they are removed by the owner or an applicable deletion request is handled. Disconnecting a platform stops its future access; it does not automatically erase all previously imported history. Copies in operational backups can remain until the backup is retired.
Contact and deletion requests
For privacy questions or a request involving your information, contact privacy@leokraz.com. Include enough context to locate the record, such as your platform username and the relevant post URL. Do not send passwords or access tokens. See the data deletion instructions.