BlackD Privacy Policy
This Privacy Policy explains how BlackD (the “Application”) accesses, uses, stores, and protects Google user data. The Application is a private tool used only by its owner for personal administrative automation.
Google user data accessed
With the owner's explicit authorization through Google OAuth, the Application may access:
- Gmail messages and metadata on a read-only basis; and
- Google Calendar events and calendar metadata on a read-only basis.
The Application does not request permission to send or delete email, or to create, edit, or delete calendar events.
How data is used
Google user data is used only to assist the owner with personal administrative tasks, such as reviewing relevant messages, identifying action items, and understanding upcoming calendar commitments. It is not used for advertising, profiling, or any unrelated purpose.
Data sharing and sale
Google user data is not sold, rented, transferred, or shared with third parties. It is not made available to other users.
Storage and security
OAuth client credentials and authorization tokens are stored securely on the owner's own server and are protected using appropriate access controls. Access is limited to the owner and the Application processes required for the personal automation. Reasonable safeguards are used to prevent unauthorized access, disclosure, alteration, or destruction.
Data retention and deletion
The Application retains OAuth credentials and any limited data needed for its operation only for as long as necessary for the personal administrative purpose. The owner may revoke the Application's Google access at any time through the Google Account permissions page. Stored OAuth tokens and locally retained Google user data can then be deleted from the owner's server.
Limited use
The Application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Changes to this policy
This policy may be updated if the Application's data practices change. The current version will remain available at this URL with its effective date.
Contact
Questions about this policy may be directed to the application owner using the contact information shown on the Google OAuth consent screen.