Spaces

What is an encryption?

Encryption scrambles information so that only the people or systems with the right key can read it.

In plain words

Imagine writing a letter in a code that only you and the reader can understand. If someone intercepts it on the way, they see nonsense. Encryption does this for data, automatically and in a fraction of a second.

You will meet it in two places. Encryption in transit protects data while it travels, for example between your browser and a website. The little padlock in the address bar is a sign of it. Encryption at rest protects data while it is stored.

Encryption is one layer of protection, not a guarantee. Good security also means limiting who has access, using strong keys and passwords, and acting fast if something looks wrong. No single measure does the whole job, which is why several are used together.

For you, the practical habit is to guard your keys and passwords. A strong lock does not help if the key is shared around. Using a different key for each tool also makes it easy to switch one off.

How it works in Spaces

Per the Privacy page, data travels over encrypted connections, and access is limited to the people who need it to run Spaces. If you connect a Meta ad account, its access token is stored encrypted.

Spaces stores a hash, not the full key, after you copy an API key. You can pause or revoke any key at any time, and Spaces may pause a key that looks compromised.

Related terms

FAQ

Is my data encrypted when it travels?

The Privacy page says data travels over encrypted connections.

Does Spaces store my full API key?

No. It stores a hash after you have copied the key, which is why a key is shown only once.

What should I do to keep things safe?

Keep your keys and passwords private, and pause or revoke a key if you think it has leaked.

Where can I read more about security?

See the Security and Privacy pages.

Useful next: Security, Privacy, Account safety. Every term: the glossary.