It would be useful to set a TTL (time-to-live) on connections when they're created through AuthKit. For example, passing something like { expiresIn: "24h" } so the connection is automatically revoked after that period.
This is especially relevant for product use cases (vs agency/internal tooling). When AuthKit is embedded in a consumer-facing product, end users connect their accounts for a specific task and may never return to explicitly disconnect. In an agency context, you control the connections and can manage cleanup — but in a product, you're relying on users to revoke access themselves, which most won't do.
Our use case: we request temporary read-only Gmail access for a one-time email scan. Users don't always click "disconnect" when they're done, so connections stay active indefinitely. An auto-expiration would let us guarantee to users that access is revoked after a set period, which is important for trust and privacy — especially when handling sensitive data like email.
It would be useful to set a TTL (time-to-live) on connections when they're created through AuthKit. For example, passing something like
{ expiresIn: "24h" }so the connection is automatically revoked after that period.This is especially relevant for product use cases (vs agency/internal tooling). When AuthKit is embedded in a consumer-facing product, end users connect their accounts for a specific task and may never return to explicitly disconnect. In an agency context, you control the connections and can manage cleanup — but in a product, you're relying on users to revoke access themselves, which most won't do.
Our use case: we request temporary read-only Gmail access for a one-time email scan. Users don't always click "disconnect" when they're done, so connections stay active indefinitely. An auto-expiration would let us guarantee to users that access is revoked after a set period, which is important for trust and privacy — especially when handling sensitive data like email.