Perksmith · security
Know who can act. Know what changed.
Customer information and reward balances need clear boundaries. This overview explains Perksmith’s approach to staff access, business records and integration credentials. Bring your security requirements to the conversation so we can discuss the details relevant to your setup.
Give each role the access it needs.
Perksmith’s access model links operations to the relevant business and assigns staff permissions by role. Review who can see customer information, change reward rules and perform financial actions. Your security review can include the permitted actions and the boundaries that stop someone going further.
Keep the original action in the record.
The records model preserves money movements and records reversals as related changes. Requests that change a balance identify the intended action so a retry can be recognized. A repeated confirmation or refund should be explainable through the resulting balance and its records.
Keep credentials with the systems that need them.
Keep the secret keys for software connections, called API credentials, in appropriate server-side systems. Use the maintained documentation for permissions, keys and webhook verification. Your messaging and payment providers bring their own account responsibilities; agree who manages those alongside the Perksmith connection.
Review the controls that matter to your business.
| What you want to understand | What the product provides | What to review for your setup |
|---|---|---|
| Staff access | Permissions and plan access control supported settings and actions. | Who may see customer information, change rewards and handle financial actions. |
| Action records | Supported actions record who acted, what changed and when. | Which workflows are covered and how long the records are retained. |
| Customer privacy requests | Customers can submit supported privacy requests and track their status. | Deletion and retention terms; some records may need to be retained. |
- What you want to understand
- Staff access
- What the product provides
- Permissions and plan access control supported settings and actions.
- What to review for your setup
- Who may see customer information, change rewards and handle financial actions.
- What you want to understand
- Action records
- What the product provides
- Supported actions record who acted, what changed and when.
- What to review for your setup
- Which workflows are covered and how long the records are retained.
- What you want to understand
- Customer privacy requests
- What the product provides
- Customers can submit supported privacy requests and track their status.
- What to review for your setup
- Deletion and retention terms; some records may need to be retained.
Review these features in the workflows your team will use, alongside the service terms, before sharing customer data.
Confirm the service details before you commit.
| Ask about | Information to confirm |
|---|---|
| Hosting and service providers | The hosting region and providers for your proposed service. |
| Retention and deletion | What is kept, what can be removed and how a request is handled. |
| Backups and recovery | Backup arrangements, recovery terms and the evidence available for review. |
| Support and incidents | How to contact the team and which support or incident-handling terms apply. |
| Moving your customer records | Supported imports or connection work, who prepares the data and how the result is checked. |
- Ask about
- Hosting and service providers
- Information to confirm
- The hosting region and providers for your proposed service.
- Ask about
- Retention and deletion
- Information to confirm
- What is kept, what can be removed and how a request is handled.
- Ask about
- Backups and recovery
- Information to confirm
- Backup arrangements, recovery terms and the evidence available for review.
- Ask about
- Support and incidents
- Information to confirm
- How to contact the team and which support or incident-handling terms apply.
- Ask about
- Moving your customer records
- Information to confirm
- Supported imports or connection work, who prepares the data and how the result is checked.
Bring your requirements so we can confirm the relevant details. The Privacy notice explains the handling of personal information. Do not send credentials or sensitive customer records in an initial enquiry.
Questions for your review.
What can I review before choosing Perksmith?
Ask about staff permissions, customer-data handling and the integration controls your team needs to assess.
Where should I send a security question?
Describe the security or privacy question on Contact. Leave credentials and sensitive customer records out of the initial enquiry.
Everyday sales. Lasting relationships.