Does inserting/removing random characters in a string count as cryptography?

Question

I'm making an iOS game. All developers need to determine whether their app uses cryptography or not.

My game saves files in the Documents folder. They are .plist files representing dictionaries. They are encoded in base 64.

From what I gather, encoding is not encrypting. So we're fine there.

However, the values inside the dictionary (after decoding) are a bit tricky. Suppose that your score is 250. In the dictionary the value is a string like:

@2@5@0@

So for the game to read your score, it removes the @ characters (and when saving the game, it puts them back).

That's just an example. Does that count as cryptography?

NOTE: I'm not asking about Apple's policies. I mentioned it for context.

• sea-rob: This sounds like a simple form of Steganography: hiding messages inside something else, like text inside an image. The problem with your scheme is that it doesn't seem to meet the goal of encryption: hiding the message so that only the intended recipient can read it. Anyone can decode your message, and pretty easily filter out the noise, and read the original message.
• Omer Iqbal: This is not even Steganography, in which the plaintext is "hidden" not obvious. Here is it quite obvious to the naked eye. This is just encoding IMO.

Answer 1

No. This is also just encoding.

Cryptography is well-defined, and according to no definition of encryption do you have a ciphertext. Per Wikipedia,

Cryptography is the practice and study of techniques for secure communication in the presence of third parties (called adversaries).

Unless you believe adding the @ can make your communication secure, you're good :-)

• Saturn: If I repeatedly encode something in base 64 over and over, that's still encoding?
• Jasmijn: Yes. A rule of thumb you might want to use is that it is only encryption if, to retrieve the stored information, you need a secret key. See also obfuscation, which repeatedly Base64ing something might be, which is more useful for preventing people from accidentally reading something (think spoilers).
• Omer Iqbal: @Omega Yes, IMO, that would still be encoding and not encryption. If by looking at your code, one can easily understand how to get the original values back, then its not encryption. Encryption algorithms are two types: original text is completely unrecoverable, e.g. in hashing, or recovering original text requires a secret without which it is irrecoverable. Your case is neither.