Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/prevedimi/public_html/translate-4.me/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Privacy Policy – Milica Mirković

About us                                     

Our website address is: https://prevedi-mi.com. This is the official web presentation of Milica Mirković, a translator and a sworn interpreter.

What personal data we collect and why we collect it

Cookies

This site uses cookies – small text files that are placed on your machine to help the site provide a better user experience. In general, cookies are used to retain user preferences, store information for things like shopping carts, and provide anonymised tracking data to third party applications like Google Analytics. As a rule, cookies will make your browsing experience better. However, you may prefer to disable cookies on this site and on others. The most effective way to do this is to disable cookies in your browser. We suggest consulting the Help section of your browser or taking a look at the About Cookies website which offers guidance for all modern browsers.

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day

Analytics:

We use Jetpack, statistics tools of WP and AWStats. All information is anonymised and most often contain country of origin of the visit, referrals and pages visited in a session.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

This website uses WPForms which are GDPR compliant and set in a manner which prevents storing of personal data on the website. While using the form, some of their privacy policy may apply. Find out more at: https://wpforms.com/privacy-policy/

Who we share your data with

Private data you provide us with are shared only in the instances required for administrative, legal or security purposes. If you use third party embedded content their respective privacy policies apply.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile.  All users can see, edit, or delete their personal information at any time (except they cannot change their username).  Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you.  This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

We only keep the contacts which you submit to us willingly. You may request deletion of this information at any point. This does not include instances or any data we are obliged to keep for administrative, legal, or security purposes.

Additional information:

How we protect your data

We do not store your identifiable private information on this website. All data that was obtained with your consent is kept in local databases or cloud storages which are not connected with this website.

What third parties we receive data from.

Third parties present on this website which may provide additional data include:

  • Akismet Anti-Spam (https://automattic.com/privacy/)
  • Cookie Consent (https://catapultthemes.com/privacy-policy/)
  • Jetpack by WordPress.com (https://jetpack.com/support/privacy/)
  • WPForms (https://wpforms.com/privacy-policy/)

What automated decision making and/or profiling we do with user data

We do not use automated decision making and/or profiling we do with user data on this website. The data which is collected automatically is exclusively anonymised data pertinent to the statistic of website traffic.

What data breach procedures we have in place

Pursuant to the stipulations of the effective Montenegrin Laws and EU, namely GDPR, all breaches shall be reported to the competent authorities within 72 hours of their discovery.

Industry regulatory disclosure requirements

The Industry regulatory disclosure requirements are stipulated by the effective Montenegrin Laws, as well as EU regulations (GDPR) More information at: http://www.azlp.me/en/home and https://ec.europa.eu/info/law/law-topic/data-protection_en

 

error: Content is protected !!