Your privacy.
Clearly explained.

Who this covers

Mementom is operated by nCent Holdings. This policy covers the Mementom website, personal keyring service, secure authorization window, shared-key pickup, company console and partner API.

Personal keyring access does not require an identity profile. Company console accounts are different: registration uses a company name, work email and protected sign-in credentials. If you email us, we receive your email address and whatever you include in the message.

A connected company is responsible for the information it collects and the way it uses its own site or app. Its privacy policy applies to those activities, including purchases, customer accounts and marketing.

Keyrings and verification

A key combines an image with a private caption. Mementom keeps the records needed to verify that combination and enforce its access rules:

• Random keyring and key identifiers, status and ownership relationships.
• Image-derived verification values created in your browser, including values used for image matching. These are credential data, even though they are not your original image.
• Protected caption verifiers and encrypted caption values. Authorized secure flows can retrieve a caption where the product requires it; captions are not stored only as irreversible hashes.
• Protected keyring-file, authenticator and recovery records, plus session and verification state.

Your saved keyring file holds the local material needed to use your keys, including images. The saved browser copy is an encrypted ZIP, not a store of decrypted pictures or captions. You can also download the file for your own safekeeping. It is different from the service’s keyring record.

When you open a personal keyring, the secure window can randomly select an eligible key, show its image and ask for its caption. Image-based recovery or verification may instead ask you to choose the matching image. Real credential entry and verification take place inside Mementom’s separately served secure window.

Identity-free email

An Email service key lets you receive permitted campaign messages in a mail app. Mementom generates the mailbox address without requiring an email tied to your identity. Mailbox addresses, messages, delivery records, inbox filters and service-key access records support that service; they are linked to your keyring’s mailbox, not a supplied identity profile.

You control the Email key’s permissions and access, and can block companies or campaigns through inbox filters. This mailbox receives campaign messages; it does not send replies or ordinary outgoing mail. Company staff work-email accounts and messages you send to support remain separate.

Permissions and activity

Mementom uses these records to create, verify, recover and manage keys; recognize permitted company relationships; and decide whether a requested action is allowed.

Permissions and challenges include the company and app, requested action, status, time and use limits, and the operational description supplied by the company. Companies must keep identifying customer details out of those operational fields.

Activity records include event and request identifiers, times, outcomes and the relevant key, permission or challenge. They support your activity history, company troubleshooting, limit enforcement and investigation of misuse. They are not a record of everything you do on a company’s website.

We also use operational records to prevent replay and abuse, maintain service reliability, respond to support requests and meet applicable legal obligations.

What companies receive

A connected company receives a temporary app session, the identifiers needed to match its request, and an approval or rejection for the requested access. It does not receive your original key images, private captions, recovery secrets or any persistent keyring identifier.

The current relationship reference is scoped to a company and may be reused across that company’s approved applications. Different companies receive different references. The reference can persist across visits and devices when you use the same keyring; an expiring session does not make every visit a new relationship.

Company details in the secure window

When a company displays private details inside a Mementom flow, those details come from a separate, company-owned frame. The company retrieves them from its own systems. Mementom’s surrounding page does not read that frame’s private content or relay its private retrieval tickets. Operational challenge records are separate from that private presentation.

Purchases and other identifying information

A reference without a name is not a guarantee of anonymity. If you give a company a shipping address, payment information, email address or other identifying information, it may connect that information to your visits using its relationship reference, cookies or other records.

Mementom does not hide identifying information you give directly to a company or control that company’s marketing systems. Using Mementom does not itself give the company a phone number or an email tied to your identity. Permitted campaigns can reach your identity-free mailbox through Mementom’s controlled delivery addresses.

Cookies and your device

Mementom uses necessary session cookies and browser storage to keep a flow connected, recognize recent authentication, handle secure-window returns and remember a saved keyring file. Protected session cookies use secure transport and HTTP-only controls.

Recent authenticator verification can be reused for a limited period in its permitted context. The default is 15 minutes, and an app can set a different period. Having a saved file does not by itself authorize an action.

The current public site does not use third-party advertising cookies. A connected company’s cookies and any content it serves follow that company’s own practices.

You can clear Mementom’s site data in your browser. This can remove its saved file and local session state, but it does not delete the service’s keyring record or copies you downloaded. Keep a current backup before clearing local storage.

Shared keys and pickup

A shared key is a separately issued credential with its own identifier, caption, permissions and limits. You can use an existing key’s image with a new caption or choose a new image. A new image saved as a shared-key record does not automatically become a personal sign-in key.

The issuer can review shared-key activity, change permitted limits, pause or restore access, or permanently delete the shared key through the secure management flow. Failed use or limits on a shared key do not change the source personal key’s limits.

For QR or link pickup, the sender’s browser encrypts the transfer material before uploading it. Mementom holds encrypted transfer data and pickup state; the recipient’s browser decrypts it and prepares the single-key file. The private caption should be delivered separately.

A completed shared-key upload remains encrypted on the service so its pickup QR code or link can be reused by multiple recipients. The issuer can reopen available pickup details in secure management. Each recipient’s pickup session is short-lived; completing that session does not delete the stored encrypted file. The payload is removed when the issuer deletes or revokes the shared key. Uncompleted transfer preparations expire and are cleaned up. Transfer status and activity records may remain.

Pickup expiry is different from the shared key’s access limits. A downloaded file can keep working while its permission remains active. Changing its server-side limits does not require sending a new file. Permanently deleting the shared key prevents that issued credential from authorizing again, but cannot erase copies from someone else’s device.

Providers and disclosures

Mementom uses infrastructure providers, including AWS hosting and database services, to operate the service. Network providers process connection information, including IP addresses, to deliver traffic. Service providers may process operational information under their agreements with us.

The application uses keyed network codes for certain abuse controls rather than storing the raw address in those records. Failed-login controls track failure counts and times. A challenge with an explicit network rule can also retain its rule result and related verification metadata.

We may preserve or disclose relevant records when required by law or valid legal process, or when reasonably necessary to investigate abuse, protect people or address a security incident.

Mementom’s access service does not sell your key images or private captions to connected companies. This policy does not authorize a separate data marketplace or a sale of links between your activity records.

How long records remain

Active credential and permission records remain available to operate your keyring and enforce its current rules. An expired permission or exhausted use allowance stops access; it does not automatically erase the record.

Completed shared-key transfer payloads remain available for reusable pickup until issuer deletion or revocation, as described above. Individual pickup sessions and uncompleted preparations expire separately. Session and challenge records have their own expiry periods. Failed-login network-code records have a default retention period of 24 hours.

Activity, relationship, deletion and security records can remain after access ends so we can show an accurate history, keep revoked credentials invalid, investigate incidents and meet legal obligations. Removing a key is not a promise to erase every related record or backup immediately.

Retention depends on the record’s purpose, whether it is needed for an active service or unresolved incident, and applicable legal requirements. Contact us about retention or deletion of a particular record.

Security

Mementom separates credential handling from public and company pages. Controls include encrypted transport, protected stored values, scoped permissions, expiring requests, replay protection and verification before sensitive changes.

Keep your files, captions and recovery material private. No online service can promise absolute security, and a download cannot be remotely removed from every place its recipient may have copied it.

Your choices and rights

• Use My key ring to open secure management, review activity, and add, replace or remove keys.
• Choose the permissions, duration and successful-use limits for shared access, and pause or permanently delete a shared key.
• Cancel an authorization before it completes, sign out, or clear saved browser data.
• Contact us to ask about access, correction, deletion, restriction, objection or portability where those rights apply. Where processing relies on consent, you can withdraw that consent.

We may need key-based verification before releasing or changing keyring-linked records. Do not send credentials by email. If you disagree with our response, you may be able to complain to the data protection authority where you live.

For information held by a connected company, contact that company directly. Deleting a Mementom credential does not delete that company’s purchase history, mailing list or other records.

Children

Mementom is not directed to children under 13 and does not knowingly ask them to create a keyring. A participating company is responsible for the age and consent requirements of its own service.

Policy changes

We will revise this policy when our data practices change and identify the effective date of the published revision. Material changes will be brought to your attention as required. Proposed features are not a description of processing already in use.

Contact

For privacy questions or requests, contact nCent Holdings at policy@mementom.net.

Do not include a key image, private caption, keyring password, recovery code, pickup secret or session token.