Support

Albarium is an iPhone app for putting your albums in Photos in order. One overview shows which albums are empty, have a duplicate name or cover just one day, and you can merge albums, rename them, put them in a folder or remove them. Before every action on your albums, the app saves how they were, so you can undo that action.

What the app does

• An overview of your albums. For each album: the number of photos and the dates it covers. If some of its photos are also in another album, the row says how many are only in that album, or that they are all also in another album. Every album the app shows counts here, also shared and synced albums, in the list and in the album itself. When removing, only your own albums count (see the question about removing an album). At the top you see how many one-day albums and empty albums you have and how many albums share a name with another, and how many albums share photos with other albums (Share photos with other albums). Tap one and the list shows only those albums, and the screen scrolls down to that list. Empty means: without photos the app shows. Such an album may still hold photos you hid in Photos (see the question about hidden photos). You can then remove the empty albums in one go (see the question about removing an album).
• Proposals. Day albums that belong together, by date, time between them and place, can be merged into one album or, when folders are on, put together in a folder. Day albums in a folder only go with day albums in that same folder: the new album or folder then goes in that folder, so your own filing stays as it is. When the day albums of a proposal are already together in a folder, with nothing else in it, the app does not propose a new folder, because it would change nothing: such a proposal only offers merging, and only when the app advises it; otherwise there is no proposal. An exception is a folder with only day albums from one month, at least three, with no other albums or folders in it: then the app proposes to merge them into one album with the name of the folder, unless they hold more than 1,500 photos together. That album takes the place of the folder, and the folder, empty by then, goes in the same action; iOS asks once whether the day albums and the folder may go. If you leave an album out, if one of the albums probably holds a hidden photo, or if folders are off, the album goes in the folder and the folder stays. The new folder of a proposal never gets the name of the folder it goes in. A proposal you applied does not come back as long as it is about the same albums, unless you restore something. To apply many proposals, tap Select at the top right, tick the proposals you want and tap Apply at the bottom. That is one action: one line in Rewind, so restoring puts them all back at once, and iOS asks once whether the albums may go. Each proposal then gets the name at the top of its card; per proposal you choose Merge into one album or Put in a folder (the latter only when folders are on). Albums with the same name (as under Duplicate names) can be merged the same way into one album with that name. The proposal shows per album how many photos are also in another album with that name, so you see whether they are real duplicates or only share a name. Only albums of the same moment belong together: they share a photo, or there is at most a month between them (also through a third album). So an album "Christmas" of every year stays apart. That happens within one folder first. When albums of the same moment are in different folders, you choose where the merged album goes: in the proposal, or, when you apply many at once, for all of them at once, for example Not in folder iPhoto Events, so that each merged album goes where the other album is. When a proposal has more than one place left, you choose it for that proposal. The app does not choose for you: as long as a place is missing, it carries nothing out. Nothing changes until you choose.
• Album actions. Merge, rename (one album, or several at once with a pattern), put in a folder, and remove. When merging, putting in a folder and removing, the app shows a preview first: which albums disappear, which albums or folders appear, and how many photos or albums they hold. When renaming with a pattern, you see the new names first.
• Rewind. A log of your actions on albums and folders, and of photos you move to another album in the workbench. For each action you can put your albums back to how they were before it. Photos you delete in the workbench are not in the log.
• Workbench. Review photos starting from your albums: near-duplicates, failed or blurry photos, and screenshots and documents.

What the app does not do

• It is not a cleaner for your whole library. It does not look for duplicate photos across your library, does not compress videos, does not calculate storage for you and does nothing with your contacts. Reviewing photos only happens for the workbench, and it always opens from albums: an album you clean up, the new album after merging, or the photos that are only in the albums you are about to remove. After merging, the app already looks for near-duplicate series in the new album by itself, before you open the workbench.
• It never deletes photos by itself. Photos are only deleted after you reviewed them in the workbench, and only when you allow it in the iOS confirmation.
• Removing an album does not delete photos.
• Albums that Photos puts together itself, such as your favourites or screenshots, are not in the app. Shared albums and albums synced from a computer can be shown, not changed.
• There is no account, and the app does not talk to a server.

Frequently asked questions

What access does the app need, and why?

The app asks for Full Access to your photos. It reads them for the overview. It changes your library to merge, rename, move into folders and remove albums, and to move or delete the photos you choose in the workbench.

Full access is needed because the app has to see which photos are in each album. With limited access the app may see only the photos you selected, and then not everything in your albums. Counts, dates and overlap would then be wrong, and merging could leave photos behind. So the app only works with full access. What exactly iOS lets the app see with limited access, we have not tested (see the next question).

The app asks for no other access: not your location, not your camera and not your contacts. Place names come from the location already stored in your photos, looked up in a list that is part of the app.

What happens with limited access?

The app shows a short explanation with one button to Settings. To change it:

1. Tap Open Settings. Settings opens on the Albarium page.
2. Choose Photos › Full Access.
3. Come back to the app. The overview starts by itself.

The same applies if you denied access. If access to photos is restricted on your iPhone, for example by Screen Time or a management profile, the app shows the screen Access to photos is restricted, without these steps. Only the person who manages your iPhone can change it; without access the app cannot do anything, and the Open Settings button is turned off. If you later set access back to limited or off, the app shows this explanation again.

We checked this screen by simulating limited access in the simulator. It has not been tested with a real selection of photos in iOS.

What happens to my photos when I remove an album?

They stay. Removing an album never deletes photos: they stay in your library and in every other album they are in. If it holds photos that would then be in none of your own albums, the app puts them in an archive album by default; you can choose otherwise when removing.

Before you remove albums, the app shows for each album, in one sentence, how many photos it holds and where they will still be. Only in these albums (with one album: only in this album) means: in no album of yours that stays. Also elsewhere means: also in an album of yours that stays. This is about your own albums, the albums the app can change; shared and synced albums do not count. If a photo is in more than one of the albums that go and in no album that stays, it counts at the first of those albums in the list. At the next ones it is already counted under that album, for example 4 already counted under Tuin (if they come from more than one album higher in the list, already counted above). That way the parts of each album add up to the number of photos in that album, and the only in these albums of all the albums together add up to the number above the choices: the photos that are in none of your own albums that stay, each once. In also elsewhere, the same photo can count for more than one album.

If some photos are only in those albums, you choose what happens to them:

• Keep them in an archive album (selected by default). The photos that would be in none of your own albums after removing go to an archive album first, so you can still find them. You choose the name. If you already have an album of your own with exactly that name, and it is not one of the albums you chose, they are added to it (if you have more than one, to one of them). Otherwise the app makes a new album with that name, also if a shared or synced album already has it, or one of the albums you chose.
• Only remove the albums. Photos that were only in the removed albums will no longer be in any of your own albums, but stay in your library.

Below that, on its own, is Review them first in the workbench. There you look at those photos first, from all the albums that go, together: delete what can go, move what belongs in another album. Then you remove the albums.

Merging also removes the original albums. All the photos you see in those albums are then in the new album. When you merge albums you selected yourself, you can keep the old albums: in the Merge screen, turn off Remove the original albums. In a proposal, the day albums are removed when you choose Merge into one album. To keep them, choose Put in a folder. That choice is only there when folders are on (see the question about folders) and when a folder changes something: when the day albums are already together in a folder, with nothing else in it, there is no Put in a folder.

The exception is albums that hold a photo you hid in Photos. If the app thinks so, it leaves such an album in place when you remove or merge albums, also in a proposal (see the question about hidden photos). When removing, such an album is listed with Stays. The heading above the list then says how many albums go, and the photo counts and the choices are only about the albums that go. Restoring leaves such an album in place too (see the question about hidden photos).

You can remove empty albums in one go. Tap Empty albums at the top, or choose the filter Empty. Above the list you then see Remove the 6 empty albums, with your number. It opens the same screen as Remove Albums when selecting, with every empty album in the list that the app can change; shared and synced albums are left out. If you search the list, only the empty albums that match your search count. Empty albums that the app thinks probably hold a hidden photo stay, as above: the button does not count them and says how many stay. No photo leaves your library.

iOS asks for your permission before albums are removed (see the question about system confirmations below).

What does the app do with photos I hid in Photos?

The app does not show photos you hid in Photos. They are not in the counts, not among the photos of an album, and not in the workbench or in proposals. A hidden photo does stay in its albums.

What else the app can do with hidden photos depends on what iOS lets it see. We have only tested this in the simulator, on iOS 27.0, with the Hidden album locked; that is the default. There, the app did not get to see the hidden photos at all. What follows applies to that situation:

• Removing. If the app thinks an album holds a hidden photo, it skips that album. What happens lists which albums stay, and why. If your choice consists only of such albums, the app removes nothing and tells you that you can remove them in Photos yourself.
• Merging. Such an album stays, even if you have the original albums removed or choose Merge into one album in a proposal. What happens says this too. If no album at all would go then, the app does not merge: the new album would only be a copy. You get no proposal for which merging does not make the list shorter; when you apply many proposals at once, such a merge is left out and What happens says which. Hidden photos do not go into the new album.
• The app does not always know. It notices a hidden photo in two ways. The first is an estimate iOS gives of the number of photos in the album, but that estimate counts a hidden photo only briefly: in our test on iOS 27, a few seconds after hiding it no longer did. The second is the history of changes that Photos keeps. From it, the app reads what changed in your library, also while the app was closed. If the app can no longer find a photo it saw in an album anywhere, and Photos does not report it as deleted, the app remembers that the album probably holds a hidden photo. A photo you delete is reported as deleted by Photos; in our test such a photo gave no protection. The other way round, the estimate can protect an album wrongly: if the app reads an album for the first time or reads everything again just after you deleted a photo in that album or took one out of it, the estimate still counts that photo for a moment. With an ordinary update this can happen too, if at the same moment a photo went out of sight elsewhere in your library without being reported as deleted. Such an album then stays until the app reads it again. It only does that once something changes in the photos in your library or in that album itself, or when it reads everything again. So trying again later usually does not help, not even after restarting the app. This too we have only tested in the simulator, on iOS 27.0. What the app cannot know this way:
  • photos you had already hidden before the app first read your library. If you already have hidden photos when you start using the app, it does not know which albums they are in;
  • a photo that was added to an album and hidden while the app was closed: the app never saw it in that album;
  • photos you hide during a period for which iOS gives the app no history of changes. The app then reads your whole library again, and from that it cannot tell a hidden photo from a deleted one;
  • photos you hid since the app last read your library, if it then cannot use its own saved overview of your library, for example because a new version of the app stores it differently or because the file cannot be read. Then too it reads your whole library again;
  • which albums it had remembered this way: that is gone if you delete the app and install it again, if the file in which the app keeps it cannot be read, and on an iPhone you restored or set up from a backup, such as a new iPhone, because the app keeps that file out of backups (we have not tested that last case).

  The other way round, the app can keep leaving an album in place when removing and merging while the hidden photo is no longer in it, for example if you later delete that photo during a period for which iOS gives no history of changes. You cannot change that in the app; in Photos you can remove such an album yourself. If an album with a hidden photo is removed anyway, the photo stays in your library, in Photos under Hidden, but is no longer in that album, not even after restoring. The app says so, in the same words, wherever albums go: under What happens when removing, merging and in proposals, after the action, in Rewind for such an action, and at the bottom of the Rewind tab. To be sure, first make a hidden photo visible again in Photos.

• Restoring. An album the app thinks holds a hidden photo is left in place by restoring too, also when the album was made after the snapshot and so is not in it. The rest of your albums go back as usual. If such an album was in a folder that goes when restoring, it moves to the nearest folder above it that stays, or otherwise to the top level. In Rewind, the question beforehand names the albums that stay this way, and after restoring the app says it again. Undo asks the same question when there is an action after it. Undo, Undo action, Put everything back as it was and Undo moving say it after restoring. And in Rewind it is listed with the restore itself, under what changed. In our test in the simulator (iOS 27.0) such an album stayed, with the hidden photo in it. Two things we have not tested in the app: moving out of a folder that goes (only with simulated albums, without Photos), and the messages after Undo, Undo action, Put everything back as it was and Undo moving. If the app does not know (see above), restoring does remove such an album. And restoring does not put a hidden photo back in an album that has gone in the meantime (see "What cannot be undone?").

If you turn off the lock on the Hidden album, or use iOS 26 or a real iPhone, it has not been tested what iOS lets the app see. If iOS does give the app hidden photos, the app keeps only their IDs for each album. With those, it always leaves such albums in place when removing and merging, and restoring is built to put those photos back in their albums. That has not been tested either.

How does undoing work with Rewind?

Before every action on your albums and folders, Rewind saves a snapshot: album names, folders, the order, and which photos are in which album. It does not contain the photos themselves. If the snapshot cannot be saved, the action does not start. Moving photos to another album in the workbench is such an action too. Deleting photos in the workbench is not: it is not in the log, and the app cannot put it back (see "What cannot be undone?").

You can restore in these places:

• Right after an action. The screen that shows what happened has an Undo button. It puts your albums back to before the action of that screen. If you did something else in the app after it, for example moved photos in the workbench after merging, that is undone too; the app then asks first, with the same question as in Rewind (see below). Undo also puts back what you changed in your albums in Photos itself in the meantime, without the app asking about it (see "What cannot be undone?"). After moving photos in the workbench, the button is called Undo moving. From iOS 26.1, the bottom of the screen, above the tabs, also shows a bar with what happened and Undo action.
• In the Rewind tab, all your actions are listed by day. Tap an action and choose Restore to before this action. In the list you can also swipe: swipe an action to the left; the button that appears is called Restore. With VoiceOver, Restore to before this action is among the row's actions.
• If an action was interrupted, for example because the app was closed, the top of the Rewind tab shows a notice with a Restore button. It puts your albums back to how they were before that action. If they already were, nothing changes and the app says so. The notice then goes away, and the action is listed as Did not finish.

In Rewind, the app first asks whether you are sure. That question names the action by its title. Usually that is the name of an album or folder:

• when merging, the new album;
• when putting albums in a folder, the folder;
• when renaming, the new name;
• when removing, the archive album if photos go to an archive album, which is selected by default (for example "before “Archive”"), and otherwise the album that goes;
• when applying several proposals at once, the first new album or folder, with how many more there are (for example "before “June 2024 and 11 more”");
• after moving photos in the workbench, the album you cleaned up. If you opened the workbench when removing albums, it is the album that goes, or with several albums at once the description Only in these albums.

If the action was about several albums, the title names one of them. If the album or folder has no name, the question calls it Untitled album or Untitled folder. A restore has the title of the action it undid.

If there are later actions, the question says how many, and that they are undone too, as far as they changed anything. That count skips actions that were already undone, but does include actions that failed or changed nothing. The question does not show what changes for each album; it only names albums that stay because the app thinks they hold a hidden photo (see the question about hidden photos). Undo moving and Undo action restore right away, without a preview and without a question from the app. So does Undo, unless there is an action after it: then the app asks this question first. After restoring, Undo says how many later actions were undone too. If albums or folders have to go when restoring, iOS does ask for permission for that.

About the bar with Undo action: it is about your latest action that succeeded. If an action fails, or is only partly carried out, while the bar is still there, the bar is still about the action before it. Undo action then puts your albums back to before that earlier action, and so also undoes what the failed action had already done. The bar goes away when a restore succeeds and changes something in your albums. It also goes away when you restore to before the action in the bar and there is nothing to restore, for example when you tap Undo action or Undo while your albums are already that way. And it goes away when the app starts again. If there was nothing to restore, the app says so. If restoring fails, or you don't allow the question from iOS, the app says so too, and the bar stays.

What to know about restoring:

• Your albums go back to the snapshot from just before that action: names, folders, order and which photos are in which album. If an album has been removed in the meantime, the app makes it again, as a new album with the same name and the same photos, except hidden photos the app does not get to see (see "What cannot be undone?"). If you choose an older action, the actions after it are undone too. In Rewind, the app tells you this first.
• A restore is itself an action with its own snapshot, so you can undo it as well. If there is nothing to restore, because your albums already are that way, nothing changes and nothing is added to Rewind.
• After restoring, the app compares your albums with the snapshot, as far as it can see them. Two differences are allowed: photos that are no longer there, such as photos you deleted (see "What cannot be undone?"), and albums that stay because the app thinks they hold a hidden photo. The app leaves those photos and those albums out of the comparison; it checks that those albums are still there, and says which they are.
• You can export a snapshot: open an action in Rewind, tap Snapshot from just before and choose Export snapshot. It is a readable JSON file in which you can check what is stored. What it contains is described in the privacy policy. The format is described on the Snapshot page. You cannot restore from an export: the app cannot read such a file back in. To make exporting possible, the app keeps a copy of the snapshot ready while you have it open; it deletes that copy when you close the snapshot, or otherwise at the next launch.

What cannot be undone?

• Deleted photos. Rewind does not keep photos, and deleting photos in the workbench is not in the log. Photos you delete in the workbench are in Recently Deleted in Photos, and you put them back from there yourself (see the next question). Photos that are no longer in your library, including those in Recently Deleted, are skipped when restoring.
• What is not in a snapshot. For example a cover photo you chose for an album in Photos, or which albums you pinned in Photos. The app does not put that back.
• Shared albums, synced albums and albums that Photos puts together itself. The app cannot change these, so they are not in a snapshot either.
• What you did in Photos in the meantime does not always stay. Restoring puts your whole album structure back to that moment. Albums and folders added since then, including ones you made yourself in Photos, are removed. The photos in them stay in your library. An album the app thinks holds a hidden photo does stay (see the question about hidden photos). If the app does not know, restoring removes it, and the photo stays in Photos under Hidden, but is then no longer in that album. Names and contents of your own albums also go back to that moment. If in doubt, restore to a recent action.
• Hidden photos in an album that has gone in the meantime. When restoring makes a removed album again, photos you hid in Photos do not come back into it if the app does not get to see them, as in our test on iOS 27.0 (see the question about hidden photos). They stay in Photos under Hidden. The comparison after restoring does not notice this, because the app compares what it can see.
• Photos you hid since then. If you hid a photo after the snapshot and the app does not get to see it, restoring does not put it back in its albums, even though it is still in your library. If it is still in an album that remains when restoring, restoring does not take it out of that album either.
• Snapshots after deleting the app. The snapshots are kept in the app's own storage on your iPhone. If you delete the app, iOS deletes them from your iPhone. Your albums in Photos stay as they are at that moment. A snapshot you export first stays with you as a readable file, in which you can check how your albums were. The app cannot restore from that file.

Where do deleted photos go, and how long do they stay there?

Only the workbench deletes photos, and only after your review and the iOS confirmation. Those photos go to Recently Deleted in Photos. You can put them back from there in Photos until iOS deletes them for good. How long they stay in Recently Deleted is decided by iOS, not by the app. If you delete them from Recently Deleted yourself, they are gone sooner.

Removing an album sends no photos to Recently Deleted. The photos simply stay in your library.

How do folders work, and what do I see of them in Photos?

You can put albums in a folder from the app:

• In the Albums tab, tap the checkmark in a circle at the top right (Select), choose albums, and tap Move to Folder in the bar at the bottom.
• Or open an album, tap the button with three dots at the top right, and choose Move to Folder.
• Or choose Put in a folder in a proposal.

With the first two you choose a new folder or an existing one; a proposal always makes a new folder, where the day albums are: at the top level, or in their folder, and never with the name of that folder. The albums stay as they are.

In Photos, a folder appears under Collections › Albums, as a card with small covers of the albums inside. Tap it to see the albums. This was checked in our test setup on iOS 26.5 and iOS 27.

Folders are on by default in the app. If you prefer to keep all albums at the top level, turn off Folders in the app's Settings (the gear in the Albums tab). The choices above then no longer appear. Folders you already have stay, and restoring also puts folders back if they are in the snapshot. The switch is also there in case a later version of iOS starts treating folders differently.

The app has no action to remove a folder. Through the app, a folder only disappears when you restore (folders added since that moment are then removed) and with the proposal for a folder of day albums from one month, when all those day albums become one album (see Proposals at the top). iOS asks for your permission for that too.

What can the app do with shared albums and the Shared Library?

Shared albums (iCloud) appear in the app with the label Read-only. You can look at them, but you cannot select them for an action or clean them up in the workbench. They are not part of proposals or snapshots either. How shared albums behave on a real iPhone has not been tested yet: our test setup has none. That is why the app treats them as read-only for now. The same goes for albums synced from a computer.

Shared Library. iOS does not let apps see which photos come from the Shared Library. This means:

• Merging, renaming, moving into folders or removing albums deletes no photos, so no one else's photos either.
• According to Apple, all participants can delete photos from the Shared Library, and such a photo goes to Recently Deleted. So if you delete a photo in the workbench that is in the Shared Library, it is gone from the Shared Library for the others too. We have not tested this, and the app cannot see which photos it concerns. That is why the summary says so before iOS asks you to confirm.

How does the workbench work?

Open an album and tap Clean Up. You also reach the workbench:

• After merging. On the screen that shows what happened, the app looks for near-duplicate series in the new album by itself, if it holds at least two photos. If it finds any, you can open the workbench from there.
• When removing albums, with Review them first in the workbench. You then look at the photos that are only in the albums that go, from all of those albums together.

The workbench looks only at those photos, on your iPhone, with the image model of iOS. It looks for three kinds:

• Near-duplicates: photos taken shortly after each other that are nearly the same. First comes the photo the app proposes to keep: a favourite, otherwise the photo that turned out best according to iOS. If none of the photos is a favourite and iOS could not judge every one of them, the first photo of the series comes first, and the app says so.
• Failed or blurry: photos that did not turn out according to iOS, such as photos that are out of focus. In our tests with synthetic test photos, the image model found out-of-focus photos almost always, photos that are too dark about half the time, and overexposed photos often not. We calculated those figures with the same image model from Apple on a Mac; on an iPhone it has not been measured.
• Screenshots and documents: photos that according to iOS are screenshots, receipts or documents.

You can also go through all the photos yourself. Swipe left to delete, right to keep, and down to move a photo to another album. Every swipe is also a button, and you can undo each step.

Nothing goes until you finish and confirm. The summary shows everything once more. Photos are moved first; Rewind saves your albums beforehand, so you can undo that. Then iOS asks you once to allow deleting all the photos you chose. A photo you delete goes to Recently Deleted and so leaves all your albums, not just the album you are cleaning up. In our tests on iOS 27, iOS also said in that question how many albums the photos disappear from. If you don't allow it, or deleting fails, nothing is deleted. The move did happen, and you can undo it right away or later in Rewind. If you try again after that, the app only deletes: it does not move the photos again, also not if you undid the move. The deletion itself does not go into Rewind.

Good to know:

• The workbench requests the images without internet access and only uses what is already on your iPhone. So it does not download a photo that is only in iCloud. If it gets no image of a photo, it does not look at that photo and tells you so. This has not yet been tested with photos that really are only in iCloud.
• What the workbench works out for each photo is kept on your iPhone: a series of numbers that describes the image, a quality score, and whether it looks like a screenshot or document. That way a next visit is faster.
• If the image model of iOS gives no usable result, the workbench says so. Then it does not make up groups or scores. It still recognises screenshots, and you can go through all photos yourself.
• Shared albums and other read-only albums cannot be cleaned up.
• The workbench does not look at hidden photos, just as Photos does not show them in an album.

When does iOS ask for confirmation?

Some things iOS does not let an app do without your permission. The question comes from iOS itself, in its own window, not from the app.

• Access to your photos: on first launch, after the three introduction pages, when you tap Allow access to photos.
• Removing albums: one question per action, even for many albums at once, and also when you apply many proposals at once. In our tests on iOS 27, iOS added that the photos will not be deleted. This question also comes up when merging, if the original albums are removed, and when restoring, if albums or folders are removed in the process. If restoring removes only folders, iOS may not mention photos: in a trial in which we removed only empty folders, iOS said nothing about photos. We did not check this when restoring itself. In any case, no photo is deleted then.
• Deleting photos in the workbench: one question per round, for all chosen photos together.

For creating albums, renaming them, and adding photos to an album or taking them out, iOS asks nothing. When merging, putting in a folder and removing, the app does show you a preview first, when renaming with a pattern the new names first, and in the workbench a summary first. When you rename one album, you only see the name field and the old name. Restoring with Undo, Undo moving, Undo action or Put everything back as it was starts right away, without a preview. In Rewind, the app first asks whether you are sure, but there too without a preview per album; the question only names albums that stay because the app thinks they hold a hidden photo. Undo asks the same question when there is an action after it.

If you don't allow something, that part does not happen. When merging, the new album may then already exist while the old albums are still there too. The app tells you so and offers Put everything back as it was right away. If you don't allow the question when restoring, after the app had already put part of it back, your albums are only partly back as they were. The app says that too; then try once more with the same button.

Which devices does the app work on?

An iPhone with iOS 26 or later. The bar with Undo action at the bottom of the screen is there from iOS 26.1. On iOS 26.0 you undo an action on the screen right after it, or in Rewind. The app is available in English and Dutch.

What does the app cost?

In the Netherlands the app costs 6.99 euros, once; in other countries the price is what the App Store shows there. That gets you the whole app: there are no in-app purchases and no subscription.

Payment goes through Apple. Refunds are also requested from Apple.

Contact

If you are stuck, email info@farcon.cloud. Please include which iPhone and iOS version you have, and what you were doing when it went wrong.

Dennis Siersma