Your pages, your choice.

This policy describes Handinly for iPhone and iPad and this website. Handinly is developed by Felipe Miranda. Contact developer@felipejmiranda.com with privacy questions.

Scanning and local storage

Handinly uses your camera, with your permission, to scan documents. You can also select images using Apple’s Photos picker. Handinly receives only the images you select; it does not request access to your entire photo library or change the originals in Photos. Images stored only in iCloud may require Apple to download them before import. Document processing and PDF creation happen on your device. Scans, draft pages, thumbnails, PDF filenames, and saved PDFs are stored inside the app’s local storage. They are not automatically uploaded to a Handinly server. Handinly does not operate a document-storage backend.

Your device’s backup settings may include app data in Apple backups. Deleting a saved PDF moves it and its saved revisions to Recently Deleted in Settings. They remain on your device until you permanently delete them there. Damaged records may be retained in Recovery so you can export readable files. Interrupted camera transfers, photo imports, and unsaved captured pages may be retained in Recovery; you can add them to a draft or explicitly discard the captured batch there. Draft deletion removes the draft’s local pages. Export cache copies may remain until iOS removes them or Handinly cleans copies unused for seven days during a later export. Deleting the app removes its local library. Backups and exported copies are managed separately through Apple or the destination provider.

Sharing and Files

When you choose AirDrop, Save to Files, or another share destination, you select where to send a copy. A cloud location in Files may sync the PDF with that provider. The recipient or provider handles that copy under its own policies. Handinly cannot remove copies you have already shared.

Optional Google Drive

No account is needed to scan or save locally. If you connect Google Drive, Google’s official sign-in SDK authenticates your Google account. Handinly displays the account email and uses authorization tokens managed by the SDK to perform your requested uploads. Handinly requests the drive.file permission, which covers files you create or choose to use with the app, rather than unrestricted access to your Drive.

Choosing an existing folder opens Google’s folder picker and grants access to your selected folder. Handinly verifies the connected account and folder upload permission. It stores the folder name and ID separately for each account. Uploading sends the selected PDF, its filename, destination folder ID, and request information directly to Google Drive over HTTPS. Protected local session records allow interrupted uploads to resume; no access tokens are stored in these records. Old session records are cleaned during later uploads. Picker authorization tokens are used in memory to validate the selected folder. Documents may contain personal information you choose to include. PDFs remain in your Google account until you delete them there. Handinly does not receive these documents on a developer-operated server.

Google’s SDK privacy manifest declares account/contact information (name, email address, phone number), approximate location, user and device identifiers, usage data, and other data for app functionality and/or analytics. Actual processing depends on the Google services and account involved. Handinly does not request your contacts, phone number, or device location permissions. Google may derive approximate location from network information. See Google Sign-In privacy information and Google’s Privacy Policy.

Handinly uses Google user data only to provide the requested account connection and file export. It does not sell Google user data, use it for advertising, or use your documents to train AI models. Handinly’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting Google

Open Settings → Google Drive. Sign out removes the local sign-in session. Disconnect Google Drive revokes Handinly’s Google access and signs you out; an internet connection is required. You can also remove access in your Google Account connections. Disconnecting does not delete your Google account, local scans, or PDFs already uploaded to Drive.

Widgets, notifications, and preferences

Widgets open scanning or photo import without showing document titles or pages. If you enable PDF-ready notifications, Handinly asks iOS for permission and posts a local alert when a save finishes in the background. Alerts contain generic text and a local document identifier, not your assignment name or page contents. No notification server receives your documents. iOS limits background execution; force-quitting stops work.

Haptic, notification, and library-sort preferences stay on your device. Local save counts and dates help choose an appropriate moment for Apple’s optional App Store review prompt. They are not sent to a developer analytics service.

Ads, tracking, and support

Handinly has no advertising, in-app purchases, developer analytics service, or cross-app advertising tracking. The Google SDK’s own declared processing is described above. If you email support, your email address and message are processed to respond to your request. Avoid sending private homework or sensitive documents unless necessary. Ask by email if you want support correspondence deleted; retention required for security or legal obligations may still apply.

This website

This site provides product information and support. It contains no advertising or analytics scripts. Hosting and network providers process technical request information, such as IP addresses and browser headers, to deliver and secure the site. Email is handled through our email providers.

Children and changes

Handinly is designed for students and general document scanning, and is not directed at children under 13. We do not knowingly solicit personal information from children through support. Contact us if you believe a child supplied personal information. We may update this policy as the app changes; the effective date above identifies the current version.