Privacy Policy

• Your account: your name, email address, a picture you pick, your role and the teams you are in. Your password is stored only as a one-way hash.
• What you make: the research, papers, images, voice profiles, chats, comments and files you create or upload.
• Websites you add: when you add a website to Site Monitor, we read its public pages and posts.
• How the app is used: a log of actions taken in the workspace (for example “created a paper”) with the time and who did it, and the network address of sign-in attempts, so we can stop people guessing passwords.
• Cookies and browser storage: one cookie that keeps you signed in, and your preferences (such as theme and sounds) kept in your own browser. We use no advertising or tracking cookies.

Site Metric shows how a website performs in Google Search. A workspace admin may connect a Google account to it. When they do, we ask Google for:

• Read-only access to Google Search Console (the webmasters.readonly permission): the list of Search Console properties the account can see; their search numbers (clicks, impressions, click-through rate and average position, by day, device, country, search query, page and search appearance); their sitemaps as Search Console lists them; and, for the website’s pages, Google’s index status (whether it is indexed and why not, its canonical address, when it was last crawled), asked a page at a time.
• The account’s email address, so admins can tell which account each website is read through.

How we use it: only to show those numbers in Site Metric, for the websites an admin linked, to the signed-in members of the workspace who may open that website in the app (the person who added it, the people and teams it is shared with, and admins). We never change anything in Search Console: the access is read-only.

How we keep it: the access token Google gives us is stored encrypted (AES-256-GCM) on our servers. The search numbers are stored in our database, so the workspace can compare them over time (Google keeps only 16 months): the last 16 months when a site is linked, then each new week once Google calls it final; index status as each page is checked. They are deleted when an admin unlinks the site.

What we never do with it: we do not sell it, share it with third parties, use it for advertising, or use it to train or improve AI models. Nobody at Content Made Better reads it unless you ask us to (for example to fix a problem), it is needed for security, or the law requires it.

Taking access back: an admin can remove the Google account in the app’s admin console, which also asks Google to revoke our access, and unlink a site, which deletes its stored numbers. You can also revoke it at any time from your Google Account at myaccount.google.com/permissions.

Content Made Better’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• To run the app: sign you in, save your work and show it to the people you share it with.
• To do what you ask of the app’s AI features, search and page reading.
• To keep the app safe: stop abuse, investigate problems and keep backups.
• To tell you about things you started (for example that a build is done).

We do not sell personal information and we do not show advertising.

Some features rely on outside services. Each receives only what that feature needs, when you use it:

• AI model providers, reached through Vercel’s AI Gateway: the text, files and pictures you send to an AI feature.
• Image generation (Runware): the description and reference pictures of an image you ask for.
• Search and page reading (SearchAPI, ScrapingBee, scrape.do): the keywords you research and the public web addresses to read.
• Storage: files you make or upload, and our backups, are kept in our cloud storage bucket.
• Google: Search Console, as described in part 2.

Data from Google Search Console is never sent to AI providers or to any other service. We may also share information if the law requires it.

We keep your information while your account and its workspace are active. What you delete is removed from the app; copies in our backups are removed as the backups age out, within about 30 days. A connected Google account’s token is deleted as soon as an admin removes the account, and a site’s Search Console numbers when it is unlinked.

The app is served only over HTTPS. Passwords are hashed, and stored keys and tokens are encrypted. Access inside the workspace follows each person’s role and what has been shared with them, and every change is checked on our servers. No system is perfectly secure, but we work to protect your information.

You can see and change your name, picture and password in the app. To ask for a copy of your information, a correction or its deletion, write to [email protected].

Content Made Better is a tool for work and is not meant for children. We do not knowingly collect information from anyone under 18.

If we change this policy, we update the date at the top of this page. If a change is important, we tell workspace members in the app before it takes effect.