1. Who we are
PumpPerks is operated by [full legal entity name] (“PumpPerks”, “we”, “us”). Our registered or business address is [postal address]. For privacy questions, contact [privacy contact email]. Update the visible contact link before publishing.
2. Information this service uses
Describe only information that the live website or app actually collects. Depending on the features you launch, this may include:
- Account details such as [phone number / email / name — keep only what applies].
- Offer and transaction details needed to check eligibility or show reward status, such as [fields, source and purpose].
- Location data if a person chooses to use nearby-station features. State whether it is approximate or precise, when it is accessed, and how to disable it.
- Device, app, diagnostic or usage information such as [actual identifiers, logs, analytics SDKs].
- Information a person provides when contacting support.
Do not list payment-card or financial-account details unless your service actually receives or processes them; identify the payment provider and exact flow if it does.
3. How we use information
Set out the actual purposes, for example: creating and securing an account; displaying location-relevant offers; checking a transaction against campaign rules; communicating reward status; answering support requests; preventing abuse; and measuring or improving the service. Add the relevant choice or permission for each optional use.
4. Offers, stations and service providers
Explain what transaction or eligibility information is exchanged with participating fuel stations, payment providers, reward partners, hosting, analytics and customer-support providers. Name the providers or link to an up-to-date list where appropriate. State what each recipient does and whether it may use information for its own purposes.
5. Permissions and choices
Explain how users can manage location, notifications, marketing messages, analytics choices and account preferences. Describe how to withdraw optional permissions and what feature may stop working as a result. Provide the actual in-app and device-setting steps.
6. Retention and security
State the real retention periods or criteria for account, transaction, support and diagnostic records, including any records retained after account closure and why. Describe security controls accurately; do not promise that transmission or storage is perfectly secure.
7. Requests and complaints
Explain how people can request access, correction, deletion or other choices available to them, how identity is verified, and the response channel and expected process. Grievance contact: [name / role, postal address and monitored email or web form]. Make sure this contact is staffed and the process matches your actual obligations and practices.
8. Children
Describe the actual intended audience and age controls, if any. Add the real process for handling a child’s information and guardian requests. Do not claim the service is designed for children unless that is true.
9. Changes and contact
Explain how material changes will be announced and how the effective date will be updated. For privacy questions, write to [privacy contact email].
Before launch, have this draft checked against the service’s real data collection, vendor contracts, app permissions and applicable requirements. No company-specific facts or data practices were supplied for this draft.