Privacy Policy

The short version

Sheaf does not collect any data about you. It has no accounts, no analytics, no crash reporting and no advertising. On Android it does not even hold the INTERNET permission, so it cannot send anything anywhere — not by design decision alone, but because the operating system will not let it.

Your photos, your scans and your PDFs stay on your phone until you personally choose to share one.

Who we are

Sheaf is published by Oxon Pty Limited ATF Mullet Creek Investments Trust, trading as Ripteq ("we", "us"), in Australia.

Contact: support@ripteq.com.au

What data we collect

None.

We do not collect, receive, store, transmit or have any access to:

  • your name, email address, phone number or any other identifier

  • your photos, documents, scans or PDFs

  • your location

  • your device's advertising ID (Sheaf does not request one, and the AD_ID permission is not in the app)

  • usage analytics, event logs, session recordings or performance telemetry

  • crash reports or diagnostic data

There is no account to create and no way to sign in, because there is nothing to sign in to.

What data stays on your device

Sheaf stores the following in the app's own private storage area, which other apps cannot read:

WhatWhyThe original photo of each pageSo a scan can be re-cropped or re-straightened later without lossThe generated PDF for each projectThe thing you madeA local index (project names, page counts, page size, dates)So the app can list your projectsA regenerable cache of rendered previews and thumbnailsSpeed only; deleting it loses nothing

This data is created by you, used only to show you your own documents, and is deleted when you delete the project. Deletion is immediate and permanent — there is no cloud copy to recover from and no recycle bin.

Backups

On Android 12 and later, Sheaf is excluded from Google Drive cloud backup. Your scans are never uploaded to Google's servers as part of the system backup. Direct device-to-device transfer (moving to a new phone with a cable or the setup wizard) is permitted, because that transfer goes straight between the two handsets. On Android 8 to 11 the operating system cannot tell those two cases apart, so Sheaf is excluded from both.

On iOS, Sheaf's data is included in your device backup, which is encrypted and controlled entirely by you through Apple's settings. We have no access to it.

Permissions, and what each is actually for

Camera — to photograph a document. The camera preview is processed on your device to find the page edges. Frames are never recorded, never stored and never leave the device; only the still photo you deliberately capture is saved.

Photo library —

  • Android: Sheaf does not request permission to read your photo library. It uses the system photo picker, which runs outside the app and hands back only the individual files you select. Sheaf never sees the rest of your library.

  • iOS: Sheaf asks for photo library access so it can show you a photo grid inside the app. If you choose "Limited Access", Sheaf only ever sees the photos you selected. Either way, a photo is copied into the app's private storage only when you pick it.

Storage (Android 9 and older only) — needed by the system camera fallback on those versions to save a captured photo. Not used on Android 10 or later.

Sheaf does not request microphone, location, contacts, calendar or any other permission.

Sharing

The only way data leaves your device is when you choose it: tapping Share PDF or Save to device hands the file to the operating system's share sheet, and you pick where it goes — mail, messages, a cloud drive, a printer. Once you hand a file to another app, that app's own privacy policy governs what happens to it.

Generated PDFs are written with minimal metadata, so a PDF you share does not carry your device name or account name inside it.

Third parties

Sheaf contains no advertising SDKs, no analytics SDKs, no crash reporting SDKs and no social media SDKs. The third-party components it does use — .NET MAUI, SkiaSharp, sqlite-net and the .NET Community Toolkit — are open-source libraries for drawing, image processing and local storage. None of them collects or transmits data.

We do not sell, rent or share personal information, because we do not have any.

Children

Sheaf is a general-purpose utility and is not directed at children. It collects no data from anyone, including children.

Your rights

Privacy laws such as the Australian Privacy Act, the GDPR and the CCPA give you rights to access, correct, export or delete the personal information a company holds about you. We hold none, so there is nothing for us to disclose or delete on request. The data on your phone is yours: you can view it in the app, export any PDF through the share sheet, and delete any project or the whole app at any time. Uninstalling Sheaf removes all of it.

Changes to this policy

If Sheaf ever changes in a way that affects this policy, we will update this page and change the effective date above. A change that introduced any data collection would be described here plainly before it shipped.

Contact

Questions about this policy, or about Sheaf generally:

support@ripteq.com.au Oxon Pty Limited ATF Mullet Creek Investments Trust, trading as Ripteq — Australia https://www.ripteq.com.au

Appendix — Google Play Data Safety answers

Reproduced here so that the declaration in Play Console and this policy can be checked against each other without interpretation.

QuestionAnswerDoes your app collect or share any of the required user data types?NoIs all of the user data collected by your app encrypted in transit?Not applicable — no data is transmittedDo you provide a way for users to request that their data is deleted?Not applicable — no data is held by us. Users delete data in the app, or by uninstallingDoes your app contain ads?NoDoes your app use an advertising ID?No. The AD_ID permission is not declaredDoes your app collect device or other IDs?NoDoes your app collect photos or videos?No. Photos are read and processed on the device and never sent anywhereDoes your app collect files or documents?No. Generated PDFs stay in the app's private storage until the user shares oneDoes your app collect location, contacts, calendar, messages, health or financial data?NoDoes your app collect app activity, crash logs, diagnostics or performance data?NoThird-party SDKs that collect dataNone. The app uses .NET MAUI, SkiaSharp, sqlite-net and the .NET Community Toolkit, none of which collect or transmit data

Permissions declared in the Android release build, in full:

PermissionWhyandroid.permission.CAMERATo photograph a documentandroid.permission.WRITE_EXTERNAL_STORAGE (maxSdkVersion="28")Needed by the system camera fallback on Android 9 and older to save a captured photocom.ripteq.sheaf.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONInjected by AndroidX. Signature-level and scoped to the app's own package; it registers a non-exported broadcast receiver and grants no access to anything

There is deliberately no INTERNET permission, and no photo-library permission: the Android build reads photos through the system photo picker, which runs outside the app.