RentSure — Privacy Policy
Effective date: 24 April 2026 | Version: 2.0 | App: RentSure | Bundle ID: com.jchen.RentSure
Important. This document is written to align with common Apple App Store and App Store Connect expectations (including clarity for the App Privacy questionnaire and Privacy Policy URL). It is not legal advice. You must ensure that your answers in App Store Connect, your in‑app disclosures, and this policy match the actual behaviour of each build you ship. If you add analytics SDKs, ads, account systems, or new data flows, update this policy and your store disclosures before release.
This Privacy Policy explains how information is collected, used, stored, disclosed, and protected when you use the mobile application RentSure (“the App”). The data controller for personal data that the developer processes in connection with the App is the individual developer who publishes RentSure on the App Store (referred to as “we”, “us”, or “the developer”). Trading / product name: RentSure.
1. Data controller & contact
- Controller type: Individual (sole) developer — not a separate legal entity unless you have registered one in App Store Connect.
- Developer / support contact (privacy & data rights): jianchen8863988@gmail.com
- App Store listing: RentSure — bundle identifier
com.jchen.RentSure.
For access, correction, deletion, portability, objections, or questions about this policy, email the address above. Include your country/region if you are exercising a statutory right so we can respond appropriately.
2. Scope & consistency with Apple
- This policy covers the RentSure app and data flows described here. It does not govern Apple’s collection or use of data when you use iOS, the App Store, or Apple’s payment systems — those are governed by Apple’s Privacy Policy and related terms.
- The App Privacy details shown on the App Store product page must be consistent with this policy and with what the App actually does. If there is any conflict, the actual behaviour of the shipped build and your App Store Connect declarations take precedence for accuracy; you should then correct the policy or the questionnaire.
- Tracking (Apple definition): We do not link data collected in the App with third‑party data for advertising or advertising measurement, and we do not share data with data brokers. We do not use the App to track you across other companies’ apps and websites for those purposes. Therefore we do not request the App Tracking Transparency (ATT) prompt for cross‑app advertising tracking in the current design described in this policy.
3. Summary (plain language)
- Local‑first: Most information you enter is stored on your device (e.g. local app storage).
- Optional network features: When you use features like fetch from link (listing preview) or subscription verification, limited data may be sent to a developer‑operated service endpoint (for example: the listing URL you paste, or subscription verification payloads).
- Payments: In‑App Purchases on Apple platforms are handled by Apple (StoreKit). We do not receive your full card number.
- Your controls: The App offers export and deletion of on‑device app data where implemented; see Section 10.
4. App Store “App Privacy” alignment (current design)
The table below is a disclosure aid. When you complete App Privacy in App Store Connect, select only the categories and purposes that match your build.
| Apple-style category |
What RentSure may involve |
Linked to you / tracking |
Purposes (examples) |
| User Content |
Rental profile inputs, saved listings (title, rent, description, source URL, metadata), feedback you record. |
Stored on device; linked to you only in the sense that it is your content on your device. Not used for “tracking” as defined by Apple. |
App functionality, product personalization (on‑device). |
| Purchase History (via Apple) |
Subscription / entitlement state via StoreKit (e.g. product IDs, transaction identifiers). |
Processed by Apple per Apple’s policies; the developer may receive limited entitlement signals needed to unlock features. |
App functionality, fraud prevention if you implement server‑side verification. |
| Diagnostics (if you later wire SDKs) |
UI toggles for analytics/crash consent exist; transmission to a third party should occur only if you integrate an SDK and respect consent. |
Declare in App Store Connect if any SDK sends diagnostics off‑device. |
Analytics / app functionality — only as implemented. |
| Identifiers (developer‑controlled) |
The App is not designed to collect advertising identifiers (e.g. IDFA) for the developer. If you add such collection, disclose it. |
N/A unless you add it. |
— |
| Location |
No continuous GPS background collection is described here. Any “location snapshot” in feedback is derived from listing/profile context you save, not precise ongoing location tracking by the developer. |
Not used for cross‑app tracking by the developer as described. |
App functionality (on‑device insights). |
Data used to track you (Apple App Store label): as of this policy version, the developer does not declare cross‑app/website tracking for advertising. If that changes, you must update App Store Connect, the App, and this policy.
5. Categories of data & purposes
5.1 Profile & preferences (local)
- Rental profile fields you enter; language, theme, onboarding flags.
- Purpose: provide the App, remember your preferences.
5.2 Listings & imported content (local; optional network)
- Listing text, numbers, URLs, and metadata you import or save.
- If you use “fetch from link” / preview features, the App may send a listing URL to a developer‑operated service endpoint for parsing; a local fetch fallback may occur.
- Purpose: screening, templates, reliability of preview.
5.3 Feedback & screening history (local)
- Feedback you log; lightweight keys or snapshots derived from profile/listing context at time of feedback.
- Purpose: on‑device insights and feature behaviour you expect from the App.
5.4 Subscriptions & verification (Apple; optional backend)
- Apple processes payment and related account data per Apple’s terms.
- The App may send transaction verification data (e.g. signed JWS, transaction IDs) to a developer‑operated backend if you enable that path.
- Purpose: unlock paid features, validate entitlement, reduce fraud.
- Manage / cancel subscriptions (Apple): https://support.apple.com/en-us/HT202039 (open Settings → Apple ID → Subscriptions on device, or use the support article for your region).
5.5 Notifications
- Local notifications if you grant permission and the App schedules reminders.
- Purpose: reminders you opt into.
5.6 Analytics & crash reporting (preference on device)
- Consent toggles may be stored on device.
- Until you ship an SDK that transmits data, do not mark App Privacy as collecting diagnostics/analytics from users. When you integrate a vendor, name the vendor, list data types, purposes, and link to their privacy notice.
5.7 Technical data
- OS‑level permissions, network requests you trigger, and other technical signals required to operate the App.
- Purpose: operate the App securely and as configured.
5.8 Photos, OCR, Share Extension, and clipboard (on device; user‑initiated)
- Photos permission (optional): If you tap the OCR / “recognize text from screenshot” feature, the App will request access to your photo library to let you select a screenshot.
- On‑device OCR: Text recognition is performed on your device using iOS system capabilities. The App does not upload your screenshot image to the developer as part of OCR in the current design.
- Share Extension (optional): If you share a URL or text from Safari or another app to RentSure, the Share Extension processes only the content you choose to share (for example: the page URL or selected text) and opens RentSure to prefill the Import screen.
- Clipboard (optional): The App reads the clipboard only when you tap a “Paste” button (for example: Paste URL / Paste description) to fill an input field. It does not continuously read your clipboard.
- Data export: If you export your data, the App packages your on‑device data into a JSON file and shows the iOS system share sheet so you can save it to Files or share it. The App does not automatically send the exported file to the developer.
6. Legal bases (EEA / UK / similar)
Where GDPR or UK GDPR applies: contract / steps prior to contract (Art. 6(1)(b)) for providing features you request; legitimate interests (Art. 6(1)(f)) for security, anti‑abuse, and improving the App without overriding your rights; consent (Art. 6(1)(a)) where required (e.g. optional notifications or optional analytics transmission).
7. Sharing & recipients
- Apple Inc. and affiliates: App Store distribution, In‑App Purchase, StoreKit, and related infrastructure.
- Developer‑operated services (if enabled): if a build uses a backend for listing preview or subscription verification, it is operated by the developer and should be accessed over HTTPS.
- We do not sell personal information (including as “sale” is defined under California law for covered businesses).
- We do not disclose personal data to data brokers for tracking as described in Section 2.
8. International transfers
Apple and any developer‑operated services (if enabled) may process data in multiple countries. Apple provides information about international transfers in its privacy materials. If the developer operates a backend in a specific country, users should be aware that network features may transfer limited data (such as listing URLs or verification payloads) to that jurisdiction.
9. Retention
- On‑device data: retained until you delete it in the App, clear app data, or uninstall the App, subject to device backups you control.
- Email support: correspondence may be retained for a reasonable period to resolve issues and meet legal obligations.
- Developer‑operated services (if enabled): retention is governed by the developer’s backend configuration and applicable law.
10. Your rights & controls
- In‑app: use export and delete features where available.
- Email us for other requests (access, correction, objection, portability) where applicable law grants rights.
- California residents (CPRA): You may have rights to know, delete, correct, and opt out of certain “sharing” for cross‑context behavioural advertising. We do not sell personal information as described in Section 7. To exercise rights, email us; we may need to verify your request.
- European Economic Area / UK: You may lodge a complaint with your local supervisory authority.
- Singapore PDPA: You may withdraw consent where processing is consent‑based (subject to exceptions), and may contact us to access or correct personal data we hold about you in our systems (e.g. support mailbox).
11. Security
We apply reasonable technical and organisational measures appropriate to a consumer app developed by an individual developer, including use of HTTPS for network calls where applicable and minimising data sent off‑device. No method of storage or transmission is completely secure. If we become aware of a breach affecting systems we control and your personal data, we will take steps consistent with applicable law, which may include notification.
12. Children
The App is not directed to children under 13 (U.S.) or the minimum digital consent age in your country (often 13–16). Do not use the App if you are below the age at which you may lawfully consent to processing in your jurisdiction. If you believe a child has provided personal data to us through support channels, contact us and we will delete it where required by law.
13. Automated processing
Screening and scoring features assist your decisions; they do not replace your judgment or legal advice. Where GDPR applies, you generally have rights regarding solely automated decisions with legal or similarly significant effects — contact us if you believe a specific feature falls in that category in your case.
14. Changes
We may update this Privacy Policy. The effective date and version at the top will change. Material changes will be reflected in the App or store listing where appropriate. Continued use after the effective date may constitute acceptance where permitted by law.