new app store assets ready for relese

2026-11-04 15:49:26 +00:00
parent 280a459377
commit fd42aad1de
68 changed files with 757 additions and 10 deletions
@@ -0,0 +1,17 @@
+# Age rating, content rights and encryption worksheet
+
+Complete Apple's current questionnaire in App Store Connect; the store calculates the rating. Do not invent a rating from this worksheet.
+
+Current app features: server administration and monitoring; no ads, chat, social posting, gambling, contests, purchases, loot boxes, health advice or built-in public torrent search. It displays metadata supplied by the user's server. It does not display downloaded media contents. External documentation/support links do not provide an in-app unrestricted web browser.
+
+Assess the questionnaire's user-generated-content and web-access wording against this private-server model. Do not claim the app is specifically designed for children or that it provides parental controls.
+
+Content rights: only manage content the user is authorised to access/share. Review the third-party-content-rights declaration rather than blindly answering Yes or No. No licensed film/music artwork or third-party logos are used in the screenshot pack. Sample transfer names are fictional and describe open/public-domain content. qBittorrent is mentioned to identify compatibility; no affiliation is claimed.
+
+Brand ownership: Tarnax is an existing Marvel fictional place name. Earlier naming searches are not trademark clearance. The release owner must settle commercial naming rights and similar marks before submission. The artwork is an original generated orbital T, with no Marvel imagery. The generated PNG is the raster master; no hand-drawn vector master is claimed.
+
+Encryption audit: networking uses Apple's URLSession/HTTPS, Keychain and LocalAuthentication; no custom encryption protocol or third-party crypto SDK was found. ITSAppUsesNonExemptEncryption is set to false on that basis. The account owner must confirm export-compliance answers and update them if encryption use changes.
+
+Business/account fields still require owner decisions: seller/trader status, legal/address details requested by Apple, tax/banking/agreements, price, distribution territories, content rights and any regional requirements. Do not put private identity documents into this pack.
+
+Accessibility Nutrition Labels: the app uses Dynamic Type, VoiceOver labels, semantic colors, native controls and non-color graph distinctions. Claim only features verified with Apple's required testing. Full VoiceOver, Voice Control, contrast and physical-device testing have not all been completed; do not tick every accessibility feature automatically.
@@ -0,0 +1,22 @@
+# App Privacy assessment
+
+Proposed production label: **Data Not Collected**, subject to the owner confirming the final service arrangements and the statements below.
+
+Code audit for this pack found no ad/tracking/analytics SDKs and no developer-hosted API. The user chooses an HTTPS server; credentials live in the device Keychain; lock and navigation settings stay local; transfer history stays in memory. The production default server is now blank.
+
+This proposed answer assumes the developer does not collect and retain user data through a bundled/default backend, telemetry, support SDK or other integration. A user-configured server is controlled by that user or their chosen operator; its practices must be assessed separately if the developer also operates that service. Apple defines collection in terms of data transmitted off-device and retained beyond serving the request; merely transmitting an authentication request is not automatically the same as declaring retained analytics.
+
+Support email is user-initiated external correspondence. The public policy explains it. Review Apple's optional-disclosure criteria against your actual handling rather than assuming all support collection is automatically exempt.
+
+Before answering App Store Connect:
+- Confirm whether you or your partners operate any server used by ordinary users.
+- Confirm no analytics, crash-reporting or advertising SDK has been added since this audit.
+- Review any retained server access logs and account records if you operate the backend.
+- Include all third-party SDK behavior if dependencies are added.
+- Confirm the published privacy policy accurately describes support correspondence.
+
+Bundled privacy manifest: no tracking, no declared collected-data types, UserDefaults required-reason API CA92.1 for app-local settings. This manifest is not a substitute for the App Store Connect privacy questionnaire.
+
+Sources:
+https://developer.apple.com/app-store/app-privacy-details/
+https://developer.apple.com/documentation/technotes/tn3183-adding-required-reason-api-entries-to-your-privacy-manifest
@@ -0,0 +1,28 @@
+# Tarnax 1.0 submission checklist
+
+## Assets prepared by this pack
+- App Store icon and derivative brand assets.
+- Six iPhone and six iPad screenshots in raw and designed versions.
+- Device-footage app preview videos and poster frames.
+- English UK and US listing text with field-length validation.
+- Support email, ready-to-host support/privacy/usage pages, and an in-app privacy/support section.
+- Bundled privacy manifest and export-compliance declaration based on the audited app.
+- Review notes, access checklist, age/privacy/compliance worksheets.
+- App Store archive/export tooling; no upload or publication is performed.
+
+## Owner actions before submission
+- [ ] Resolve Tarnax naming/trademark rights.
+- [ ] Choose the final public website URLs; publish website/ over HTTPS and test every link. Enter the support and privacy URLs in release-config.json and App Store Connect. A local HTML file is not a public policy URL.
+- [ ] Confirm the privacy-policy operator name, support handling and final App Privacy answers.
+- [ ] Provide a dedicated external reviewer server and login details; see reviewer-access-checklist.md.
+- [ ] Enter reviewer contact phone, pricing, territories, trader status and required legal/tax/banking details.
+- [ ] Create the App Store Connect app record for net.absdev.Tarnax; confirm Tarnax is available in the chosen locales.
+- [ ] Complete age-rating, content-rights, encryption and accessibility questionnaires accurately.
+- [ ] Validate the App Store export/archive in current production Xcode/App Store Connect. An SDK/beta runtime compatibility fix was needed during development; confirm the SDK used is accepted for store upload.
+- [ ] Upload the **App Store** build, not the direct-install Ad Hoc IPA. Wait for processing and inspect warnings.
+- [ ] Confirm screenshot appearance and cropping on Apple's upload preview, then select one coherent set per locale/device. Do not upload both raw and designed copies as duplicate screens.
+- [ ] Test build 8 on physical iPhone and iPad: fresh login, saved login, Face ID, cancellation/retry, background lock, graph, library, Files import, server preferences and offline recovery.
+- [ ] Confirm public support/privacy URLs are accessible without login.
+- [ ] Prefer manual release for the first version; submit for review when all blockers are cleared.
+
+Run `python3 appstore/tools/validate.py` for local asset checks. The report distinguishes valid assets from outstanding owner/account requirements. It cannot guarantee App Review acceptance.
@@ -0,0 +1,20 @@
+Tarnax is a native remote control for a user-configured qBittorrent server. It does not download torrent contents to the iOS device, provide a content catalogue, perform public torrent searching, or sell a hosted download service.
+
+An existing qBittorrent Web UI API endpoint with trusted HTTPS is required. The developer must supply a dedicated, reachable reviewer server and credentials in App Store Connect's App Review Information fields. Do not submit this pack until those details have been supplied and tested from outside the local network.
+
+Review procedure:
+1. Open Tarnax and enter the supplied HTTPS server address and Web UI credentials. Leave the optional proxy fields empty unless separate proxy credentials are supplied.
+2. Tap Connect securely.
+3. Home shows active downloads, transfer speeds and a live graph. History is recorded during this session; wait several refreshes to see new samples.
+4. Library contains all transfers. Search, filter, sort and open the dedicated sample transfer.
+5. Open Files to inspect progress and file priorities. Use a disposable sample if testing mutations.
+6. Add accepts a magnet link or a .torrent file and uploads the request/file to the server. The developer should provide a lawful sample and ensure it remains available throughout review.
+7. Settings exposes the preferences returned by the server, with confirmation before changes and read-back afterwards. Avoid altering the reviewer server's networking/authentication configuration during review.
+8. Optional Face ID/device authentication is in Settings. It uses the system policy, with passcode fallback. Normal authentication shows a branded waiting view; cancelled authentication offers Unlock.
+9. Disconnect/change server and Forget saved credentials are in Settings. Privacy policy and support contact are available there too.
+
+Live updates pause while the app is backgrounded or locked. No background-download entitlement is requested. There are no ads, subscriptions or in-app purchases in this version.
+
+Screenshots and preview videos use the actual app interface with fictional lawful transfer data in an isolated simulator fixture. That fixture is not included in the App Store app. The shipping binary has no baked-in demo credentials.
+
+Review contact email: mark.gregory@abbeysoftware.com
@@ -0,0 +1,12 @@
+# Reviewer access — complete before submitting
+
+- [ ] Create a dedicated qBittorrent review account/server containing only disposable, lawful sample transfers. Do not expose your production library.
+- [ ] Provide a trusted HTTPS URL reachable from outside your network, with API v2 enabled.
+- [ ] Supply username and password directly in App Store Connect's App Review Information, not in this repository.
+- [ ] Supply proxy credentials separately only if needed. Avoid interactive browser-only SSO.
+- [ ] Provide a lawful magnet or .torrent sample that remains available, plus a sample small enough to test quickly.
+- [ ] Test login, Home, Library, details/files, adding, pause/resume and a harmless setting from an external network.
+- [ ] Keep the server running and the credentials valid throughout review.
+- [ ] Enter your reviewer contact telephone number in App Store Connect.
+
+The screenshot fixture is local sample-data tooling, not an approved substitute for reviewer access to the shipping app. Apple requires full access and running backend services for review.