Auto Slideshow — Privacy Policy
Last updated: August 8, 2026
Auto Slideshow ("we," "us," or "the app") respects your privacy. This policy explains what happens to your data when you use the app.
How your content is handled
Auto Slideshow processes your photos, videos, and music entirely on your device. When you create a slideshow, the app reads the media you select and combines it into a video file — none of your photos, videos, or music are uploaded to our servers or any third party as part of this process.
In-app purchases
If you purchase a resolution unlock (720p, 1080p, or 4K export), your purchase is verified by sending the product ID and a purchase token/receipt (provided by the App Store or Google Play) to our verification server, to confirm the purchase is valid before unlocking the feature. This information is used solely to verify and grant your entitlement — it is not linked to your photos, videos, or any personal profile.
What we store
The app stores a small record on your device (which resolution unlocks you own) so you don't need to re-verify every time you open the app. We do not collect your name, email, contacts, or any other personal information, and we do not use analytics or advertising SDKs.
Third-party services
Purchases are processed by Apple's App Store or Google Play, subject to their own privacy policies. We do not control and are not responsible for their data practices.
Children's privacy
Auto Slideshow is not directed at children under 13, and we do not knowingly collect personal information from children.
Changes to this policy
We may update this policy from time to time. Changes will be posted on this page with an updated "Last updated" date.
Contact us
Questions about this policy? Email cjalbagaspar@gmail.com.
A couple of things worth flagging before you publish:
Not legal advice — this is a solid starting draft based on what the app actually does, but if you want airtight legal coverage (especially for EU/GDPR or California/CCPA users), it's worth a quick pass by a lawyer or a service like Termly/iubenda.
The purchase-verification disclosure assumes your backend (verify_purchase.php) only checks the purchase token and doesn't log/store anything beyond that. If your backend does more (e.g., logs IP addresses, stores purchase history in a database), the policy should mention that too — let me know what it actually does and I'll adjust the wording.
If you add analytics, crash reporting, or ads later, this policy will need an update to stay accurate — untrue privacy policies are one of the most common App Store rejection reasons.