Blog Narrator privacy policy
Blog Narrator ("the App") is an app built for Wix. It is provided by Individual Entrepreneur ANTON ZAITSEV, registered at Georgia, Batumi city, Grigol Eliava street, N 24, trading as Jim Apps ("we"). For any question about this policy or your data, write to contact@jimapps.dev.
The short version
Blog Narrator reads the published posts of your Wix Blog to turn them into audio. It stores the audio files, the post titles and a fingerprint of each post's text, not the text itself. It reads no data about your contacts, members, orders or visitors, and the player sets no cookies and does no tracking. When you remove the App, everything it stored for your site is deleted. Your data is not sold, not shared with advertisers and not used to train AI models.
Who is responsible for what
For the content of your blog, you (the site owner) are the controller. We process it only on your behalf and only to provide the App. Payments for the Pro plan are handled by Wix; we never receive or store card details.
What the App can read
| Permission | What Blog Narrator reads with it |
|---|---|
| Read Blog | Published posts: ID, title, plain text, language and estimated reading time |
| App instance (granted to every Wix app) | Your site's app instance ID and whether it is on the free or the Pro plan |
The App cannot create, change or delete anything on your site, and it does not read draft posts, comments, members, contacts or any other data.
What the App stores
| Data | Details |
|---|---|
| Audio | One MP3 file per voiced post |
| Post records | Post ID, title, status (in line, voiced, waiting for the monthly limit, not voiced), length in characters and minutes, when it was voiced, and a SHA-256 fingerprint of the text, used to tell whether the post changed |
| Site record | The app instance ID, the plan and when it was last checked, and the install date |
The text of a post is read from Wix each time the post is voiced, passed to the speech service and then discarded; it is not stored.
Why
Only to provide the App: to voice your posts, to play the audio to your visitors, to show the status of your posts in your dashboard, to apply your plan, and to answer your support requests.
Your site's visitors
The player on your post page asks our server whether the post has audio and plays it from there. It sets no cookies, stores nothing in the visitor's browser and uses no analytics. To deliver the audio, Cloudflare processes technical request data such as the visitor's IP address and browser; request logs are kept for up to 7 days for troubleshooting and are not used to identify or profile visitors.
How long it is kept
| Data | Retention |
|---|---|
| Audio and post records | While the App is installed, until the post is deleted from your blog, or until you remove the App |
| Site record | Until you remove the App |
| Request logs | Up to 7 days |
Removing the App and deletion
When you remove Blog Narrator from your site, Wix notifies the App, and it deletes all audio and every record it stored for your site at once. Deleting a post from your blog deletes its audio. Deleted data cannot be recovered. To have your data deleted without removing the App, write to contact@jimapps.dev.
Storage and protection
On Cloudflare infrastructure (Cloudflare Workers, D1, R2 and Workers AI). All traffic is encrypted with TLS. Notifications from Wix are signed by Wix and checked by the App, and the dashboard page is opened only with a token from Wix, so one site cannot see another site's data. The audio of a published post is public, like the post itself.
Sub-processors
| Provider | Purpose |
|---|---|
| Cloudflare | Hosting the App, storing its data and audio, and turning text into speech (Workers AI) |
| Wix.com | Source of the posts, and billing for the Pro plan |
Your rights
You can ask for a copy of the data the App holds about your site, ask for it to be corrected, or ask for it to be deleted. Write to contact@jimapps.dev; requests are answered within 30 days. If you are in the EU, the UK or another country with a data protection law, you may also complain to your local data protection authority.
Changes
If this policy changes in a way that affects what is collected or how it is used, we announce it on this page at least 30 days before the change takes effect.