How Memtime Handles and Protects Your Connected App or ERP Credentials
Your Connected App or ERP credentials stay on your device. Here is where they are handled, who can access them, and how they are protected.
Where your credentials are stored
Your Connected App or EPR connection credentials are stored locally on your device, in the Memtime app's local storage. The local app uses them only to connect to Connected App.
They are not stored on Memtime's servers or anywhere else on the internet.
Memtime connects directly from your device to your Project Management tool via the Connected App, with no proxy or backend in between, so nothing passes through our infrastructure.
How your credentials are protected
- Secure local storage: Credentials are stored using Electron safeStorage.
- Encryption: Credentials are encrypted with AES-256-GCM.
- Access control: Only the locally installed Memtime app and the authenticated user on the device can access the stored credentials.
- No hardcoded credentials: Credentials are never hardcoded into the Memtime application.
- Secure communication: Credentials are only transmitted over secure HTTPS connections.
- Code obfuscation: The Memtime app's JavaScript source is obfuscated to make reverse engineering significantly harder and to protect sensitive logic.
Exceptions
Some Connected Apps work differently because of how their connection is set up:
- Shared data: If an integration requires data to be shared among users in your company, for example, a shared admin token, that data is stored in the Memtime cloud. To make the token available to everyone within the team, the proxy is used to enrich the requests.
- Cloud authentication: If an integration requires authentication through the cloud, such as “OAuth 2.0 Authorization Code Grant”, the access token is retrieved through Memtime's cloud but is not stored there.
Support
Need help with the article or have any questions? Reach out to us anytime at: