> For the complete documentation index, see [llms.txt](https://help.appybuilder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.appybuilder.com/tutorials/keystore.md).

# keystore

Keystores contain certificate information that contains security information and is used when publishing apps to Android market.

A "keystore" is a database used by JDK "keytool" command and KeyStore class to store your own private keys, and public key certificates you received from others. "keystore" supports the following features:

* Two types of entries: key entries for private keys and certificate entries for public key certificates.
* A key entry contains the private key and a certificate chain of the corresponding public key.
* Every entry has a unique alias name.
* Key entries are protected by separate passwords.
* "keystore" may have different implementations from different security package providers. The default implementation from Sun is called JKS (Java Key Store).

## Creation

A keystore is created when you initially create your first app. Every AI distribution contains its own unique keystore. As result, **if you have published an app** from another repository (e.g. MIT AI), and now would like to continue with AppyBuilder, you'll have to import keystore from MIT AI into AppyBuilder.

***NOTE: Before performing any imports, create a backup of your existing keystore by exporting it. Otherwise, you may encounter issues when you try to publish apps into Android market.***

The export / import can be done by selecting Projects menu, then selecting "Export keystore" or "Import keystore"

![](http://community.appybuilder.com/uploads/default/original/1X/522f5c637576f04f63471d829a9bf15e83a3a927.png)

.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.appybuilder.com/tutorials/keystore.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.