Privacy Policy

Effective Date: 29/03/2024


Introduction


This privacy policy ("Policy") applies to your use of the Easy Invoice Maker mobile application ("App"). This Policy describes the information that we collect from you and how we use that information.


Information We Collect


We collect two types of information through the App:


Personal Information: We do not collect any personal information directly through the App. However, some information collected by AdMob, a third-party advertising service we use, may be considered personal information under certain laws. This information may include your device's advertising ID and other non-personally identifiable information used to serve you targeted ads.

Non-Personal Information: We may collect non-personal information about your use of the App, such as your device type, operating system, IP address, browsing activity within the App, and the date and time of your use.

Use of Information


We use the non-personal information we collect to:


Improve the App and understand how users interact with it.

Analyze trends and usage patterns.

Serve you with targeted advertising through AdMob.

AdMob

a

We use AdMob to display advertisements within the App. AdMob may collect certain information about your device and app usage in order to serve you with targeted ads.  Please refer to the AdMob Privacy Policy for more information about the data they collect and how they use it: https://support.google.com/admob/answer/6128543?hl=en


You can opt out of personalized advertising from AdMob by visiting the Google Ads Settings page: https://adssettings.google.com/


Your Choices


You can opt out of the collection of information by AdMob for personalized advertising by visiting the Google Ads Settings page: https://adssettings.google.com/


Security


We take reasonable steps to protect the information we collect from you from loss, misuse, and unauthorized access, disclosure, alteration, or destruction. However, no internet or electronic storage system is 100% secure.


Changes to this Policy


 We may update this Policy from time to time. We will notify you of any changes by posting the new Policy on this page.


 Contact Us


 If you have any questions about this Policy, please contact us at:


wanalg@yahoo.com

Comments

Post a Comment

Popular posts from this blog

chatgpt02 Range -> transferMode.dlna.org: Streaming

  1.  When to Use  transferMode.dlna.org: Streaming  for Range Requests The  transferMode.dlna.org: Streaming  header is  not required  for range requests directly. Range requests are typically used to request specific parts of a file, and whether or not you include  transferMode.dlna.org: Streaming depends on the type of content and the client’s behavior. For Streaming:  When you're serving content that is streamed continuously or progressively (such as video or audio), you may include  transferMode.dlna.org: Streaming  if you're delivering content in a way that supports immediate playback. For Range Requests:  If you're dealing with range requests (e.g., for video segments or chunks of a file), this is typically used to handle partial content delivery, and  transferMode.dlna.org  is  not required  for this. The  Range header in the request specifies the byte range to fetch. So, for a range reques...
Read more

chatgpt 01

 ok so when my application setavtransportURI and than panasonic is reponse SetAVTransportURIResponse OK. than my panasonic check head using this : HEAD /b420bda59b57dd1757169be92435a3d7 host : 192.168.88.235:26607 getcontentfeatures.dlna.org : 1 user-agent : Panasonic MIL DLNA CP UPnP/1.0 DLNADOC/1.50 so what to reponse to this ? ChatGPT said: ChatGPT When your Panasonic device sends a  HEAD  request after the  SetAVTransportURI  call, it is checking for metadata and DLNA-specific compatibility features of the requested resource. The server (your application) should respond appropriately with relevant headers to satisfy the device's expectations. Here's a breakdown of what you need to include in your response: Purpose of the  HEAD  Request The  HEAD  request is used to fetch  metadata  about the requested resource without transferring the actual content. It is often a precursor to a  GET  request, ensuring that the server ...
Read more