Skip to content
Savedia
DownloaderFree & ProYour accountPrivacySafety

Savedia — Privacy Policy

Last updated: 2026-11-06

Savedia ("the app") is a personal archive/export helper you run on your own device. This policy explains what the app does with data. Savedia keeps downloaded media on your device, shows no ads, and does not use general-purpose usage analytics. Optional Savedia account and purchase services, when enabled in your build, use the providers described below. Public Post, Reel and web profile links may be resolved through Savedia's public-link service and Apify, as explained below. Instagram sign-in, Stories and requests known to require your Instagram session go directly to Instagram. Android media files download directly from its delivery network to your device. The optional web downloader relays requested public media through Savedia's Vercel service as described below. A safety report reaches support only if you explicitly review and send the optional email in your mail app. Android may back up eligible private app data if you enable a platform backup or device-transfer feature.

Who we are

Savedia is developed by HenrisLabs ("we", "us"). Contact: hello@henrislabs.com.

What data the app handles, and where it stays

  • Free web downloader. The web downloader does not require a Savedia account or subscription. When you confirm you are 16 or older and have permission to save the content, your canonical public Post, Reel or profile link is sent through Savedia's Vercel service to the public-link resolver described below. Surrounding pasted text and tracking parameters are removed. The web downloader does not ask for, receive or forward Instagram passwords or session cookies, and does not unlock private content, Stories or Highlights. Vercel streams requested public media and thumbnails from Instagram's delivery network to your browser; this uses temporary transfer buffers, not a persistent Savedia media library. Your browser controls the final save location.
  • Web downloader storage. A necessary, secure, HttpOnly cookie stores a guest capability for up to seven days. It is separate from a Savedia or Instagram account. Browser-local pending request references let you resume waiting without starting duplicate jobs. Stopping the wait or closing the page does not necessarily stop a job already started on the provider. The optional on-device history contains up to eight download-request records (link, creator, media count and time), not the media files. Clear history removes these records from this browser; it does not delete downloaded files, necessary pending-request state or provider records. Clearing site data removes the cookie and browser-local records. Shared devices can expose local history to other people using the same browser profile. No advertising or general-purpose analytics is added to this flow. If you sign in to your Savedia web account, a separate encrypted, Secure, HttpOnly, SameSite=Strict account cookie can connect eligible download requests to that account. It expires within fifteen minutes, or sooner when the account session expires, and is cleared when you sign out from the web account. The download page cannot read this cookie. Savedia verifies the account and payment status before using a subscription allowance. Guest and account request references are bound together to prevent duplicate requests across browser tabs; they do not identify your Instagram account.
  • Optional Savedia account. When account services are available and you choose to sign in, Supabase handles your email verification and account session. The Savedia service stores a separate profile (optional display name and creation date), membership, billing identifier and verified purchase access. Account tokens on Android are encrypted with Android Keystore and excluded from backup. Your Savedia identity is separate from Instagram sign-in. Free saving tools remain available without a Savedia account. Supabase Auth identities may be shared across HenrisLabs applications, while each application has separate access-controlled records. When you agree to the Fair Usage & Copyright Policy while authenticated with Savedia, the Savedia service records your user identifier, policy version, web/Android source and server timestamp. It does not receive your date of birth from this acceptance step.
  • Purchases, when available. Google Play handles purchases inside the Android app; a separate Savedia web purchase route may use Stripe. Payment details are entered with the payment provider, not stored in the Savedia Android app. The Savedia service stores provider purchase/customer references, product and entitlement status, expiry and verification/event records to validate purchases, restore access and process renewals, cancellations and refunds. For subscription-based service allowances, Savedia also keeps verified net payment amounts, currency, paid service periods, hashed payment references and request-cost reservations. These records prevent duplicate allowance use and reconcile refunds or failed renewals; they are not advertising analytics and are not sent to the media-resolution provider. To recheck a Google Play subscription when you use Savedia on the web, Savedia stores an encrypted Google Play purchase token in a private, access-controlled store, with separate encryption keys for live and test purchases. Only the payment-verification service can decrypt it for a request to Google Play; it is not exposed to the web downloader or Apify. This is a purchase-verification token, not your Google password or Instagram session. The token can be used until sixty days after the last verified subscription expiry to reconcile renewals and restore access. After that it is inaccessible and queued for scheduled deletion. Revoking the purchase, deleting the Savedia account or changing its billing ownership removes the stored encrypted token. Minimal transaction and dispute records may still be retained as described below. Google Play receives an app-specific hashed billing identifier. These services do not receive your Instagram password or session cookie, downloaded media, Vault tags or private notes. Google Play services may process purchase, device, network and diagnostic information under Google’s privacy policy. The payment SDK is initialized only when billing is configured and its services are used.
  • Your Instagram sign-in and session (only if you choose to sign in). The preferred sign-in uses Instagram's own page. If you choose the separately disclosed native fallback, the username/email/phone number and password you submit leave the device over HTTPS and are sent directly to Instagram to establish the same session; they are not sent to a Savedia-controlled server. Savedia stores the resulting session cookie in private device storage so it can request login-gated content on your behalf. Your password is never stored by Savedia. The local session remains across app restarts until you explicitly sign out. The backup-excluded local session/account cache stores the session/account identifier plus username, full name, avatar URL and user ID; it does not store an email address or phone number submitted in the sign-in field. If Instagram rejects the remote session, Savedia asks you to sign in again but keeps the local record until sign-out or replacement. The app resolves public post, reel and profile links without sending the session. Only when Instagram returns a genuine login or private-access wall may Savedia retry the metadata request with the stored session. Story metadata requires the signed-in session. Media CDN download requests never include the Instagram session.
  • Public-link resolution, when available. To improve reliability, the app may send a canonical Instagram Post or Reel link to Savedia's service hosted on Supabase. Tracking parameters and surrounding clipboard text are removed. The service asks Apify's Instagram Post Scraper to resolve that public link and returns public creator details, the caption and media delivery URLs. It does not send your Instagram password, session cookie, Savedia account token, downloaded files, private Vault notes or tags to Apify. A link's visibility may not be known in advance; restricted results are rejected, not unlocked. Stories and links already known to require your Instagram session use the existing direct connection instead.
  • Public profile pages and post count, when available. When you ask the web downloader to browse a public profile, Savedia may send its canonical profile link through Apify to the community-operated APISH Instagram API Actor to obtain a page of public post previews and a continuation for a later page. Each additional page is requested only when you ask for it. If the optional profile-total feature is available, Savedia may also ask Apify's Instagram Profile Scraper for the profile's reported post count. This is a snapshot of posts, not the number of photos or videos in them. A separate request for a post can resolve its downloadable media. These requests do not send your Instagram password, Instagram session cookie, Savedia account token or private Vault data to either Actor. Savedia keeps page-job references and continuations on its service with access restricted to the requesting guest; browser-local pending references support resuming an owned request. Apify's datasets may contain additional public profile and post information, even when Savedia retains only the reported count. The Actors and their providers process requests under their own policies, and Apify's separate storage retention described below applies.
  • Public-link service records. No Savedia account is required. The service issues an app-specific guest capability, valid for up to seven days, to keep requests separate and help resume interrupted work while reducing duplicate processing. The capability and pending request references stay in backup-excluded private device storage; only a token hash is stored on the service. Request and result records include the canonical link, public metadata, expiry and job status. Cached results expire within 15 minutes, often sooner. Scheduled cleanup removes these ordinary job records after 24 hours; an outage can delay physical cleanup. If profile pagination or profile counting is enabled, those profile request records and guest-bound idempotency references may be kept until one day after the guest capability's maximum seven-day validity. Expired media results are cleared sooner; a scheduler outage can delay deletion. For unresolved costs, provider run and dataset identifiers, actor and build details, and the provider account owner identifier may be retained without the profile link or guest identifier for reconciliation; the provider may still be able to link these identifiers to its own records. A keyed hash of the network address is used for registration throttling and removed after 24 hours by that cleanup; this application layer does not store the raw address. Hosting providers still process network information needed to serve requests under their own policies. Minimal cost and processing receipts for the guest service, without a guest identifier, target link, caption or media URLs, are kept for reconciliation; unresolved provider charges can remain until resolved. Reconciled guest-service receipts become removable after two calendar months. Separate subscription-allowance records retain account and billing identifiers, job and guest references, and verified payment and cost facts for reconciliation, including after ordinary guest/job expiry or account deletion. The short request-record retention schedule does not apply to these accounting records; there is currently no automatic deletion schedule for them. They do not contain Instagram links or media.
  • Apify processing and retention. Apify receives the public target link and processes its public result and run information. Its retention is separate from Savedia's cache: on the current Free plan the ten most recent runs can be retained for four months, with older unnamed storage following the plan's retention rules. Savedia does not name these storages for indefinite retention. See Apify storage retention and Apify's privacy policy. Contact us for requests concerning Savedia-initiated runs; clearing local app data does not itself delete provider records.
  • Downloaded media. Files you choose to download are saved to your device's gallery in the Savedia Pictures, Movies or Music folders. The independent Savedia app reads its own folders; earlier-version compatibility builds may also read their previous application folders so earlier downloads remain visible after an update. Savedia does not upload these files to an operator-controlled media service. Preview caches and saves are local; if you choose Share, Export or a separate backup service, the destination you choose handles that data under its own terms. These are public MediaStore files, so they may remain after you uninstall Savedia. Delete them in your gallery or a file manager if you want to remove them.
  • Clipboard link suggestion (local only). When Home resumes, Savedia may read the current clipboard to look for a recognizable Instagram or TikTok-shaped link and show a suggestion. It does not persist or transmit the clipboard contents. A recognized link is used off-device only after you choose the suggestion or start the related action. Android may show its normal clipboard-access notice. TikTok downloading remains unsupported in this release.
  • On-device history and settings. A local record of what you downloaded, the creators you saved, your theme/preferences, and an optional app-lock PIN (stored only as a salted hash, never the PIN itself). The session, PIN, and safety-control stores are excluded from Android backup/device-transfer rules. Other private preferences or history may be eligible for Android backup or device transfer because the app enables Android backup; the destination and retention are controlled by your device, operating system and account settings. Clearing app data or uninstalling normally removes private data on that device, subject to any separate platform backup you enabled.
  • Age eligibility and UGC safety controls. Savedia has a minimum age of 16, subject to any higher applicable requirement. The app checks a full birth date locally and asks for Terms, UGC-safety and Fair Usage & Copyright Policy acceptance. The birth date and selected report reason are not persisted or transmitted by the gate. The app stores the accepted policy version and local acceptance timestamp, plus local normalized blocked, hidden and reported creator/content identifiers; this safety store is excluded from Android cloud backup and device transfer. Report immediately hides locally. Block creator stops future Savedia recommendations, profile/previews, notifications, creator checks and worker saves, but does not block anyone on Instagram or delete downloaded files. Neither action sends data automatically. A separate optional button opens your mail app with a draft containing only the chosen reason label, known normalized creator/content identifier, a constructed public reference and a user-action note. No cookie, session, password, PIN or device ID is attached; you can cancel.
  • Optional Vault details. You can attach local tags, private notes, source links/creator reminders and a self-declared rights status to a saved Vault item. Savedia does not verify ownership, permission or a licence from these entries, and does not send them to us or to a server. You can clear them per item or with Settings → Clear Vault details without deleting the gallery media, Collections or download history. Unlike the session and PIN stores, these optional local details may be eligible for Android backup or device transfer when you enable those platform features.
  • Crash reports (local). If the app crashes, it writes a diagnostic report to private on-device storage with password, login/account, session-cookie, token and authorization values removed. A report retained from an older app version is scrubbed again before export. The report is excluded from Android cloud backup and device transfer. It is never sent automatically; it leaves your device only if you explicitly tap "Report last crash" and choose an app to share it with.

What we do NOT do

  • We do not provide cloud backup or a public hosting library for your media, sell data, or use data for advertising or tracking. Public-link metadata processing, temporary web media relay, direct Android requests and optional user-sent support email are described above.
  • We do not use Savedia advertising or general-purpose usage analytics. Payment-provider diagnostics and Instagram's own pages, requests and cookies are used only for the Instagram content and sign-in flows described above and remain subject to Instagram's controls.
  • We do not require a Savedia account for the existing free saving tools.

Network connections

The web downloader connects to Savedia's same-origin Vercel endpoints. Vercel connects to the Savedia resolver on Supabase and relays approved media from Instagram's delivery network. The resolver sends only the public target link to Apify. Vercel passes a signed client network address to the resolver solely to enforce guest-registration limits; the resolver stores its keyed hash, not the raw address. The job and provider retention periods above also apply to web requests. Hosting providers process network and diagnostic information needed to deliver and protect the service under their own policies, including Vercel's privacy policy.

The app connects to Instagram and its content-delivery network to fetch and download media you request. If you submit the optional native sign-in form, its username/email and password fields are transmitted directly to Instagram over HTTPS for app functionality; Savedia does not retain the password. Public Post and Reel resolution may first use the Savedia service and Apify without your Instagram session. When that service is unavailable, the existing direct resolver remains available; Android profile resolution is direct. Direct metadata requests are attempted anonymously first. If Instagram proves that access requires sign-in, the app may retry that request with the stored session. Story metadata requires the signed-in session. Media CDN requests remain credential-free. Access can still fail when Instagram changes or limits its web responses, rejects the stored session, or the account does not have permission to view the requested content. Remote rejection does not itself erase the local session before explicit sign-out or replacement.

When enabled, optional account requests also connect to the configured Supabase service. Purchase requests connect to Google Play or, on the separate web route, Stripe and the Savedia verification service. Providers process the network and transaction information needed to operate these services under their own policies. No media backup or cloud upload is provided.

Deletion and local controls

Savedia cloud account: Settings → Savedia account → Delete Savedia cloud account removes your Savedia profile, Fair Usage policy acceptance receipts and access. A minimal revoked membership/billing identity is retained to prevent automatic re-enrollment, and purchase/event records, subscription-allowance records and their payment and cost reservations remain for reconciliation and applicable record-keeping. This action does not delete a shared HenrisLabs Auth identity or another application’s records. Contact hello@henrislabs.com for account-data/deletion requests, including when you cannot access the app. We may need to verify your identity. Do not send passwords, session cookies or payment-card details. Active subscriptions must be cancelled with the provider separately; account deletion does not cancel payments.

Savedia sign out on this device clears its local Savedia session. It does not sign you out of Instagram, other applications or a browser session.

Sign out, Clear download history, Clear Vault details, Restore reported & hidden items, Unblock, gallery/file-manager deletion and clearing app data remove the corresponding local records or files under the limits described above. These local controls are not a universal deletion-request mechanism for data transmitted off-device. Savedia cannot delete data already processed or held by Instagram, an email provider, Android backup/device transfer or another platform. Use those services' own controls for their copies. For public-link service and Apify records initiated by Savedia, contact us using the address above; do not send a guest capability or other token in email.

Background behavior

Savedia periodically checks favourite creators when Android allows it (network available and battery not low). The check does nothing when you have no favourites. “Auto-save favourites' new posts” is off by default. If you turn it on, newly discovered posts from a favourite creator can be saved to your gallery in the background, up to five posts per creator per check.

The background check uses public, session-free requests only and stops when Instagram asks it to slow down.

Permissions

  • Notifications — to show download progress and optional new-post alerts.
  • Storage / media access — Savedia writes and reads only its own MediaStore media; it does not request broad access to your entire gallery.
  • Foreground service (dataSync) — to show progress while an in-app download queue runs after you leave the app.
  • Wake lock and boot-completed receiver — AndroidX/WorkManager uses these normal permissions to run and restore eligible scheduled work; neither grants access to personal content.

Each permission is used only for the purpose above and can be revoked in Android settings.

Acceptable use

Savedia is a personal archive/export helper for content you own or have explicit permission to save. It does not grant rights or verify permission. Respect copyright, privacy, other people's rights and the source platform's terms.

Age eligibility

You must be at least 16 to use Savedia and meet any higher age or other requirement that applies to you or the source platform. This product minimum does not replace local law or parental-consent requirements. Savedia is not designed for children under 16.

The current Fair Usage & Copyright Policy remains available from Settings and this website. A new policy version requires a new explicit agreement; simply continuing to use the app does not record agreement to a changed version.

Changes

We may update this policy; the "Last updated" date will change accordingly. Material changes will be reflected here before they take effect.

Contact

Questions about this policy: hello@henrislabs.com.

User and Child Safety Standards

Savedia

By HenrisLabs. Made for your personal media collection.

HomePrivacy PolicyFair Usage & Copyright PolicySafety StandardsContact