What the MSG. companies keep when you sign in, where it stays,
and the only three reasons a person there may look at it.
Closed.
Who we are
The MSG. companies, MSG. Philantropy (Hong Kong, China), MSG. Vanguard (China,
Mainland), MSG. Americas (Argentina) and MSG. Monnet (Luxembourg), and their
subsidiaries, share a common responsibility to promote Trust. That is why they are
united in BERNAYS & BERNAYS SINGAPORE PTE. LTD., which handles everything their apps collect in Singapore,
one of the safest jurisdictions in the world, hosted by Amazon Web Services, the
most reputable provider in the industry.
Your data. Your choices.
Access, update or delete your data
Ask the product you are using, directly. A request that spans several products
is not available yet. For that, or for anything else, write to
privacy@msg.community.
Decide where your data lives
Your data is kept in Singapore. The MSG. companies look forward to fair and sound
privacy laws when Europe becomes a federal state.
Please don't use MSG. services if what you intend to do with them includes
handling data that cannot be exported.
Say how you feel about what MSG. may do with your data
after you die, or once you stop using MSG. services
MSG. is a cradle of innovation and experiments on emerging technologies, such as
digital voice replicas or memorial chatbots, which could help your loved ones
through grief. If you feel uncomfortable about a future use of your personal data,
write your guidelines to legacy@msg.community.
We will make our best efforts to follow them in our products.
AI & Tracking Transparency
We clearly mark an interaction as recorded, REC, or
content as generated by AI, AI, when all three of these
are true:
an average person could not easily tell that it is recorded, or generated by AI;
an average person could face seriously adverse consequences from believing
otherwise;
the channel lets us show a mark.
Otherwise we do not mark it, so that a mark keeps its meaning. For example:
REC When you digitally sign a binding agreement, or
agree orally to pay a retainer or to commit to a multi-year plan for a product,
the interaction is recorded, to be used as evidence in the event of
litigation.
AI When you press a button such as “Read
aloud” or “Rephrase with a more formal tone”, the result is
not marked as generated by AI: you asked for it.
AI When a prospective business partner uses our
platforms to preview an upcoming feature, the preview is marked, so as not to
mislead them about what is actually available if they enter into an agreement
today.
This policy covers MSG. sign-in: the sign-in buttons in each MSG.
app, our page at login.msg.community where you sign in with your phone
number, the address auth.msg.community through which Google and Apple
return you, and the guest access that lets you use an MSG. app without signing in.
It does not cover what each app does with its own data once you are in. Each app
describes that itself. “Your data. Your choices.” and “AI &
Tracking Transparency”, on the home page,
speak for all MSG. services.
The sign-in pages
auth.msg.community, run by Amazon Cognito, sets cookies that keep
your sign-in session and protect against forged requests. They are needed for
sign-in to work. Our page at login.msg.community sets no cookie, and
neither does this privacy center.
What we will ask Google
Three things only: openid, email and
profile. Google handles the sign-in on its side, under its own privacy
policy. We never see your Google password.
What we will ask Apple
Your name and your email address. Apple lets you hide your email address and not
share your name. Apple handles the sign-in on its side, under its own privacy
policy.
With your phone number
We ask for your number, and nothing else.
Or as a guest
Some MSG. apps let you use them as a guest, without signing in. We then create a
random guest identifier for that app on your device, with no name, email or account
behind it.
your Google account identifier, a number that never changes;
your email address;
your name;
if your Google account belongs to an organisation's Google Workspace, the
domain of that Workspace (for example example.com).
We never see your Google password.
What Apple gives us
your Apple account identifier for MSG., which never changes;
your email address or, if you chose to hide it, an address Apple creates that
forwards to yours, ending in @privaterelay.appleid.com;
your name, the first time you sign in only, if you share it.
We never see your Apple password.
When you sign in with your phone number
You type your number on our page. Amazon Web Services sends you a code by SMS,
through Amazon Simple Notification Service, which hands the message to phone carriers
to reach your phone. Your number and the code pass through Amazon and those
carriers. We accept numbers from the countries the page lists.
Your number is your account: a new number is a new account.
What we create from it
An MSG. account, which holds the items above, the date it was created and updated,
and the groups you belong to. The staff group is added automatically only
when you sign in with Google and your Workspace domain is one of ours. Other groups,
which open a given app, are added by a person.
If you were a guest
If you sign in on a device where you used an app as a guest, the guest identifier
is linked to your MSG. account, so what you did as a guest stays yours.
Records of sign-in activity
Each sign-in, sign-up and session refresh is recorded to help us keep the service
secure and fix problems. These records may include your IP address and details of
your device and browser. A sign-in with a code is also checked by Amazon Web
Services for signs of attack, from your IP address and device. When an account is
created, the full sign-in event is recorded, with the email address, name, Workspace
domain or phone number it carries.
To let you in: to check with Google or Apple who you are, or that the phone is
yours.
To recognise you as the same person across the MSG. apps, so you have one
account.
To recognise members of our own organisations as staff.
To let you use an app as a guest, and keep what you did when you sign in.
To keep the service secure and to investigate problems.
We do not sell this data. We do not use it for advertising.
Who may look at it
Our services use it to do what this page describes, and for nothing else.
No person at the MSG. companies looks at it, except:
in connection with litigation;
when a person's life is under imminent threat;
to run the service: to give someone the access they asked for, or to
fix a fault or stop an attack, each time by a named person.
Any other access by a person is a violation of our policy.
Who we are
The MSG. companies, MSG. Philantropy (Hong Kong, China), MSG. Vanguard (China,
Mainland), MSG. Americas (Argentina) and MSG. Monnet (Luxembourg), and their
subsidiaries, share a common responsibility to promote Trust. That is why they are
united in BERNAYS & BERNAYS SINGAPORE PTE. LTD., which handles everything their apps collect in Singapore,
one of the safest jurisdictions in the world, hosted by Amazon Web Services, the
most reputable provider in the industry.
Who else handles it
The MSG. apps you sign in to receive your account identifier,
email address or phone number, name and groups, so they know who you are.
Amazon Web Services hosts MSG. sign-in, stores everything
above, and sends the codes by SMS.
Phone carriers deliver the code to your phone.
Google and Apple handle the sign-in on their
side, under their own privacy policies. They know that you signed in with MSG.
sign-in.
Where it is kept
In Amazon Web Services' Asia Pacific (Singapore) region. The sign-in address is
delivered through Amazon's worldwide content delivery network.
How long we keep it
We keep it with no end date: your MSG. account, guest identifiers, and the records
of sign-in activity are kept for as long as MSG. sign-in runs.
If you sign in with Apple, or another provider we add
What we keep
Whatever the provider shares with us, as it reaches us. We do not sort it, and we
do not look through it for personal data to set aside.
Where it is kept
In MAXIN, our record store, with Amazon Web Services in Singapore. It is encrypted
at rest. Nothing in it is ever deleted or overwritten.
Who may look at it
The same rule as above, with the same three cases. Any other access by a person is
a violation of our policy.
How a look is traced
Every read of MAXIN is logged. A read made through ORACLE, our reading service, is
written into MAXIN itself with the identity of whoever made it, and is never deleted:
it stays traceable to its author for good.
Questions and requests
Ask the product you are using first. For anything else, write to
privacy@msg.community.
You can stop using MSG. sign-in at any time. You can also remove MSG. sign-in's
access from your Google or Apple account settings.
Changes to this policy
When this policy changes, its version and effective date change, and the previous
version stays readable here.
Version 1.2, kept on record. The current version is version 1.3.
Before you sign in with Google
Privacy policy, version 1.2. Effective 14 October 2026. Version 1.1 and
version 1.0 stay on record.
This policy covers MSG. sign-in: the page at
auth.msg.community where you sign in with Google, and the guest
access that lets you use an MSG. app without signing in. MSG. sign-in is shared by
the MSG. apps on msg.community. It does not cover what each app does
with its own data once you are in. Each app describes that itself.
The sign-in page
The sign-in page at auth.msg.community, run by Amazon Cognito,
sets cookies that keep your sign-in session and protect the form against forged
requests. They are needed for sign-in to work. This privacy center sets no
cookie and stores nothing in your browser.
What we will ask Google
We ask Google for three things only: openid, email and
profile. Google handles the sign-in on its side, under its own
privacy policy. We never see your Google password.
Or as a guest
Some MSG. apps let you use them as a guest, without signing in. We then create
a random guest identifier for that app on your device, with no name, email or
account behind it.
Privacy policy, version 1.2. Effective 14 October 2026. Version 1.1 and
version 1.0 stay on record.
What Google gives us
your Google account identifier, a number that never changes;
your email address;
your name;
if your Google account belongs to an organisation's Google Workspace, the
domain of that Workspace (for example example.com).
We never see your Google password.
What we create from it
An MSG. account, which holds the items above, the date it was created and
updated, and the groups you belong to. The staff group is added
automatically when your Workspace domain is one of ours. Other groups, which open
a given app, are added by a person.
If you were a guest
If you sign in on a device where you used an app as a guest, the guest
identifier is linked to your MSG. account, so what you did as a guest stays
yours.
Records of sign-in activity
Each sign-in, sign-up and session refresh is recorded to help us keep the
service secure and fix problems. These records may include your IP address and
details of your device and browser. When an account is created, the full sign-in
event is recorded, including the email address, name and Workspace domain.
Privacy policy, version 1.2. Effective 14 October 2026. Version 1.1 and
version 1.0 stay on record.
Why we use it
To let you in: to check with Google who you are.
To recognise you as the same person across the MSG. apps, so you have one
account.
To recognise members of our own organisations as staff.
To let you use an app as a guest, and keep what you did when you sign
in.
To keep the service secure and to investigate problems.
We do not sell this data. We do not use it for advertising.
Who may look at it
Our services use it to do what this page describes, and for nothing else.
No person at the MSG. companies looks at it, except:
in connection with litigation;
when a person's life is under imminent threat;
to run the service: to give someone the access they asked for, or to
fix a fault or stop an attack, each time by a named person.
Any other access by a person is a violation of our policy.
Who we are
The MSG. companies, MICHEL SIMON GESTION. (France), MSG. Vanguard (China),
MSG. Americas (Argentina) and MSG. Monnet (Luxembourg), share a common
responsibility to promote Trust. That is why they are united in BERNAYS & BERNAYS SINGAPORE PTE. LTD.,
which handles everything their apps collect in Singapore, one of the safest
jurisdictions in the world, hosted by Amazon Web Services, the most reputable
provider in the industry.
Who else handles it
The MSG. apps you sign in to receive your account
identifier, email address, name and groups, so they know who you
are.
Amazon Web Services hosts MSG. sign-in and stores
everything above.
Google handles the sign-in on its side, under its own
privacy policy. Google knows that you signed in with MSG. sign-in.
Where it is kept
In Amazon Web Services' Asia Pacific (Singapore) region. The sign-in page is
delivered through Amazon's worldwide content delivery network.
How long we keep it
We keep it with no end date: your MSG. account, guest identifiers, and the
records of sign-in activity are kept for as long as MSG. sign-in runs.
If you sign in with another provider
Today, MSG. sign-in offers Google only. If we add another provider, this is
what applies to what it shares with us.
What we keep
Whatever the provider shares with us through OAuth, as it arrives. We do not
sort it, and we do not look through it for personal data to set aside.
Where it is kept
In MAXIN, our record store, with Amazon Web Services in Singapore. It is
encrypted at rest. Nothing in it is ever deleted or overwritten.
Who may look at it
The same rule as above, with the same three cases. Any other access by a
person is a violation of our policy.
How a look is traced
Every read of MAXIN is logged. A read made through ORACLE, our reading
service, is written into MAXIN itself with the identity of whoever made it, and
is never deleted: it stays traceable to its author for good.
You can stop using MSG. sign-in at any time. You can also remove MSG. sign-in's
access from your Google account settings, under Third-party apps and
services.
Changes to this policy
When this policy changes, its version and effective date change, and the
previous version stays readable here.
Version 1.1, kept on record. The current version is version 1.3.
Signing in with Google
Privacy policy, version 1.1. Effective 14 October 2026. Version 1.0 stays on record.
This policy covers MSG. sign-in: the page at
auth.msg.community where you sign in with Google, and the guest
access that lets you use an MSG. app without signing in. MSG. sign-in is shared by
the MSG. apps on msg.community. It does not cover what each app does
with its own data once you are in. Each app describes that itself.
What we collect
When you sign in with Google. We ask Google for three things
only: openid, email and profile. Google then
gives us:
your Google account identifier, a number that never changes;
your email address;
your name;
if your Google account belongs to an organisation's Google Workspace, the
domain of that Workspace (for example example.com).
We never see your Google password.
What we create from it. An MSG. account, which holds the
items above, the date it was created and updated, and the groups you belong
to. The staff group is added automatically when your Workspace domain
is one of ours. Other groups, which open a given app, are added by a person.
When you use an app as a guest. We create a random guest
identifier for that app on your device, with no name, email or account behind
it. If you later sign in on that device, the guest identifier is linked to
your MSG. account, so what you did as a guest stays yours.
Records of sign-in activity. Each sign-in, sign-up and
session refresh is recorded to help us keep the service secure and fix
problems. These records may include your IP address and details of your device
and browser. When an account is created, the full sign-in event is recorded,
including the email address, name and Workspace domain.
Cookies on the sign-in page. The sign-in page at
auth.msg.community, run by Amazon Cognito, sets cookies that keep
your sign-in session and protect the form against forged requests. They are
needed for sign-in to work. This privacy center sets no cookie and stores
nothing in your browser.
Why we use it
To let you in: to check with Google who you are.
To recognise you as the same person across the MSG. apps, so you have one
account.
To recognise members of our own organisations as staff.
To let you use an app as a guest, and keep what you did when you sign
in.
To keep the service secure and to investigate problems.
We do not sell this data. We do not use it for advertising.
Who may look at it
Our services use it to do what this page describes, and for nothing else.
No person at the MSG. companies looks at it, except:
in connection with litigation;
when a person's life is under imminent threat;
to run the service: to give someone the access they asked for, or to
fix a fault or stop an attack, each time by a named person.
Any other access by a person is a violation of our policy.
Who we are
The MSG. companies, MSG. Vanguard (China), MSG. Americas (Argentina) and
MSG. Monnet (Luxembourg), share a common responsibility to promote Trust. That
is why they are united in BERNAYS & BERNAYS SINGAPORE PTE. LTD., which handles everything their apps
collect in Singapore, one of the safest jurisdictions in the world, hosted by
Amazon Web Services, the most reputable provider in the industry.
Who else handles it
The MSG. apps you sign in to receive your account
identifier, email address, name and groups, so they know who you
are.
Amazon Web Services hosts MSG. sign-in and stores
everything above.
Google handles the sign-in on its side, under its own
privacy policy. Google knows that you signed in with MSG. sign-in.
Where it is kept
In Amazon Web Services' Asia Pacific (Singapore) region. The sign-in page is
delivered through Amazon's worldwide content delivery network.
How long we keep it
We keep it with no end date: your MSG. account, guest identifiers, and the
records of sign-in activity are kept for as long as MSG. sign-in runs.
You can stop using MSG. sign-in at any time. You can also remove MSG. sign-in's
access from your Google account settings, under Third-party apps and
services.
Changes to this policy
When this policy changes, its version and effective date change, and the
previous version stays readable here.
Version 1.0, kept on record. The current version is version 1.3.
MSG sign-in: privacy policy
Version 1.0 · Effective 29 September 2026 ·
Operated in Singapore by BERNAYS AND BERNAYS SINGAPORE PTE. LTD. ·
Contact privacy@michel-simon.com
This policy covers MSG sign-in: the page at
auth.msg.community where you sign in with Google, and the guest
access that lets you use an MSG app without signing in. It does not cover what
each app does with its own data once you are in. Each app describes that
itself.
What we collect
When you sign in with Google. We ask Google for three things
only: openid, email and profile. Google then
gives us:
your Google account identifier, a number that never changes;
your email address;
your name;
if your Google account belongs to an organisation's Google Workspace, the
domain of that Workspace (for example example.com).
We never see your Google password.
What we create from it. An MSG account, which holds the
items above, the date it was created and updated, and the groups you belong
to. The staff group is added automatically when your Workspace domain
is one of ours. Other groups, such as access to Sabine, are added by a
person.
When you use an app as a guest. We create a random guest
identifier for that app on your device, with no name, email or account behind
it. If you later sign in on that device, the guest identifier is linked to
your MSG account, so what you did as a guest stays yours.
Records of sign-in activity. Each sign-in, sign-up and
session refresh is recorded to help us keep the service secure and fix
problems. These records may include your IP address and details of your device
and browser. When an account is created, the full sign-in event is recorded,
including the email address, name and Workspace domain.
Cookies on the sign-in page. The sign-in page at
auth.msg.community, run by Amazon Cognito, sets cookies that keep
your sign-in session and protect the form against forged requests. They are
needed for sign-in to work. This privacy center sets no cookie and stores
nothing in your browser.
Why we use it
To let you in: to check with Google who you are.
To recognise you as the same person across the MSG apps, so you have one
account.
To recognise members of our own organisations as staff.
To let you use an app as a guest, and keep what you did when you sign
in.
To keep the service secure and to investigate problems.
We do not sell this data. We do not use it for advertising.
Who else handles it
The MSG apps you sign in to receive your account
identifier, email address, name and groups, so they know who you
are.
Amazon Web Services hosts MSG sign-in and stores
everything above.
Google handles the sign-in on its side, under its own
privacy policy. Google knows that you signed in to MSG.
Where it is kept
In Amazon Web Services' Asia Pacific (Singapore) region. The sign-in page is
delivered through Amazon's worldwide content delivery network.
How long we keep it
We keep it with no end date: your MSG account, guest identifiers, and the
records of sign-in activity are kept for as long as MSG sign-in runs.