Glossary

Terms below use the same named anchors as the Spanish edition.

• Bank credit {#bank-credit}: saved time for a configured app group, spent only during an explicitly started session and measured group-app use. See the full concept.
• Partner allowance {#partner-allowance}: a signed, fixed-duration authorization for a specific request scope. Its deadline starts when approval is recorded. See the full concept.
• Sleep {#sleep}: a policy restriction that blocks bank access; only an explicitly approved, enabled sleep exception can permit access. See the full concept.
• Policy {#policy}: the signed app, bank, and schedule configuration activated on the phone. See the full concept.
• Request {#requests}: a durable server record asking for an allowance, with a distinct decision and expiry state. See the full concept.
• Offline behavior {#offline}: local enforcement continues from saved verified policy, while new server information and unresolved decisions remain unavailable. See the full concept.
• Approver: the paired person who reviews and decides requests.
• Grant: the signed authorization sent after approval; it is not the same as the request or notification.
• Usage Access: Android permission that allows BloqueApp to read app-usage events for practical bank accounting.
• Exact alarm: Android scheduling capability used for timed recovery and expiry boundaries; delivery can still be delayed by the operating system.
• Receipt: the durable server response describing a request’s current state. A receipt is not itself access authority.
• SignalR hint: a foreground live message that prompts the Android app to refresh a durable receipt. It does not authorize access or wake a background phone.
• Web Push: browser push delivery used to notify the approver; it prompts review and does not itself record a decision.

See concepts for stable explanations and the guide for workflows.