Privacy Policy
This worksheet sets out the privacy topics a Social API operator should document before publishing a public policy. It is an owner-input draft, not an effective policy. Complete each section with verified facts about the operator, the service scope and the actual data practices, then obtain appropriate review before publication.
Who operates the service
Record the legal entity that operates Social API, the service origin, the relevant establishment country, the scope of the service and its users, the effective date, and how this notice relates to the terms of service and any other notices. These are owner-input fields to be completed and verified; this worksheet does not itself identify an operator or establish an effective date.
Interpretation and definitions
In this notice, “we” refers to the operator identified in the section above, “service” refers to Social API and its documented scope, and “you” refers to an individual using the service or an authorized representative of an organization. An account is the user record used to access service features. Personal data is information relating to an identified or identifiable person. Usage data records interactions with the service. A device is the computer, phone or other system used for access. A service provider processes information on behalf of the operator. Cookies store information on a user’s device. Add any affiliate definition, social sign-in and connected-platform definitions, and jurisdiction-specific adjustments that actually apply.
Information you provide
List the personal data categories actually collected and the contexts in which they are collected. Specify whether account registration or contact requests require a name, email address or other identifiers, which fields are optional, and the consequence of not providing a required field. Add any purchase, support and user-content data categories that are actually collected.
Information collected through service use
Describe the automatic collection practices actually in place. Identify the technical and usage categories collected, such as IP addresses, browser and device information, pages used, timestamps, visit duration, identifiers and diagnostic events, only where they are collected. Add any mobile-device collection practices and the collection methods and purposes that apply.
YouTube and Google API data
State whether a YouTube integration applies. If it does, describe the YouTube functions and data accessed, the Google OAuth scopes and authorization flow, the Google API data purpose restrictions and Limited Use commitment where applicable, the Google permission revocation link and instructions, the Google Privacy Policy reference, and the YouTube data deletion process and timing. Complete only the items that reflect the actual integration.
Cookies and similar technologies
Describe the cookie, beacon, tag, script and email tracking practices actually used. Detail session and persistent cookies, browser and service-level cookie choices and their effects, and link to a separate cookie inventory identifying each technology, purpose, controller or provider and actual lifespan. Add the cookie notice link and consent controls that apply.
Cookie purposes and choices
Record the necessary cookie purposes, providers and lifespans; the cookie preference record purposes, providers and lifespans; the functionality cookie purposes, providers and lifespans; any analytics and marketing categories present; and how users can change or withdraw cookie choices.
Why information is used
Document the purposes that actually apply: service delivery and maintenance, account administration, contract and purchase performance, service and security communications, marketing and opt-outs, request handling, analytics, improvement and campaign measurement, and business transaction purposes where applicable. State the actual legal bases and choice details for each purpose.
Recipients and sharing
List the service provider recipients and their purposes, any affiliate sharing, any business partner sharing, any public interaction and other-user visibility, any consent-based sharing, and the actual sharing limitations and user controls.
How long information is kept
Set out retention periods or determination criteria by data category, the effect of account deletion on retention, legal obligation, dispute and contract retention exceptions, usage and diagnostic data retention, and backup expiry and deletion schedules.
Where information is processed
Identify the processing locations and recipient countries, the cross-border transfer circumstances, the applicable transfer mechanisms and safeguards, and how users can request transfer safeguard information.
Access, correction and deletion
Describe the applicable user rights, the self-service account and data controls, the access, correction and deletion request channel, the identity verification method, response timing and complaint options, and the deletion exceptions and retained data.
Business changes
Describe how data would be handled in a merger, acquisition or asset transfer, how notice would be given if data moves to a different operator or policy, and the actual user choices and legal restrictions that would apply.
Legal disclosures
Describe public authority request handling, the disclosure bases for legal obligations, rights, safety, fraud and liability, and any disclosure limitations and notice practices where applicable.
Security
Describe the verified security measures and their limitations, and the incident contact or notification process. Avoid guarantees of absolute security or controls that have not been implemented.
Children’s privacy
State the service age requirements and child audience policy, the child data collection practices, the parent or guardian contact and deletion process, and any applicable parental consent requirements.
Other websites
Describe the third-party link and service relationships and the third-party data handling responsibilities and notice links.
Changes to this notice
Describe the policy change publication method, the material change advance notice method and timing, and the effective date and version history practice.
Privacy contact
For privacy questions or requests, record the privacy contact name or team, the privacy contact email, the privacy request URL, any postal address and representative details required, and any supervisory authority or complaint route that applies. These are owner-input fields to be completed and verified before publication.
Social sign-in and connected services
List the sign-in providers actually offered and the social sign-in data and permissions requested. Distinguish sign-in information from access granted to connected publishing accounts. Describe any additional optional data sharing and the controls available to disconnect a connection or revoke access.