Ext Ops Panel
Open dashboard
Permissions and history

Is Text2Calendar - Event Creator safe to install?

Text2Calendar - Event Creator asks for 6 browser permissions and 2 site patterns. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Text2Calendar - Event Creator

Chrome extension by Ahmet Rıza Ateş · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 5 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Runs its code on every site
Data collection
2 kinds of data declared
Upkeep
Updated 304 days ago
Audience
57 users · 4.5/5

What data it declares

The developer declares that it collects these kinds of data:

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Specific sites only: 2 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 2 site patterns.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: Runs its code on every site.

The typical extension there declares 3 browser permissions; this one declares 6 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

57 users

Users
unchanged since 31.08
50-61 · 28 readings
  1. 2026-08-3157
  2. 2026-09-0459
  3. 2026-09-0960
  4. 2026-09-1058
  5. 2026-09-1357
  6. 2026-09-1561
  7. 2026-09-1760
  8. 2026-09-2156
  9. 2026-09-2557
  10. 2026-09-2659
  11. 2026-09-2857
  12. 2026-10-0856
  13. 2026-10-1055
  14. 2026-10-1356
  15. 2026-10-1654
  16. 2026-10-1750
  17. 2026-10-1855
  18. 2026-10-1956
  19. 2026-10-2055
  20. 2026-10-2157
  21. 2026-10-2256
  22. 2026-10-2357
  23. 2026-10-2458
  24. 2026-10-2556
  25. 2026-10-2857
  26. 2026-10-2955
  27. 2026-10-3057
  28. 2026-10-3157

What the store shows

The listing says it offers in-app purchases.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

Ahmet Rıza Ateş. This listing has been in the store since 2025-12-21 and was last updated on 2025-12-31.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Event to Calendar Runs its code on every site · 3 permissions 11 users ★ 5.0
  2. Page to Calendar Runs its code on every site · 2 permissions, 2 site patterns 6 users
  3. supercalendar Access to specific sites only · 3 permissions, 2 site patterns 2 users (last published figure)

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Text2Calendar - Event Creator access?
Specific sites only: 2 match patterns. It declares 6 browser permissions.
What data does Text2Calendar - Event Creator collect?
The developer declares that it collects these kinds of data: Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Text2Calendar - Event Creator asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Text2Calendar - Event Creator publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-10-31.

Back to Text2Calendar - Event Creator · Alternatives to Text2Calendar - Event Creator

Where the data comes from: how the catalog is built