Frequently asked questions

Credently logs when an approval request is sent, when the client link is opened, and subsequent visits with timestamps and channel metadata where available. If a client claims they never saw the request, you can point to that delivery and view history as part of your record — but whether that satisfies your contract or local rules is for you and your counsel to assess. Credently documents the process; it does not decide disputes.

It depends on your jurisdiction, contract type, and how the clause was agreed. Credently helps you execute and document a tacit-consent workflow after you add an appropriate clause to your agreement — it does not guarantee enforceability. Start from our sample clause template on the Resources page, then have your lawyer adapt it for your country and use case. That page is not legal advice.

We recommend it, but it is not strictly required to use Credently. Our sample clause page gives you a starting template you can paste into your master agreement or SOW. Before you rely on it for live client work, have your own counsel review the wording for your jurisdiction and industry.

Each certificate includes a unique reference code, request metadata (title, client, deadline), a timestamped outcome (approved, rejected, revision requested, or auto-approved), key audit events (sent, viewed, decided), and a QR code so third parties can verify the record on Credently. If e-signature was required, the signed document link is included when available.

Once the review window closes without a rejection or revision request, the outcome is recorded (including auto-approval when tacit consent applies). The client may still open the link afterward, but they cannot change the logged decision on that request. For a new round, send a fresh request or restart from a revision workflow.

One approval request = one credit on paid plans (or one slot against your Free monthly quota), regardless of how many file links you attach. Sending a revised version (V2) after a revision request is a new send on the same request record, not a brand-new billing unit on Free; on paid plans, restarts follow your plan's request-credit rules.

By default you share links (Figma, Drive, Loom, uploaded PDFs for e-sign, etc.). Credently stores the approval record, audit trail, and certificate — plus signed PDFs when e-signature is used. We do not mirror your entire Drive; optional Google Drive activity sync reads metadata/events for files you link.

You cannot silently extend an active timer on the same request. You can send a manual reminder while it is still pending, or create a new request with a later deadline. If the client asked for changes, use the revision flow and send an updated version with a fresh window.

Credently uses encrypted connections (HTTPS/TLS) for data in transit. Data at rest is hosted on infrastructure providers with industry-standard encryption. For a detailed breakdown aligned with your compliance needs, contact hello@credently.co — we will share our current security summary as it is finalized.

Certificates already issued remain verifiable via their reference codes and public verification URLs. Account cancellation affects your dashboard access and new sends; retention of underlying records follows our Privacy Policy and data-retention schedule. Export important certificates before closing your account.

We design Credently for B2B use with GDPR-aligned practices: lawful bases documented in our Privacy Policy, data-processing terms for business customers, and controls for access and deletion requests. Formal compliance posture (DPA, sub-processors, EU hosting choices) is described in our legal docs — review them or ask hello@credently.co for the latest package.

No. Clients open a secure link and verify their identity with a one-time link sent to the email on the request before they approve or request revision — they do not need to create a Credently account. Their options are to approve, request revision, or stay silent (if tacit consent applies, silence becomes auto-approval when the deadline passes). You need an account to create and manage requests.

Free plan allows three new approval requests per calendar month. When you reach the cap, you can wait until the next month, upgrade to a paid plan with prepaid request credits, or purchase top-ups on eligible tiers. Existing requests stay accessible; you just cannot create new ones until quota resets or you upgrade.

Yes. The Free plan needs no card — sign up with email, send up to three requests per month, and upgrade only when you want paid features. Paid plans and add-ons use Stripe checkout when you choose to buy.