JoeyJooste

There is a single mention of html in their terms, and it just restricts wrapping cloudflares software. Could you link me the section where they restrict anything to html-only?

After reading this article carefully I have a few thoughts. Firstly you were knowingly in violation of TOS after they pointed it out to you. Violating their TOS is a fast way to have your account suspended.

Secondly I'm a little confused why they would require you to pay a year upfront? I would like to hear from cloudflare as to why they required this? It's pretty fair for them to ask you to pay a year in advance because of the risk that you carry as a gambling company.

Cloudflare needed you to have to enterprise plan to remove liability from them. It's not even a big request, they have specific pricing plans for a reason.

I was really excited for this. But I am largely disappointed. The flaws with Loom being closed source is that it's free tier is so horrible. Cap's free tier is just as bad. There is no reason why I would pay cap and not loom. The open source aspect is nice, but I also don't care about loom not being open source because whatever I post on loom is public anyway.

It would be really nice if cap was client side and allowed you to save the video directly to your drive. That way you could remove the paid tier and make it free for everyone. Adding 1 or 2 more options for webcam shape etc could also be a good selling point.

You do realize that cloudflare already offer this exact service for free?

Noted, the blog post didn't have enough care taken to the sales copy in it.

Very true, we make a number of requests to the LLM, specifically related to each field after data extraction. We will be better communicating this is our sales copy in the future, as we want to really show the value we are providing.

Thanks for the feedback, we have adjusted the pricing to $1 and have apple pay built in. Also applied a few of your other suggestions. Thanks

We are adjusting the landing page copy to better reflect how we handle user data. We don't collect any user data other than the Resume and the Google OAuth details. The resume gets deleted immediately after upload, and that data isn't used for training our or any third parties AI. The OAuth details are deleted a year after the account's last generated review.

Thanks for the input, we are looking into adding that in the coming months while we develop out different features and functionality.

We only store json web token data from google, which only gets added after you sign in or create an account. The only option right now to create an account is using google OAuth. We plan on adding more options later down the road. The data is stored in 2 cookies which are both essential for the use of the app.