Excluded Devices
Rupt employs a unique approach to device management that prioritizes user trust while maintaining security. When device signals change over time, Rupt uses intelligent exclusion mechanisms to handle device evolution without compromising account sharing detection accuracy.
- How device exclusion works
- The dormant state
- Trust-first approach
- Device resurrection
- Benefits of device exclusion
How device exclusion works
Rupt follows two fundamental heuristics in device identification:
- Always perform device identification - Every device interaction is analyzed
- Always err on the side of caution - Trust users first, verify when necessary
When device signals drift over time, Rupt may detect what appears to be a new device that looks very similar to an existing one. This commonly happens when specific device signals change in a way that makes it unidentifiable from the original device.
Instead of treating this as a completely separate device (which could trigger false account sharing alerts), Rupt excludes the older device version.
Device exclusion prevents false positives while maintaining the ability to detect genuine account sharing scenarios.
The dormant state
When a device is excluded, it enters a dormant state rather than being permanently deleted. This serves several important purposes:
| State | Description | Behavior |
|---|---|---|
| Not excluded | Device is currently recognized and counted | Participates in account sharing detection |
| Excluded/Dormant | Device is excluded but preserved | Does not count toward device limits |
| Resurrected | Previously excluded device becomes attached again | Returns to normal operation |
Excluded devices remain in Rupt's system but do not:
- Count toward device limits
- Trigger account sharing challenges
- Appear in attached device counts
Trust-first approach
Rupt's device exclusion mechanism embodies a trust-first philosophy:
This approach ensures that:
- Users aren't unnecessarily challenged due to device updates
- Legitimate device evolution doesn't trigger false account sharing alerts
- The user experience remains smooth and uninterrupted
Device resurrection
One of the key advantages of the dormant state is device resurrection. If the original device signals ever return, Rupt can reactivate the dormant device.
This usually happens when the user actually changed the device or multiple sharers keep alternating between similar devices.
Device resurrection ensures that legitimate usage patterns don't result in lost device associations or unnecessary account sharing challenges.
Benefits of device exclusion
Rupt's device exclusion strategy provides multiple advantages:
1. Maintained accuracy
If Rupt's exclusion decision was incorrect and the "old" device returns, the system can still detect account sharing because the device was preserved in a dormant state rather than deleted.
2. Enhanced user experience
Users don't face unnecessary friction from device updates, software changes, or natural device evolution. The system adapts to legitimate changes without compromising security.
3. Reduced false positives
By excluding older device versions instead of counting them as separate devices, Rupt significantly reduces false account sharing alerts.
4. Flexible recovery
The dormant state allows for recovery from incorrect exclusion decisions, ensuring robust long-term device management.
Implementation considerations
When working with Rupt's device exclusion system:
- Monitor device counts: Excluded devices won't appear in attached device counts but may be visible in detailed analytics.
- Plan for resurrection: Rupt fully handles device resurrection and exclusion so you don't need to worry about it.
- Trust the system: Rupt's exclusion logic is designed to minimize false positives while maintaining security.
Device exclusion works automatically and requires no additional configuration. The system handles device evolution transparently while maintaining account sharing detection accuracy.