Google Play & Apple App Store Compliance Information

Last Updated: 12 September 2026

This page summarizes PalenquePH’s current app-store compliance framework for publishing and maintaining Palenque mobile applications on Google Play and the Apple App Store. It is intended as a reference for app submission, privacy disclosures, permissions, store metadata, and review preparation.

App-store declarations must reflect the actual production version of each app, including all enabled features, permissions, SDKs, libraries, payment providers, analytics tools, authentication services, and third-party integrations.

1. App Identity and Developer Information

Developer / Legal Entity: PALENQUE PH OPC
Brand: Palenque / PalenquePH
Website: palenqueph.com
Support Email: support@palenqueph.com
Corporate / Legal Contact: corporate@palenqueph.com

Principal Office:
Level 21, Unit 2116-17, Park Triangle Corporate Plaza, North Tower
32nd Street corner 11th Avenue, Bonifacio Global City
Taguig City 1635, Philippines

The exact app name, package/bundle identifier, subtitle, descriptions, and category should match the final production app and the corresponding Google Play Console or App Store Connect record.

2. Privacy Policy Requirements

Each published Palenque app must provide or reference an up-to-date privacy policy that accurately describes the app’s actual data practices.

The privacy policy should accurately explain, where applicable:

• What personal data is collected or processed.
• How the data is collected.
• The purposes for which the data is used.
• The categories of third parties with whom data is shared.
• Location and device-data processing.
• KYC and uploaded-document processing.
• Payment and payout information.
• Data retention and deletion practices.
• Security measures.
• Data-subject rights and privacy-request channels.

The public PalenquePH Privacy Policy and App Privacy Policy should remain consistent with the declarations submitted to Google Play and Apple.

3. Google Play Data Safety

The Google Play Data safety form must accurately describe the data collected or shared by the app, including data handled through third-party SDKs and libraries.

Before completing or updating the Data safety form, PalenquePH should verify:

• All data types transmitted from the app off the user’s device.
• Whether each data type is collected, shared, or both.
• The purpose for each data type.
• Whether collection is required or optional.
• Whether data is encrypted in transit, where applicable.
• Whether users can request deletion of their data.
• Data handled by all integrated third-party SDKs and libraries.

The Google Play Data safety declaration must be reviewed whenever app features, SDKs, permissions, or data practices materially change.

4. Apple App Privacy Disclosures

Apple App Store Connect requires PalenquePH to disclose the data collected by the app and by integrated third-party partners or SDKs, together with the purposes for which the data is used.

App Privacy responses must accurately reflect the current app version and should be updated whenever the app’s data practices materially change.

The App Store listing must include a valid Privacy Policy URL. Where applicable, PalenquePH may also provide a privacy-choices URL explaining how users can exercise privacy rights or request deletion.

5. Data Categories That May Require Disclosure

Depending on the actual production app and enabled features, categories that may require disclosure can include:

• Account information such as name, email address, and mobile number.
• Delivery or billing address information.
• Precise or approximate location information.
• Device or app identifiers.
• App activity and usage information.
• Uploaded photos, documents, identity records, or KYC information.
• Driver’s license, vehicle, or Vendor-business information where applicable.
• Order, delivery, transaction, payment-status, refund, and payout information.
• Crash, diagnostics, analytics, or performance information.
• Customer-support and communications data.

This list is illustrative only. PalenquePH must declare only the data actually processed by the relevant app and integrated third parties, while ensuring that no actual collection or sharing is omitted from the store disclosures.

6. App Permissions

PalenquePH should request only permissions that are necessary for current, disclosed app functionality. Permission requests should be made in context and should accurately explain why access is required.

Permissions that may be relevant, depending on the actual app, include:

• Location: delivery address assistance, dispatch, Rider navigation, delivery tracking, safety, or fraud prevention.
• Camera: identity or document capture, product photos, proof of delivery, or complaint evidence.
• Photos / Files: user-selected image or document uploads where supported.
• Notifications: order, delivery, security, account, Vendor, or Rider alerts.
• Authentication: account sign-in or supported biometric/security functionality where implemented.

PalenquePH should not request a permission merely because it may be useful in the future. The permission should correspond to a current feature that is accurately described in the app and store listing.

7. Location and Background Location

Location access must be limited to what is necessary for the actual feature being provided.

If the Rider App uses foreground or background location, PalenquePH must ensure that the actual collection, purpose, duration, user controls, app permission prompts, Privacy Policy, Google Play declarations, and Apple privacy disclosures are consistent.

Background location must not be described as being collected unless the production app actually requests and uses it.

8. Account Creation and Account Deletion

Where a Palenque app allows users to create an account, the app and related support/privacy process should provide an appropriate mechanism for account-deletion requests in accordance with applicable app-store requirements and law.

Account deletion does not necessarily require immediate deletion of every record where retention is required or permitted for legal, tax, accounting, transaction, fraud-prevention, dispute, safety, or other lawful purposes.

9. Authentication and Social Login

If PalenquePH enables Google, Facebook, Apple, or another third-party sign-in provider, the store disclosures and Privacy Policy must reflect the actual authentication data and third-party processing involved.

Social-login providers should not be listed in public disclosures unless the corresponding login method is actually enabled in the production app.

Where Apple’s App Review Guidelines require an equivalent privacy-preserving login option, PalenquePH should implement the required sign-in method before submission.

10. Payments and Financial Information

Payment methods and payment providers disclosed in the app-store listing or privacy materials must reflect the actual production payment flow.

PalenquePH should not claim that payment-card or e-wallet credentials are stored directly by PalenquePH unless that is technically accurate. Where payment information is collected or processed directly by an authorized payment provider, disclosures should reflect that arrangement.

11. Third-Party SDK and Service Review

Before each initial submission and material app update, PalenquePH should review all integrated SDKs, libraries, and third-party services that may collect, transmit, store, or otherwise process user data.

Examples may include, where actually enabled:

• Push-notification services.
• Maps and location services.
• Payment SDKs or gateways.
• Social-login or authentication providers.
• Analytics and crash-reporting tools.
• Advertising or attribution SDKs.
• Marketplace or app-builder SDKs.

PalenquePH remains responsible for ensuring its Google Play and Apple declarations include data collection or sharing carried out by integrated third-party code where the platforms require it.

12. Advertising and Tracking

PalenquePH should not state that the apps contain targeted advertising, ad networks, tracking, or attribution technologies unless those technologies are actually present in the relevant production app.

If advertising, tracking, or attribution technology is added later, PalenquePH should first review applicable consent, permission, App Tracking Transparency, Google Play disclosure, privacy-policy, and app-store requirements before enabling the feature.

13. Age Rating and Audience

Google Play and Apple age-rating questionnaires should be completed according to the app’s actual functionality, content, commerce features, user-generated content, communication features, and intended audience.

PalenquePH should not publish a fixed age-rating claim on this page unless it matches the rating assigned to the actual app version in the relevant store.

Account eligibility for marketplace transactions should also remain consistent with the PalenquePH Terms & Conditions and applicable Philippine law.

14. Store Listing Content and Assets

App-store listing information should accurately describe the app’s current functionality and may include:

• App name and icon.
• Short and full descriptions.
• Screenshots and promotional assets.
• Support and website links.
• Privacy Policy URL.
• App-access or reviewer credentials where required for review.
• Accurate descriptions of ordering, Vendor, Rider, payment, delivery, or account features actually available in the submitted version.

PalenquePH must not represent a feature as available in the store listing if that feature is not included or operational in the submitted app version.

15. Reviewer Access

Where the app requires authentication or access to restricted functionality, PalenquePH should provide valid review credentials, instructions, or other access information requested by the relevant app store.

Reviewer credentials should be limited to review purposes, maintained securely, and kept functional throughout the applicable review period.

16. Ongoing Compliance

App-store compliance is an ongoing obligation. PalenquePH should reassess its declarations and legal pages whenever there is a material change to:

• App features.
• Permissions.
• SDKs or service providers.
• Authentication methods.
• Payments.
• Location processing.
• Advertising or analytics.
• Account-creation or deletion flows.
• Data collection, sharing, retention, or security practices.

Google Play Data safety and Apple App Privacy responses should be updated when relevant practices change.

17. Relationship With Palenque Privacy Policies

This compliance-information page does not replace the PalenquePH Privacy Policy or App Privacy Policy. Those policies are the primary public-facing notices explaining how PalenquePH processes personal data.

If this page is maintained publicly, it should remain consistent with the actual production apps and the declarations submitted to Google Play and Apple.

18. Contact

For app-store, technical, privacy, or compliance questions:

Support Email: support@palenqueph.com
Corporate / Legal / Privacy Contact: corporate@palenqueph.com
Website: palenqueph.com