Support for FamPlan, OctoVault and the products and services of the Spydaz family of companies. Each channel below reaches the same support team.
State the product concerned, the issue observed and the result expected. Email creates a support ticket automatically.
support@spydaz.comAvailable during business hours. Calls are frequently unattended; leaving a message creates a support ticket, which is answered in the same queue as email.
(860) 292-0859Each product maintains its own documentation, published independently of application releases and revised as the product changes. Consult it before submitting a ticket; most configuration and usage questions are answered there.
Reference documentation for every screen, its controls and its behavior. These are the pages the application itself serves under “How this screen works”.
FamPlan documentationReference documentation for backups, devices, encryption keys and billing. Published within the account dashboard; authentication is required.
Sign in to the dashboardThis form creates a support ticket and routes it to the team responsible for the product. A reply is sent by email. support@spydaz.com reaches the same queue.
Reporting from within the application is the preferred route. Every screen provides “How this screen works” and “Report a problem”: from the menu control at the upper left on screens that have one, and from a “?” control at the upper right on screens that do not, such as a module screen or the assistant. A report submitted this way includes the originating screen, the application version and the device model, which removes a round trip to establish the build in use. Email and the ticket form above are equivalent alternatives.
Handling and retention of reports and their attachments is set out in the Privacy Policy.
For backups, account administration, billing or device enrollment, sign in to the account dashboard or email support@spydaz.com. Include the product name and a description of the issue. Target response time is one business day.
OctoVault is zero-knowledge: no copy of an encryption or recovery key is retained. Data cannot be recovered without the key, and the offline recovery key should be stored accordingly.