# The App Exit Test — full text

> The App Exit Test is an independent publication about evaluating software, trial plans, permissions, export, migration, and reversible adoption. It is not an app store, software developer, reseller, review platform, support desk, security auditor, or continuation of any former entity associated with this domain.

# How to Cancel an App Subscription and Keep Proof

> To cancel an app subscription, identify who bills you, open that provider's subscription controls, complete cancellation and save the confirmation with the access-end date. Uninstalling an app is not a cancellation method. Before access changes, check export and retention terms and preserve needed data. Treat account deletion and refund requests as separate decisions, and check subsequent statements for unexpected charges.

Source: https://apptuse.com/cancel-app-subscription/  
Publisher: The App Exit Test  
Published: 2026-09-07  
Updated: 2026-09-07

## Cancel through the company that bills you

To cancel an app subscription, identify who bills you, open that provider's subscription controls, complete cancellation and save the confirmation with the access-end date. Uninstalling an app is not a cancellation method. Before access changes, check export and retention terms and preserve needed data. Treat account deletion and refund requests as separate decisions, and check subsequent statements for unexpected charges.

The useful finish line is evidence: the right plan, on the right account, with renewal stopped. An empty space on your phone's home screen cannot establish any of those things.

## Which account actually owns the subscription?

Start with a receipt and the matching statement entry. Write down the service, account email, billing provider, plan and next renewal date. Do not assume the account you use inside the app is also the account that paid for it.

For example, a notes service might have a personal workspace and a work workspace. Your objective is to stop the unwanted personal plan, not remove the app that opens both. That is an illustrative account mix-up, not a claim about a particular product.

Use this routing table as a starting point:

| Evidence you have | Where to check | What to establish |
|---|---|---|
| Receipt issued by Apple | Apple's subscription controls | The purchasing Apple Account |
| Receipt issued by Google Play | Google Play subscriptions | The purchasing Google Account |
| Invoice from the software company | Its official billing help and account | The billed workspace or plan |
| Subscription included through another provider | That provider's official support | Who controls renewal |

Do not send an unredacted bank statement to an app's public forum. Keep the full record privately and provide only the relevant information through the provider's official support channel.

If the payment is unfamiliar, do not assume it belongs to the app you last installed. First establish what the charge represents.

## What should you save before cancelling?

**Do not delete the account, remove its data or revoke access needed for an export as a shortcut to cancellation.** Those actions can affect the information you are trying to preserve. Read the provider's current cancellation, export and retention documentation for your exact plan.

Our editorial checklist separates three questions:

- When does paid access end?
- What remains readable or exportable after that date?
- What happens to stored information, shared work and integrations?

If the documentation does not answer them, ask support before proceeding. For a work account, involve the billing owner and the people responsible for data retention. Do not cancel a shared service on behalf of other users without authority.

Save needed records to an approved location and open representative files independently. Include an attachment and a structured item, not just a plain text note. This is a check that the export is usable, not a guarantee that every feature transfers. Follow the fuller [safe app-data migration workflow](/migrate-app-data-safely/) if you are moving a substantial archive.

There can be a trade-off between meeting a cancellation deadline and finishing an export. Check both immediately. Ask the provider about the actual access deadline; do not assume cancellation always preserves the rest of a free trial.

## How do you cancel an Apple-billed subscription?

On an iPhone, open Settings, tap your name, then Subscriptions. Choose the relevant subscription and use Cancel Subscription. On that subscription's page, Apple says an absent Cancel button or a red expiration message indicates it is already cancelled. These are [Apple's current instructions](https://support.apple.com/en-us/118428), not steps for every subscription used on an iPhone.

If the plan is missing, search your email for an Apple receipt and check its purchasing account. A family member must cancel a subscription purchased under their own account. Apple also directs people without an Apple receipt to identify the biller from their statement.

For Apple's free or discounted trials, its guidance says to cancel at least 24 hours before the trial ends. Do not apply that deadline to every company's trial; check its own terms.

Deleting the app will not do this job. [Apple explicitly separates app deletion from subscription cancellation](https://support.apple.com/en-us/101550). Keep the billing confirmation even if you later remove the app.

## How do you cancel a Google Play subscription?

On Android, open your subscriptions in Google Play, choose the plan, select Cancel subscription and finish the displayed instructions. Sign in to the Google Account that holds the purchase. If the subscription is absent, check whether you used another account. [Google's cancellation guide](https://support.google.com/googleplay/answer/7018481?co=GENIE.Platform%3DAndroid&hl=en) confirms that uninstalling the app does not cancel its subscription.

Google says a cancelled subscription generally remains usable for the time already paid. A payment plan has a separate limitation: stopping renewal does not remove remaining payments owed under the current plan. Read that section if you committed to multiple payments.

Do not mistake a pause for your intended final outcome. Where offered, pausing is a distinct option; check the restart details before choosing it. Record the resulting status and dates rather than assuming every option on a retention screen stops future billing permanently.

## What if the software company bills you directly?

Use the company's official help page for the plan named on your invoice. There is no universal sequence of Billing, Manage and Cancel buttons that works across direct-billed services. Giving one would create false precision.

Read each confirmation screen before advancing. In your own notes, distinguish an offer to change plans from an acknowledgement that cancellation is complete. If you choose to stay for a different offer, record its actual renewal terms; do not continue using the old cancellation checklist as though nothing changed.

If you cannot locate the control, contact official support with the account identifier, plan and relevant invoice reference. A useful message is: "I want to stop renewal of this subscription. Please confirm the cancellation procedure, effective date, remaining charges and access-end date."

This is a request for clarification, not proof the subscription has been cancelled. Keep any reply and follow up on unanswered points. The [FTC's subscription guidance](https://consumer.ftc.gov/articles/getting-and-out-free-trials-auto-renewals-and-negative-option-subscriptions) recommends following the company's cancellation instructions and retaining your request and conversation notes.

## What counts as useful cancellation evidence?

Create one private record containing:

- The service, plan and billed account.
- When you submitted the cancellation.
- The confirmation screen, email or support response.
- The stated expiry date and any remaining payment obligation.
- Any unresolved issue and the next follow-up action.

Our recommendation is to reopen the subscription record after finishing and read its status again. This catches a simple operational problem: closing a process without knowing which screen was its last confirmation.

An expiry date and a renewal date mean different things. If the wording is unclear, ask the provider to explain whether another payment is scheduled. Do not convert "request received" into "renewal stopped" in your own notes.

A receipt for the last payment proves that payment happened; it does not, by itself, prove cancellation. Likewise, a refund request needs its own outcome. Record it separately if you want both a refund and an end to renewal.

## What if charges continue afterward?

Compare the new charge with your records: account, service, payment date, cancellation date and any remaining commitment. Keep the discrepancy specific when contacting the biller. Avoid assuming that two similar statement descriptions represent the same subscription.

For US consumers, the FTC recommends checking statements after cancellation and disputing improper continued charges with the credit or debit card issuer. Its guidance also recommends written follow-up to the issuer's billing-dispute address and saving the records. Ask your issuer about the applicable process and deadlines; this is not a promise of a refund or a universal legal timetable.

If an unexpected renewal message asks for payment details, do not use its links or phone number to investigate. The FTC advises contacting a known company through a contact you know is genuine. Outside the US, use your provider, payment issuer and local consumer-protection guidance.

Finally, make the next subscription easier to leave. In your [app trial evaluation](/test-app-before-committing/), record the billing owner, cancellation route, export result and deadline before committing important work. A good exit plan starts while you still have time to use it.

## Sources

- [Apple: cancel a subscription](https://support.apple.com/en-us/118428).
- [Apple: delete apps on iPhone or iPad](https://support.apple.com/en-us/101550).
- [Google Play: cancel, pause or change a subscription](https://support.google.com/googleplay/answer/7018481?co=GENIE.Platform%3DAndroid&hl=en).
- [Federal Trade Commission: trials, renewals and subscriptions](https://consumer.ftc.gov/articles/getting-and-out-free-trials-auto-renewals-and-negative-option-subscriptions).

## Frequently asked questions

**Does deleting an iPhone app cancel its subscription?**

No. Apple states that deleting an app does not automatically cancel its in-app subscriptions. Complete cancellation through the billing provider and retain confirmation. Before removing an app or deleting an account, check what happens to local files and stored information and preserve anything you need.

**What if I cannot find the subscription in my account?**

Compare the account you are viewing with the purchase receipt. Check the billing provider and any other purchasing account you legitimately use. The account used inside an app may not identify who paid. Do not cancel another plan merely because its name looks similar.

**Should I delete my account to stop paying?**

Do not use account deletion as a cancellation shortcut. Check the provider's documented billing procedure and complete that process. Treat data removal as a separate decision after you have preserved required records and understood the consequences. For shared work accounts, involve the authorized billing and data owners.

**What proof should I keep after cancelling?**

Keep the service and plan name, billed account, submission date, confirmation, access-end date and any remaining payment obligation. Store them privately. If a message only acknowledges your request, seek confirmation of the final outcome rather than recording the subscription as cancelled on that evidence alone.

**Does a refund request also cancel future renewal?**

Do not assume it does. Treat the refund decision and subscription status as two separate records, and verify both through the provider's official process. If the answer concerns only a previous payment, ask explicitly whether renewal has also stopped and whether any remaining charges are scheduled.


---

# Migrate App Data Without Losing the Original

> Migrate app data by inventorying records, attachments, structure, permissions, integrations, and retention requirements; preserving an independent export; and importing a pilot into an isolated destination. Map every field, reconcile counts by record type, open files, test search and permissions, and assign every exception. Move in batches with a documented stop and rollback plan, capture changes made during migration, and keep the source intact or read-only through user acceptance. Delete accounts, revoke access, cancel subscriptions, and remove temporary archives only as approved destructive actions after required retention and verification are complete.

Source: https://apptuse.com/migrate-app-data-safely/  
Publisher: The App Exit Test  
Published: 2026-07-19  
Updated: 2026-08-26

## Keep the source intact through verification

Migrate app data safely by inventorying the source, making an independent export and backup, testing a small representative import, reconciling counts and fields, then moving in controlled batches. Keep the original system read-only or otherwise intact until users have tested the destination and every exception has an owner.

**Destructive actions come last.** Do not delete the source account, revoke a required integration, overwrite the only export, or cancel access needed for verification. A successful progress bar is an event, not a signed affidavit from every attachment.

## Inventory what must move

List record types, owners, workspaces, folders, tags, comments, attachments, links, permissions, timestamps, versions, automations, templates, recurring items, integrations, and audit or retention requirements. Record source counts and known anomalies.

Separate active data from material that should be archived, retained for legal or policy reasons, excluded for privacy, or deleted under an approved process. Migration is not permission to copy every historical record into a new processor.

Name the people responsible for security, privacy, compliance, business validation, and user communication where appropriate. Confirm current export and import documentation for the exact source plan and destination version.

Browse [data moves](/data-moves/) for more staged handoff patterns.

## Export to an independent location

Request the official export and preserve the original archive unchanged. Save a working copy for transformation. Record export time, account, scope, format, tool version, and any warning or excluded item.

Store files with access controls appropriate to their contents. Exports can be more exposed than the source because they may lack application permissions or encryption. Do not email sensitive archives, place them in a shared personal folder, or upload them to an unapproved converter.

Open the archive and inspect its manifest, folders, files, and encoding. An export that cannot be extracted or read is not a backup merely because its filename contains the word “backup.”

## Build a representative pilot

Choose a small set covering simple and difficult cases: long text, non-Latin characters, old and new dates, attachments, duplicates, nested structure, shared records, links, comments, and any custom field. Use a sandbox or isolated destination when available and approved.

Map every source field to a destination field, archive, transformation, or explicit exclusion. Record how identities, time zones, permissions, and links will change. Do not silently put unmatched data into a generic notes field if users or systems need its original meaning.

Run the pilot and save logs or reports. Investigate warnings before scaling.

Visit [app decisions](/app-decisions/) when destination limitations reopen the product choice.

## Reconcile content and behavior

Compare source and destination counts by record type, not only a grand total. Check missing, duplicated, truncated, or failed items and sample records from every edge category. Open attachments, follow internal links, search known phrases, and compare dates, authors, permissions, and special characters.

Test destination behavior: sync, sharing, notifications, recurring items, exports, and expected integrations. Some features cannot migrate as data and must be rebuilt, replaced, or intentionally retired.

Assign each exception a disposition and owner. Keep a migration ledger with batch, count, errors, decisions, and verifier. “Mostly moved” becomes useful only after the unmoved portion has names.

## Plan a reversible cutover

Tell users when the source becomes read-only, where new work begins, what will not migrate, how to report an error, and how long verification lasts. Freeze changes or capture a final delta so records created during migration are not stranded.

Move in batches with checkpoints. Stop when errors exceed the agreed threshold or a critical field fails. Restore or roll back according to the tested plan rather than improvising under deadline.

Use our [app trial guide](/test-app-before-committing/) to verify the destination's export before it becomes the new source of truth.

## Retire only after separate approval

After acceptance, retain the source and exports for the approved period. Confirm legal, contractual, privacy, security, tax, and organizational requirements with qualified owners.

**Destructive step:** account deletion, source data deletion, access revocation, and subscription cancellation may be irreversible or may start retention clocks. Treat each as a separate approved task. Verify the target account, capture required evidence, and understand the provider's current process before acting.

Remove migration archives from temporary locations under the approved retention plan and revoke temporary credentials. The migration is finished when the destination works, exceptions are resolved, rollback is no longer required, and retirement has been authorized—not when the new logo first appears on everyone's phone.

## Frequently asked questions

**What should I back up before migrating apps?**

Preserve an official full export where available, including records, attachments, metadata, structure, permissions, comments, versions, and manifests the provider supplies. Keep the original archive unchanged and make a working copy. Record export date, account, scope, format, and warnings. Store it independently with controls suitable to the data. A folder on the same system, an unread archive, or a synchronized copy without retention may not provide meaningful recovery.

**How do I test an app migration?**

Import a small representative pilot containing simple and difficult records, old and new dates, long text, non-Latin characters, nested structure, links, comments, attachments, duplicates, and multiple permission levels. Map each field before the run. Then compare counts, open content, search known phrases, verify identities and dates, and test destination behavior. Resolve or assign every warning before scaling to larger batches.

**How can I tell whether all data migrated?**

Compare source and destination counts by record type, folder, owner, or another meaningful group rather than only a grand total. Review failed-item logs, duplicates, truncation, attachments, permissions, timestamps, links, encoding, and edge-case samples. Test features that may require rebuilding, such as automations and recurring items. Maintain a ledger of batches, counts, exceptions, decisions, and verifiers so the acceptance claim has evidence.

**When should the old app become read-only?**

Make it read-only at the planned cutover when users have been informed, the pilot has passed, backups exist, and the team knows where new work belongs. If read-only mode is unavailable, define a short freeze or capture a final delta of changes. Do not let both systems accept uncontrolled edits indefinitely. Keep source access long enough for verification and rollback under the approved retention and contract plan.

**When is it safe to delete the old app account?**

Only after destination acceptance, exception resolution, required retention, tested recovery, and separate approval from relevant data, security, privacy, legal, financial, or business owners. Deletion, cancellation, and credential revocation can have different effects and retention clocks. Verify the exact account and provider process before acting, save required evidence, and remove temporary migration archives under the approved plan. Never delete merely because the import screen reported success.


---

# How to Review App Permissions on iPhone and Android

> Review app permissions in your phone's privacy settings, then separately inspect apps linked to your online accounts. Match each permission to a feature you actually use, reduce unnecessary access, and check the result. Before removing a sign-in connection, understand how you will regain access. Revoking permission is not proof that a company deleted information it already received; data deletion needs its own process.

Source: https://apptuse.com/review-app-permissions/  
Publisher: The App Exit Test  
Published: 2026-09-15  
Updated: 2026-09-15

## How do you review app permissions?

Review app permissions in your phone's privacy settings, then separately inspect apps linked to your online accounts. Match each permission to a feature you actually use, reduce unnecessary access, and check the result. Before removing a sign-in connection, understand how you will regain access. Revoking permission is not proof that a company deleted information it already received; data deletion needs its own process.

A useful review ends with a small record of what you kept, changed and still need to investigate. It does not require a verdict that every app is trustworthy or untrustworthy. This guide is based on current Apple and Google documentation checked in September 2026, not hands-on testing of every phone model or app.

## What should you check before changing anything?

Choose one app you use and write down its job. “Scan an occasional receipt” is a clearer starting point than “organize my life.” Then list the information or device functions that job appears to require.

Our editorial review sheet uses these columns:

| Item | What to record |
|---|---|
| App and account | App name, developer and which personal or work account you mean |
| Intended task | The feature you still want to use |
| Current access | The permission wording shown on your device or account |
| Proposed change | Keep, reduce, remove or investigate |
| Result | Whether the task still works and what remains unresolved |

Keep account identifiers and screenshots private. For a work or school account, ask the responsible administrator about access you do not own or understand. Do not change a shared workflow just because its purpose is unfamiliar.

Before removing a connection needed for an export, preserve and verify the information you need. The [safe app-data migration guide](/migrate-app-data-safely/) covers that separate task. A permissions review should not accidentally become an account-retirement project.

## Where are iPhone app permissions?

Apple's current iPhone guide routes information-access reviews through **Settings → Privacy & Security**. Select an information category, such as Calendars, to see apps that requested access, then change an app's access there. Apple says a permission decision can be changed after the original request. See its [information-access instructions](https://support.apple.com/guide/iphone/control-access-to-information-in-apps-iph251e92810/ios).

Read the category and the app name together. A list of apps requesting calendar access answers a different question from a list of every app installed on the phone. If the documentation and your screen differ, select the guide's version for your iOS release before following another route.

## Where are Android app permissions?

Google's [Android permission guide](https://support.google.com/android/answer/9431959?hl=en) gives two routes:

1. **For one app:** Settings → Apps → the app → Permissions. Use See all apps if necessary.
2. **For a permission category:** Settings → Security & Privacy → Privacy → Permission manager, then choose the category and app.

Tap the permission to choose an available setting. Depending on the permission, options may include allowing access only while using the app, asking every time or not allowing it. “All the time” applies to location, not every permission.

Google notes that some steps require Android 11 or later on Pixel. Treat this as a documented starting point; use your device manufacturer's current help if the menus differ. Record the wording you actually see rather than assuming every Android phone offers identical choices.

## How do you decide whether to keep access?

Use a task-based check rather than a blanket rule. For an illustrative receipt-scanning app, ask whether the permission is needed to take a new picture, select an existing image or perform a separate feature you do not use. This example is a set of questions, not a claim about a named product's design.

Change one setting, then repeat the intended task with harmless sample material. Record exactly what happens. If a feature stops working, decide whether it is worth the requested access; do not automatically restore every permission just to dismiss a prompt.

A useful result might be “manual entry works; the optional capture feature needs review.” That is more informative than “the app broke.” Ask the developer which feature requires the access and whether a narrower option exists. Do not invent an alternative workflow if the app does not provide one.

This is the same criteria-led approach used in [testing an app before committing](/test-app-before-committing/): evaluate a real task and keep the outcome observable.

## Can an iPhone show how permissions were used?

On iOS 15.2 or later, [App Privacy Report](https://support.apple.com/en-us/102188) can show data and sensor access and network activity. Enable it through Settings → Privacy & Security → App Privacy Report. It begins gathering information after activation, so an initially empty report is not a historical all-clear.

The report covers activity over the past 7 days. A domain contact can come from content inside an app, such as an embedded video. Likewise, access to device data does not necessarily mean the developer collected it; Apple gives on-device use as an example.

Use unexpected entries to form a specific question for the developer, not as automatic proof of misuse. **Turning the report off clears its data**, so preserve needed observations before doing that.

## Why check Google Account connections separately?

Device permissions and online account connections are separate review locations. Google's [linked-apps guide](https://support.google.com/accounts/answer/13533235?hl=en) distinguishes Sign in with Google, Google accessing a linked app account, and an app accessing Google Account data. One app can have more than one connection type.

For an app's access to Google data, follow the guide's linked-apps link, select **Access to your Google Account**, choose the app and select **See details**. Read the access before choosing **Remove access → Confirm**. Removal can disable features that depend on it.

Do not substitute the Sign in with Google removal control for this data-access review. Read which connection the confirmation screen describes. Removing one type is not evidence that you reviewed the others.

## What should you know about Sign in with Apple?

Apple lists these connections under **Settings → your name → Sign in with Apple**. Select an app to review the information originally shared. Its [management guide](https://support.apple.com/en-us/102571) says stopping use signs you out of the app on that device.

Before using the Delete control, check your intended sign-in route. Apple says signing in with Apple again returns you to the same account; some apps also allow a password for the existing account. Do not assume that option exists everywhere or create a duplicate account unintentionally.

If a developer uses the connection across several apps, stopping it for one can apply to all of them. Managed Apple Accounts should be handled with the administrator.

## Does removing permission erase data already shared?

Do not use a changed switch as proof of deletion. Google's [account-data sharing guidance](https://support.google.com/accounts/answer/14013600) explains that linked apps can copy data to their own servers and retain it according to their policies. Deletion may not be immediate or automatic.

If removal of stored data is your objective, consult that provider's privacy policy and account-deletion instructions, preserve any needed records first, and keep the request and response. **Account deletion can destroy information or access; review its consequences before confirming it.**

Close the review with separate entries for access changed, functionality checked and data-deletion questions still open. An unanswered retention question should stay visible. A permissions screen cannot answer it on the provider's behalf.

## Sources

- [Apple: information access on iPhone](https://support.apple.com/guide/iphone/control-access-to-information-in-apps-iph251e92810/ios).
- [Google: Android app permissions](https://support.google.com/android/answer/9431959?hl=en).
- [Apple: App Privacy Report](https://support.apple.com/en-us/102188).
- [Google: manage linked apps](https://support.google.com/accounts/answer/13533235?hl=en).
- [Apple: manage Sign in with Apple](https://support.apple.com/en-us/102571).
- [Google: account-data sharing and retention](https://support.google.com/accounts/answer/14013600).

## Frequently asked questions

**Where do I review information access on an iPhone?**

Open Settings, then Privacy & Security, and choose an information category such as Calendars. Apple lists apps that requested that access so you can review or change it. Match the guide to your iOS version if the screen differs, and check the intended task after changing a permission.

**How do I check one Android app's permissions?**

Google's documented route is Settings, Apps, the app name, then Permissions. Use See all apps if needed. Review the available choices for each permission; they are not identical for every category. Some documented steps require Android 11 or later on Pixel, and other devices may use different menus.

**Does an empty App Privacy Report prove no access occurred?**

No. Apple says App Privacy Report begins gathering information only when enabled, so it cannot show an earlier history that it never recorded. Let it collect activity during normal use before interpreting the entries. Turning the report off clears its stored data, so preserve needed observations first.

**Will removing access delete the data an app already copied?**

Do not assume so. Google explains that linked apps can retain copied account data under their own policies, and deletion may not be immediate or automatic. Check the provider's current deletion process separately, preserve needed records before destructive actions, and keep the request and any confirmation.

**What happens when I stop using Sign in with Apple?**

Apple says you are signed out on that device. Using Sign in with Apple again returns you to the previously used account; some apps also support a password for that account. Check before disconnecting, because a developer's shared sign-in connection can apply across several of its apps.


---

# How to Test an App Before Committing

> Test an app with three real tasks and realistic fictional data before committing production information. Define must-haves, useful features, and disqualifiers first; then check permissions, accessibility, offline and sync behavior, collaboration, support, total cost, renewal, cancellation, deletion, and current terms. Export the sample, store it outside the app, and open it independently to verify text, dates, structure, attachments, tags, links, and encoding. Compare candidates with the same scorecard and pilot the winner in a limited reversible scope. An attractive interface does not compensate for a failed workflow or unusable exit.

Source: https://apptuse.com/test-app-before-committing/  
Publisher: The App Exit Test  
Published: 2026-07-19  
Updated: 2026-08-26

## Test the exit before trusting the entrance

Test an app before committing by defining three real tasks, using realistic sample data, checking permissions, offline and sync behavior, accessibility, collaboration, export, cancellation, and account deletion, then scoring the result against criteria chosen before the trial. Keep important production data out until the export opens correctly elsewhere.

The best trial verdict is rarely “this interface feels modern.” It is “this completed our work, preserved the difficult details, cost what we expected, and let us leave with usable data.” A pleasant button radius may attend the evaluation, but it does not chair the committee.

## Write the verdict criteria first

Choose must-have, useful, and disqualifying conditions. Include supported devices and operating systems, required file formats, number and type of collaborators, offline needs, accessibility, privacy, security, support, integrations, total cost, and exit requirements.

Define the actual result for three tasks. For a notes app, that might include creating a structured note, finding it on another device, sharing a read-only copy, and exporting attachments. For scheduling, include a recurring event, time zone, invitation update, and export.

Use the same tasks for every candidate. A comparison in which each app receives its favorite demo is a talent show, not an evaluation.

Browse [app decisions](/app-decisions/) for more criteria-led comparisons.

## Inspect current terms and total cost

Read the current official pricing, trial, renewal, cancellation, refund, data-retention, privacy, and account-deletion information for your region and plan. Save a dated copy of material terms. Do not rely on an old review or a price shown to another account.

Calculate required seats, billing period, storage, usage limits, taxes, add-ons, export access, and the cost of any connector or automation the workflow needs. A nominally free plan can still fail the must-have criteria; a paid plan can be economical when it replaces real work.

Set a reminder before renewal and confirm how cancellation affects access and data. Cancellation and deletion are separate actions in many services; verify the exact current process.

## Use safe sample data

Create fictional but structurally realistic records. Include long text, non-Latin characters, dates, attachments, tags, nested folders, comments, links, recurring items, or other features the real workflow uses. Never upload secrets, regulated data, personal archives, or client information merely to test an unapproved product.

Review requested permissions and grant only what the test requires. If the app requests broad contacts, storage, microphone, camera, location, administrator, browser, or account access, understand why and how to revoke it. Seek qualified security, privacy, legal, or compliance review where the organization requires it.

## Test failure and awkward cases

Work briefly without a network if offline operation matters. Edit the same sample from two devices and observe conflict handling. Try a large permitted attachment, a very long item, a time-zone change, a collaborator with restricted access, and a search for an older record.

Do not deliberately overload or attack a service. Stay within terms and reasonable use. The goal is to expose workflow limits, not to begin an unsolicited security career from the trial account.

Record the exact app version, platform, plan, date, and result. Behavior may change later.

Visit [data moves](/data-moves/) before testing an export with valuable information.

## Export and open the result elsewhere

Export the full sample in every promised format available to the plan. Store the files outside the app, inspect their structure, and open them in independent software. Check text, dates, hierarchy, tags, comments, attachments, links, metadata, and character encoding.

An export archive is not useful merely because it downloaded. Proprietary fields may be omitted or flattened. Document what survives, what changes, and what would require manual work.

Use our [safe app-migration guide](/migrate-app-data-safely/) for a larger staged move.

## Compare with one scorecard

| Area | Pass evidence | Worth knowing |
|---|---|---|
| Core tasks | Three real scenarios completed | Count workarounds and training |
| Data exit | Export opens independently | Note flattened or missing fields |
| Reliability | Sync and offline tests understood | Record conflicts and recovery |
| Access | Required users and accommodations work | Test least-privileged role |
| Cost | Total needed plan calculated | Include renewal and add-ons |

Choose the app only when must-haves pass and the weaknesses are acceptable. Pilot with a limited reversible scope before full adoption. The verdict can be “not yet” or “none”; software shopping does not require sending a winner home with custody of the database.

## Frequently asked questions

**What should I test during an app free trial?**

Test three real workflows, difficult sample records, permissions, accessibility, offline use when needed, sync conflicts, collaboration roles, search, support, export, cancellation, and deletion. Calculate the plan and add-ons required for actual use. Use fictional data unless the product and organization are approved for sensitive information. Record platform, app version, plan, and date because behavior and terms can change after the evaluation.

**How do I compare two apps fairly?**

Give both the same must-have criteria, tasks, sample data, user roles, devices, and failure cases. Record evidence rather than impressions and count workarounds, training, add-ons, and migration effort. Test the export from each, not just the onboarding path. A weighted score can help, but a failed disqualifying condition should remain a failure rather than disappearing inside an average boosted by attractive features that the workflow does not need.

**Should I upload real data during an app trial?**

Not by default. Use fictional but structurally realistic records until security, privacy, legal, contractual, and organizational approval is settled. Real data can contain personal, client, regulated, secret, or licensed material that an unapproved service should not receive. If a controlled pilot requires limited production data, define scope, permissions, retention, backup, deletion, and incident handling with qualified owners before uploading it.

**Why should I test app export before subscribing?**

Export determines whether you can back up, migrate, audit, or leave. Download every promised format available to the intended plan and open it outside the app. Check hierarchy, text, dates, attachments, tags, comments, links, encoding, and metadata. Some exports flatten or omit proprietary fields. Discovering that limitation during a trial is inconvenient; discovering it after years of records have accumulated can turn a product choice into a large migration project.

**How do I calculate the real cost of an app?**

Include required seats, billing period, taxes, storage, usage tiers, add-ons, integrations, support, training, migration, export access, and expected renewal pricing under current terms. Note what happens when a collaborator needs a different role or the team exceeds a limit. Also count staff time spent on workarounds. Compare the total against the work replaced or improved, not against a headline price shown for a smaller plan or another region.


---