Skip to content
TRUST

No Passwords. Verified Every Time.

Every sign-in is confirmed with a one-time code sent to the member's own email or phone, and every request is checked against the member's role.

WHAT IT ISPasswords are reused, guessed, phished and leaked. Upward removes them. A member enters their email or phone, receives a short-lived one-time code, and only the person who controls that inbox or device gets in. Behind sign-in, role-based permissions, row-level data isolation between companies and encrypted integration credentials limit what each account can reach.

One-time codes

Codes expire quickly and work once. Text codes last 10 minutes with 5 attempts, and sign-in attempts are logged with the identifier masked.

  • Email or phone
  • Short-lived and single use
  • Masked audit trail of sign-in attempts

Sessions you can inspect

Each session is tied to the verified contact and can expire or be revoked. Members can see their devices and a log of changes to their login email or phone, and the old contact is notified.

  • Session expiry and revocation
  • Device list
  • Login change log with notifications

Roles and isolation

Roles are stored apart from profiles so a profile edit can never grant access. Row-level security enforces company boundaries in the database itself.

  • Owner, admin, leader and member roles
  • Database-enforced tenant boundaries
  • Calendar sharing exposes busy time, not private details

Secrets and keys

Integration credentials are encrypted with AES-256-GCM. API keys for developers are issued per company.

  • Encrypted mailbox credentials
  • Server-only secret keys
  • Contact form embed keys can be regenerated

Staff access is accountable

When support signs in as a member to help, the session records who started it and the reason, and ends on its own expiry.

  • Actor and reason recorded
  • Time-limited sessions
  • Reviewed in the admin audit

Honest limits

We follow an application security checklist and review database policies regularly, and findings from those reviews are tracked and fixed.

  • Regular database security reviews
  • No claim of certifications we do not hold
  • Report concerns through Contact

How Upward is different

No passwords to steal, guess, reuse or phish
One-time codes that expire quickly and work only once
Access tied to the member's own verified email or phone
Role-based permissions and company-level data isolation
Encrypted storage of connected integration credentials

Frequently asked questions

What if I lose access to my email or phone?

Members can add backup contacts, and the Contact page lists how to reach us.

Can I sign in with Google?

Where enabled, yes. Upward still stores no password.

How long do codes last?

Text codes expire after 10 minutes and allow 5 attempts.

Can staff see my account?

Only through a recorded sign-in-as session with a reason.

Are my emails safe if I connect a mailbox?

Credentials are encrypted at rest, and you can disconnect at any time.

Related

Have a question about Security?

Ask Vutesa, Upward's AI assistant — answers draw on this page's content.

Ready to turn every conversation into growth?

Start free, then replicate your system across your whole team.