Privacy Policy
Who we are
Suggested text: Our website address is: http://cpress.in.
1. Introduction
Welcome to [Your Blog Name] (“us”, “we”, or “our”). We are committed to protecting your privacy and ensuring the security of your personal information. This Privacy Policy outlines how we collect, use, and share your information, particularly in relation to advertising services provided by AdSense and Ezoic.
2. Information We Collect
We may collect various types of information when you visit and interact with our website:
-
Personal Information: We may collect certain personally identifiable information, such as your name and email address, when you voluntarily provide it for purposes like subscribing to our newsletter or leaving comments on our posts.
-
Log Data: Like many websites, we automatically collect certain information whenever you visit our site. This may include your IP address, browser type, operating system, referring URLs, pages viewed, and the dates/times of your visits.
-
Cookies and Similar Technologies: We use cookies and similar tracking technologies to enhance your browsing experience and to provide targeted advertisements. Our ad partners, AdSense and Ezoic, may also use cookies to serve relevant ads.
3. Advertising Partners
We work with third-party advertising partners to display ads on our website:
-
Google AdSense: We use Google AdSense to serve ads when you visit our website. Google may use the information collected from cookies to provide you with targeted ads based on your browsing history. For more information on how Google collects and uses data, please refer to Google’s Privacy Policy.
-
Ezoic: We partner with Ezoic to optimize the placement and performance of ads on our site. Ezoic may collect and use certain data for this purpose. For more details, please review Ezoic’s Privacy Policy.
4. Your Choices
- You can control the use of cookies and similar technologies through your browser settings.
- You can opt out of personalized advertising from AdSense by visiting Google Ad Settings.
- Ezoic provides options to manage your data usage for ad personalization. You can find more information in their Privacy Policy.
5. Data Security
We take reasonable measures to protect your personal information. However, no data transmission over the internet can be guaranteed to be completely secure. You use our site at your own risk.
6. Changes to this Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page, and the effective date will be updated accordingly.
Comments
Suggested text: 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 anonymised 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
Suggested text: 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.
Cookies
Suggested text: 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 visit our login page, 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.
Embedded content from other websites
Suggested text: 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.
Who we share your data with
Suggested text: If you request a password reset, your IP address will be included in the reset email.
How long we retain your data
Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise 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
Suggested text: 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 your data is sent
Suggested text: Visitor comments may be checked through an automated spam detection service.
Personal and Sensitive User Data
Personal and sensitive user data includes, but isn’t limited to, personally identifiable information, financial and payment information, authentication information, phonebook, contacts, device location, SMS and call-related data, health data, Health Connect data, inventory of other apps on the device, microphone, camera, and other sensitive device or usage data. If your app handles personal and sensitive user data, then you must:
- Limit the access, collection, use and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy-conforming purposes reasonably expected by the user:
- Apps that extend usage of personal and sensitive user data for serving advertising must comply with Google Play’s ads policy.
- You may also transfer data as necessary to service providers or for legal reasons such as to comply with a valid governmental request, applicable law, or as part of a merger or acquisition with legally adequate notice to users.
- Handle all personal and sensitive user data securely, including transmitting it using modern cryptography (for example, over HTTPS).
- Use a runtime permissions request whenever available, prior to accessing data gated by Android permissions.
- Not sell personal and sensitive user data.
- “Sale” means the exchange or transfer of personal and sensitive user data to a third party for monetary consideration.
- User-initiated transfer of personal and sensitive user data (for example, when the user is using a feature of the app to transfer a file to a third party, or when the user chooses to use a dedicated purpose research study app), is not regarded as sale.
- “Sale” means the exchange or transfer of personal and sensitive user data to a third party for monetary consideration.
Prominent Disclosure & Consent Requirement
In cases where your app’s access, collection, use, or sharing of personal and sensitive user data may not be within the reasonable expectation of the user of the product or feature in question (for example, if data collection occurs in the background when the user is not engaging with your app), you must meet the following requirements:
Prominent disclosure: You must provide an in-app disclosure of your data access, collection, use, and sharing. The in-app disclosure:
- Must be within the app itself, not only in the app description or on a website;
- Must be displayed in the normal usage of the app and not require the user to navigate into a menu or settings;
- Must describe the data being accessed or collected;
- Must explain how the data will be used and/or shared;
- Cannot only be placed in a privacy policy or terms of service; and
- Cannot be included with other disclosures unrelated to personal and sensitive user data collection.
Consent and runtime permissions: Requests for in-app user consent and runtime permission requests must be immediately preceded by an in-app disclosure that meets the requirement of this policy. The app’s request for consent:
- Must present the consent dialog clearly and unambiguously;
- Must require affirmative user action (for example, tap to accept, tick a check-box);
- Must not interpret navigation away from the disclosure (including tapping away or pressing the back or home button) as consent;
- Must not use auto-dismissing or expiring messages as a means of obtaining user consent; and
- Must be granted by the user before your app can begin to collect or access the personal and sensitive user data.
Apps that rely on other legal bases to process personal and sensitive user data without consent, such as a legitimate interest under the EU GDPR, must comply with all applicable legal requirements and provide appropriate disclosures to the users, including in-app disclosures as required under this policy.
To meet policy requirements, it’s recommended that you reference the following example format for Prominent Disclosure when it’s required:
- “[This app] collects/transmits/syncs/stores [type of data] to enable [“feature”], [in what scenario].”
- Example: “Fitness Funds collects location data to enable fitness tracking even when the app is closed or not in use and is also used to support advertising.”
- Example: “Call buddy collects read and write call log data to enable contact organization even when the app is not in use.”
If your app integrates third party code (for example, an SDK) that is designed to collect personal and sensitive user data by default, you must, within 2 weeks of receipt of a request from Google Play (or, if Google Play’s request provides for a longer time period, within that time period), provide sufficient evidence demonstrating that your app meets the Prominent Disclosure and Consent requirements of this policy, including with regard to the data access, collection, use, or sharing via the third party code.
Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at [info@cpress.in].