> For the complete documentation index, see [llms.txt](https://docs.lightpost.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightpost.app/education/securing-your-data.md).

# Securing Your Data

Practical guidance for protecting church member data, limiting exports, and responding carefully to requests for information.

Church records contain personal information that members have trusted your congregation to protect. Names, contact information, addresses, family relationships, birthdates, attendance, and other details can all be useful to someone with the wrong intentions.

Keeping that information secure requires deliberate decisions about who receives it, why they need it, and how much they actually need.

{% hint style="warning" %}
**Treat every export as sensitive.** Once data leaves Lightpost, it can be copied, forwarded, synced, or stored in places your church no longer controls.
{% endhint %}

### What Lightpost Protects

Lightpost uses authenticated access, permissions, proactive monitoring, log analysis, alerting and security-focused infrastructure to protect information while it remains in the platform.

Those protections do not extend to a PDF, spreadsheet, contact list, or other file after it has been downloaded. Its security then depends on the device, email account, cloud storage, transfer method, and person receiving it.

### Before Sharing or Exporting Data

Pause before creating a copy and ask:

* What specific need are we solving?
* Can that need be met through normal Lightpost access instead?
* Have we independently verified the requester's identity and authorization?
* Which people and fields are actually required?
* How will the data be delivered, stored, and deleted when it is no longer needed?

Do not distribute data simply because a request sounds routine or appears to come from a familiar person.

### Export Only What Is Needed

Filtering is an important security measure. Use filters to limit an export to only the people needed, then select only the fields required for the task.

For example, if someone needs mailing addresses for one ministry group, export that group and its address fields—not the congregation's full people list. A smaller export creates less risk if the file is misplaced or compromised.

### How Data Can Get Into the Wrong Hands

Data exposure often happens through ordinary copies rather than a platform breach:

* Email attachments remaining in inboxes for years
* Files saved to personal computers or cloud storage
* Public or incorrectly shared links
* Contact lists synced to other apps and services
* Lost, shared, or already logged-in devices
* Someone posing as a member and asking for a directory

Every additional copy creates another place that must remain secure.

### Frequent Member Requests

When someone requests data, first understand the actual need and recommend the safest option.

#### “Please email me a PDF copy of the directory.”

Direct the member to Lightpost for digital directory access. If they truly need a paper copy, print it and physically hand it to them. Avoid emailing the full directory for convenience—email inboxes are a major attack surface, and attachments may be retained, synced, forwarded, or exposed if the account is compromised.

#### “I need a list of members for a ministry or event.”

Ask which people and details are necessary. Use groups and filters to create the smallest useful list, or handle the communication through Lightpost without providing a raw export.

#### “I cannot log in, so can you send me the directory?”

Help the member regain access to Lightpost instead of bypassing its access controls with an exported copy.

#### “I am a member and need a copy of the directory.”

Do not rely only on the name, email address, or phone number used to make the request. Verify the person's identity and need through contact information already on file or another trusted method.

{% hint style="info" %}
**A simple standard:** Keep data in Lightpost whenever possible. Verify who is asking, share only the minimum needed, use the safest practical delivery method, and remove copies when the need has passed.
{% endhint %}