Help for using Ampaly

How does Ampaly store my data?

Ampaly is designed as a local-first app. Your budgeting data stays on your device unless you choose to export a backup file yourself.

Can I move my data to another device?

Yes. You can export a `.ampaly` backup file and then import it on another device. This is the recommended way to transfer your budgeting setup.

How do recurring transactions work?

You create a contract once with an amount, frequency, and next date. Ampaly then generates future operations from it, while still letting you adjust a single occurrence when life changes.

How do I mark an operation as paid?

Open the operation from the dashboard, change its status to paid, and confirm the update. You can also choose whether the account balance should be updated automatically at the same time.

Can I postpone or adjust just one occurrence?

Yes. Ampaly lets you edit a single generated occurrence without changing the whole recurring contract. This is useful when a payment moves to another day or has a slightly different amount.

What should I do if my real balance is different from the forecast?

Update the account balance to match reality, then review unresolved operations. Ampaly is built to help you catch up without rebuilding your whole budget from scratch.

Can I change the theme or appearance mode?

Yes. In Settings, you can choose the appearance mode and switch between available themes. Some themes may depend on your subscription plan.

Can I change language, currency, or first day of week later?

Yes. Regional preferences can be updated at any time from Settings, so you are not locked into the choices made during onboarding.

Does Ampaly require an account?

No. There is no mandatory Ampaly account to create before using the app.

How do backups work?

You can export your app data as a `.ampaly` backup file and import it later. Importing a backup replaces the current app data after confirmation, so it is best used intentionally.

How can I report a bug or suggest a feature?

Send an email to support and describe what happened, what you expected, and which screen or action triggered the issue. Feature ideas are welcome too.