01 / Profile text & AI feedback
When live roasts are available, you can paste LinkedIn or professional profile text, or load a plain-text or Markdown file. The file is read in your browser; its text fills the profile field. Submitting a roast sends up to 12,000 characters of profile text to Roastly's server and then to OpenAI to generate feedback and rewrite suggestions.
Roastly reviews the copy you provide. It does not connect to your LinkedIn account or fetch your profile from LinkedIn. When the public submission form is paused, that form does not accept profile submissions.
The profile field clears after a successful result. The result stays in the active page so you can read or share it. Sharing is your choice: the website copies recap text to your clipboard, and the iPhone app opens the device share sheet. Anything you share is then handled by the app or recipient you choose.
02 / Accounts & subscriptions
If you create an account when sign-up is available, Roastly uses your email, password credentials, and any name you provide for authentication. Account records, authentication sessions, and any workspace or membership details are stored through Convex. These support sign-in and account features.
Where a subscription checkout is offered, it is handled on MadeThis rather than in Roastly's profile form. Roastly stores workspace plan and subscription status information. Payment information you enter at checkout is handled by MadeThis and its payment providers under their own privacy terms.
If you email support, the team receives your email address, message, and any attachments you include, and uses them to investigate and respond to your request.
04 / Storage & service providers
The current roast feature does not save submitted profile text or generated results as roast history in Roastly's database. This does not mean information is never retained elsewhere: hosting infrastructure processes requests, OpenAI processes submitted text, and configured analytics services process usage data. Service providers may retain technical logs or data under their own terms.
Roastly uses Vercel for hosting, Convex for account data and authentication, OpenAI for roast generation, MadeThis for platform services and checkout, and PostHog when analytics is configured. Processing may take place outside your country. OpenAI's handling and retention of API data are governed by its applicable service terms and settings; this policy does not promise zero retention or a particular training policy.
Account and support information can remain after you close a page. There is no automatic account-deletion tool or published fixed retention schedule in the current app. Contact the team to ask about the information associated with you.
05 / Your choices & requests
Choose what profile text to submit and whether to share a recap. Remove information you do not want processed before submitting. Closing or reloading the page clears the active roast view; it does not delete data held by service providers.
Depending on where you live, you may have rights to access, correct, or delete personal information, or object to or restrict its processing. Email the team to make a request, including an account-deletion request. We may need to verify that the information belongs to you before acting, and some information may need to be retained to meet legal obligations.
06 / Contact & updates
For privacy questions or requests, contact Roastly at team@roastly-hem.madethis.app. Please do not include passwords or unnecessary sensitive information.
We will update this page as the product or its data handling changes, with the revision date shown above.
Visit Roastly support