Sign in. Then verify.
Perim uses Google or Apple sign-in. Access to financial data requires an additional authenticator check enforced by the backend. Keep your sign-in account, device and authenticator secure. We never ask for an authenticator code by email or chat.
Banking features in development
The planned account and card are not currently available. Their provider and security details will be published before launch. The controls below describe our current connected-account private test.
Read-only bank access in the private test
Bank connections use Plaid. Perim does not receive your bank password, hold your money or initiate payments. Connection credentials are held on the backend. You can disconnect or delete your account.
Protecting the information
Production traffic uses encrypted HTTPS connections. Google Cloud encrypts the database at rest, and access is limited through authenticated backend services and restricted administrative permissions. Sensitive app authentication state is stored using iOS Keychain. We check dependencies for known vulnerabilities and maintain a remediation process.
Protection and security are different
App blocking depends on Screen Time permissions, the iOS version and your settings. It cannot secure your bank account or prevent every way of spending. Read the protection guide and run the device test.
Report a concern
Email jibril@perim.money with a description and steps to reproduce. Do not include customer data, access tokens or passwords. We will arrange a suitable way to share sensitive details if needed. If your bank account or card may be compromised, contact the bank immediately.